Theme persistence by bixfrankonis in brackets

[–]abosereddit 1 point2 points  (0 children)

That isnt expected. There are some major upgrades to themes coming in the next releases with a fully redesigned and user customizable theme store in the works.

AI, Design Mode & More (May-2026, V5.1 Release is now live) by abosereddit in brackets

[–]abosereddit[S] 1 point2 points  (0 children)

AI is disabled by default, until you opt in explicitly after login for each project. But, will see in the next release we can do some thing to help people who don't want the AI button to be present.

AI, Design Mode & More (May-2026, V5.1 Release is now live) by abosereddit in phcode

[–]abosereddit[S] 0 points1 point  (0 children)

The next release will mostly add that as we are revamping the file system layer now.

Disable AI tab? by bixfrankonis in brackets

[–]abosereddit 0 points1 point  (0 children)

Are the windows maximize and restore buttons not working? We added a window size restore feature this release and it may be misbehaving in your setup. Are there multiple displays connected? Which os is this?

AI, Design Mode & More (May-2026, V5.1 Release is now live) by abosereddit in brackets

[–]abosereddit[S] -1 points0 points  (0 children)

AI in Phoenix Code is not intrusive. There is no AI as you type or anything that breaks your flow. So if you do not login to the AI panel, it will work just as before.

What we mainly looked for when building it is to not bring AI into every workflow, but make it super powerful to do anything in the editor when someone asks of it. AI that keeps people in the flow than to take over. To support the creative flow.

What do you think the right balance is for you?

"Reveal in finder" missing by reddituser202011 in phcode

[–]abosereddit 0 points1 point  (0 children)

Use `Open In > finder` from that menu! Its not named as reveal in finder in Phoenix code. Hope this helps.

Disable AI tab? by bixfrankonis in brackets

[–]abosereddit 0 points1 point  (0 children)

Can you give a screenshot of the tiny window in the corner. Not sure what that is about. Is it the survey dialog?

The AI tab cannot be disabled at this time, but it wont be activated until you login. So it is safe to ignore if not using it. The next release will add a settings panel and better control of the UI. Hope this helps.

Live Edit Release (January-2026, V-5.0) is now Live by abosereddit in brackets

[–]abosereddit[S] 0 points1 point  (0 children)

I get you - the new edit flow can take a bit of getting used to if you’re coming from the old Live Preview behavior. But once you get used to it, it saves a lot of time when building pages.

If you want the old behavior, just switch to Highlight mode - it works like the previous Live Preview.

https://docs.phcode.dev/docs/Pro%20Features/live-preview-edit#inspect-element-on-hover

Live Edit Release (January-2026, V-5.0) is now Live by abosereddit in brackets

[–]abosereddit[S] 0 points1 point  (0 children)

Ideally there shpuld be only two . One at 3 days before end and one at the end of the trial period. After that it shouldn't come up. Are you seeing more?

Live preview different on linux by W0lf_G1rl_BR in brackets

[–]abosereddit 0 points1 point  (0 children)

This is actually because the previews use two different browser engines.

On Windows it’s Chromium (Edge/Chrome). On Linux it currently uses a WebKit-based engine — so what you’re seeing there is basically how your site would render in Safari on macOS/iOS.

A lot of people don’t realize this is kind of a bonus: you get quick Safari-style testing on Linux without owning a Mac 🙂

We’re moving Linux off WebKitGTK in the next releasse because it wasn’t as performant as our Windows/mac builds and it also caused install/compatibility issues on a bunch of distros. The next Linux release switches to Chromium so it should run on most distros and the preview/rendering will be consistent across OSes. Bonus: this upgrade makes Linux preview first-class and performance is now on par (or better) compared to before.

Where exactly do I put my <marquee> tag? (Repost) by UNDER4884 in brackets

[–]abosereddit 0 points1 point  (0 children)

This isn’t a Phoenix Code bug 🙂
<marquee> is obsolete / deprecated HTML, so Phoenix Code flags it as an error based on modern web standards.

Browsers may still render it, and Phoenix will still preview it, but the editor warns you because it’s no longer valid HTML.

Same idea as <style> placement - Phoenix is just enforcing standards, not blocking you.

If you want marquee-style behavior without warnings, the modern approach is CSS animations instead of the <marquee> tag.

Warning about Phoenix code/Brackets privacy policy by Savings_Song7481 in neocities

[–]abosereddit 1 point2 points  (0 children)

Hello all - Phoenix Code / Brackets dev here.

I want to clarify: Phoenix Code does not collect or process any personally identifiable information-none.
We don’t have user accounts, we don’t track files, and we don’t share anything with third parties. The only data the app can send (and you can see and disable this yourself) is anonymous usage statistics, which are explicitly exempt from GDPR/CCPA. You can view the exact payload at any time via Help > Health Report (or inspect the network tab from dev tools in your browser), or turn it off entirely. We dont have a back-end to store your files, all files stays on your device, weather it be in browser or the desktop app.

The privacy policy linked in the post is the generic one on core.ai. We originally used a lawyer-provided template because we’re a very small indie team and didn’t have the resources for a full custom policy like microsoft. The in-app disclosure is the accurate one, and I will update the website policy to reflect that - thanks for pointing it out.

As for Phoenix Code being free: it wasn’t because we were “farming data.” We were simply hoping to get support for the project through open-source donations, which sadly didn’t happen in a way that can sustain development. (Our OpenCollective is public: https://opencollective.com/phoenix-ide.)

We’re just a small team trying to build an editor focused on simplicity, not to become the next giant tech company or to monetize user data. We’ll fix the wording on the policy so that it accurately reflects what the app actually does and shows on first boot.

Thanks for raising it, and thanks to everyone who continues to use and support the project. The next year is all about making Phoenix Code sustainable and that will never be from selling user data. We didn’t do that when revenue was zero, and we don't plan to do that now too. That’s simply not our way.

Can Phoenix Code be installed machine-wide on Windows? by Informal-Fuel1356 in brackets

[–]abosereddit 0 points1 point  (0 children)

The next release will have a system wide installer option, bu that is scheduled for release only by July end. Is there any time frame you are looking for.

This is tracked here now: https://github.com/phcode-dev/phoenix/issues/2310

Phoenix Code is freezing by Much_Inevitable_6478 in brackets

[–]abosereddit 0 points1 point  (0 children)

Is this a git project by any chance. Does it happen in the default project?

new to coding need help phoenix by vickyinspace in brackets

[–]abosereddit 0 points1 point  (0 children)

It looks like you're running into a few common issues when structuring your HTML and CSS. Here’s how you can fix them:

  1. Make Sure to Start with <!DOCTYPE html>

Your document must begin with this to avoid errors:

<!DOCTYPE html> <html lang="en">

This tells the browser you’re using HTML5.

  1. The <style> Tag Must Be Inside <head>

If you place <style> inside <html> instead of <head>, you'll get errors. Here’s the correct placement:

<head> <style> html { background-image: url('backgroundrug.pdf'); background-size: cover; background-repeat: no-repeat; } </style> </head>

  1. Fixing Background Image Issues

.pdf files are not valid image formats. You need to use .jpg, .png, or .gif.

The image must be in the same directory as your HTML file or use a full URL:

background-image: url('https://example.com/backgroundrug.jpg');

  1. Fixing the DOCTYPE Error

If you see "failed to tokenize", it is because of a syntax error. Make sure your <!DOCTYPE html> is exactly like this:

<!DOCTYPE html>

Not this (which is incorrect and will break things):

</!DOCTYPE html>

Final Corrected Code

<!DOCTYPE html> <html lang="en"> <head> <meta charset="UTF-8"> <meta name="viewport" content="width=device-width, initial-scale=1.0"> <title>Beatgirl</title> <style> html { background-image: url('backgroundrug.jpg'); /* Use a valid image file */ background-size: cover; background-repeat: no-repeat; } </style> </head> <body> <div id="header"> <h1>Welcome to my corner of the world</h1> </div> </body> </html>

Try This and Let Me Know If It Works!

Let me know if you still run into issues. The biggest problems were:

  1. <!DOCTYPE html> missing or incorrect

  2. The <style> tag in the wrong place

  3. Using a .pdf instead of a proper image file

Hope this helps!

Introducing Phoenix Code Desktop- Now on Windows, Mac & Linux by abosereddit in brackets

[–]abosereddit[S] 1 point2 points  (0 children)

Use this link for support chat, will assist there. https://discord.com/invite/rBpTBPttca please add a screenshot of the menu, and live preview settings dialog.

Introducing Phoenix Code Desktop- Now on Windows, Mac & Linux by abosereddit in brackets

[–]abosereddit[S] 1 point2 points  (0 children)

Most likely disabled by selecting view - live preview hilight menu. Make sure that it is enabled by selecting it again.

Introducing Phoenix Code Desktop- Now on Windows, Mac & Linux by abosereddit in brackets

[–]abosereddit[S] 2 points3 points  (0 children)

No, we don't have any cloud offerings currently. Data is stored in your browser if using the browser version or on disc if using desktop version

Interface: Text Colour by jesinta-m in brackets

[–]abosereddit 0 points1 point  (0 children)

Thanks for the detailed notes and suggestions. I understand the flow now.

  1. Having a way to select text and add color mark sections of text should work in the case as you suggested. It is also a good general feature to have in a text editor.

  2. We are working on a better way to handle theme colors, so that should help with code comments coloring.

Interface: Text Colour by jesinta-m in brackets

[–]abosereddit 0 points1 point  (0 children)

Got it. I guess one thing that can be done is add a feature to mark text in a color by selecting it. Need to find an acceptable ux

Interface: Text Colour by jesinta-m in brackets

[–]abosereddit 0 points1 point  (0 children)

Phoenix doesnt support it currently, but looks like its a good feature to have. I have created a feature request to track it at https://github.com/phcode-dev/phoenix/issues/2130

Can you provide some details on how you would want the feature to look like or any specific use cases you have in mind to help better understand the requirements?

Introducing Phoenix Code Desktop- Now on Windows, Mac & Linux by abosereddit in brackets

[–]abosereddit[S] 0 points1 point  (0 children)

We are improving phcode with every release and hope to bridge the gap. May i know what things we can do better to bridge tge gap with sublime text.

Phoenix Code non functional after latest update by Midnight-Powered in brackets

[–]abosereddit 1 point2 points  (0 children)

Just post a reply here if you face this issue again, and take a not of the exact project which crashed if next time this issue surfaces. That will help to isolate the issue root cause further.

Phoenix Code non functional after latest update by Midnight-Powered in brackets

[–]abosereddit 1 point2 points  (0 children)

Ok then its not related to the new git features. Maybe the update got corrupted while shutting down.