Registro de mudancas

When you ask the AI to recreate a design from a screenshot, check how a page looks, or work with an image, it now sees the actual picture - not just a link to it.

Before, the AI could take a screenshot but sometimes couldn't really look at it, so it would capture the same page over and over without making progress. That's fixed. Now it looks once and gets to work.

What the AI can see now:

• Screenshots it takes of a live page - so it can clone a design you point it at, or check that your published site looks right.
• Images it generates or edits - it sees its own result, so it can judge it and refine instead of working blind.
• Any image you give it a link to - paste an image URL and ask the AI to describe it, match its style, or build from it.

It also accepts more image formats automatically (including AVIF) and resizes large images for you, so you don't have to convert anything first.

Pro mode now lets you choose how much the AI thinks before it answers. Open the mode picker in the chat and set an Intelligence level for the task in front of you:

• Low / Medium - quick answers for simple edits, with less waiting
• High (the default) - the balanced setting that fits most work
• Extra High / Max - let the model reason longer on hard, multi-step problems

Set it per chat from the mode picker, or choose a default for every new chat in Preferences > AI Model > Default Intelligence. Economy mode stays the fast, simple lane, so there's no dial to think about there.

Also in this release

• No more blank Pro replies - on rare occasions a Pro answer could come back empty; those now retry automatically instead of showing nothing.

</content> </invoke>

Picking Premium mode in the AI chat sometimes did nothing in a freshly opened project - the switch quietly snapped back to Economy. That's fixed: your mode choice now sticks in every project, even before you've sent your first message.

Improvements

• Premium mode is selectable everywhere - the choice is saved the moment you make it, in any project
• Set your default mode - choose whether new chats start in Economy or Premium from Preferences > AI Model > Default Mode, and it applies across all your projects

Pointing your own domain at an app is the step where most people get stuck. So we rebuilt it into a guided setup wizard for Playcode Cloud apps that walks you through it, step by step.

Open Custom domains in the publish menu, type the domain you own, and the wizard does the hard part:

• One record, not a pile of them. It detects your DNS provider, shows the single record to copy, and the exact name your provider expects. No TXT ownership record, no IP addresses, no certificate to install.
• Ownership and SSL are automatic. Once your record resolves, Playcode confirms the domain is yours and issues the HTTPS certificate for you.
• Close the window and walk away. Setup can take a few minutes for DNS to update, so we email you the moment your domain is live instead of making you wait and refresh.
• Root or www, handled. Want yourdomain.com without the www? The wizard shows the right record when your provider supports it, and points you to www when it doesn't.

Each step has a plain-language Need help? panel answering the questions first-timers actually ask, so you never need to know what a CNAME is to finish.

See the full walkthrough in the custom domain help guide.

Two billing fixes for existing subscribers. Opening the Billing Portal silently failed on mobile (it worked on desktop) - the link is now opened in a way phones don't block. And changing your plan (for example Pro → Business) no longer dead-ends on "redirecting to secure payment" - subscribers are now sent to the billing portal's plan switcher.

Fixes

• Billing Portal opens on mobile - previously nothing happened on phones; the portal now opens reliably
• Plan upgrades work for current subscribers - switching plans routes to the billing portal instead of failing

When Playcode's AI takes on a multi-step job (setting things up, running your tests, building, or publishing), it now tells you what it's doing in plain language as it happens, instead of showing raw technical output. You'll see what it's checking and why, like "Are there already settings files here?", and how a longer step is going, like "Tests about halfway, passing so far", so you're never left watching a blank, frozen screen.

On longer jobs the AI now works more like a teammate at the keyboard: it starts the step, keeps an eye on it, and gives you a quick read every few seconds, flagging early if something looks stuck instead of going quiet until the very end. Clearer, simpler, and written for founders, not engineers.

Sites served on your own custom domain now load over HTTP/2. Browsers can fetch many files at once over a single connection instead of requesting them one after another, which is the same modern protocol your visitors already get on Playcode subdomains.

The effect is most noticeable on mobile, where pages have many scripts and styles to load. In our mobile testing on a custom-domain site:

• Mobile Lighthouse performance: 73 → 85
• Largest Contentful Paint: 4.7s → 3.5s

No setup is needed. Every site published to a custom domain on Playcode Cloud gets this automatically.

Cloud publishing now observes deploy logs in short, bounded checks instead of waiting on one long-running server step. This helps the publish dialog keep up with newer publish and rollback activity, especially when a build step is quiet for a while.

If a publish is cancelled or a deploy step takes longer than expected, Playcode can now notice follow-up publish activity faster instead of appearing stuck with no output.

Cloud project previews now come back much faster after they have gone idle.

For projects with a warm snapshot available, Preview can wake in about 1-2 seconds instead of waiting for a full cold start that can take about a minute. That is up to around 60x faster when you return to a recent Cloud project.

This is most visible when you are iterating on a full-stack app: open the project, wait for Preview, make a change, leave it idle, then come back later. Playcode can now resume the working project state instead of rebuilding the whole dev environment every time.

If a project needs a clean start, for example after an infrastructure update or an expired snapshot, Playcode falls back to the slower cold start path so the project still opens correctly.

GLM 5.2 is now selectable in Playcode's AI model picker. It replaces GLM 5.1 in the visible picker and gives you a newer long-context reasoning option for code-heavy tasks.

Choose it from Menu → Preferences → AI Model when you want to compare GLM against your usual model on the same project.

GLM 5.1 is no longer shown in the picker. Existing history remains intact, and the newer GLM 5.2 option is the one to use going forward.