Registro de cambios

The publish dialog could not be scrolled on a phone, which on small screens put the confirm button out of reach. The dialog body now scrolls properly, so you can publish a project from your phone end to end.

Speaking your idea on the home screen asked the wrong wallet whether you were allowed to. If you were working inside a team workspace, the microphone checked your personal plan and credits instead of the team's - so a team with an active subscription and credits to spare could still be told it needed to subscribe.

Voice now prices the same workspace everything else does: the one you have selected, which is the one a new project is created in and the one that pays for the work. Typing was never affected.

On very long builds the agent periodically folds older conversation history into a compact brief to stay fast. That fold used to be lossy: the agent could forget its instructions, lose its place, and re-read files it had just read. The whole handoff was rebuilt:

• The agent now writes its own handoff note. Instead of an outside

summary, the model working on your project writes a structured continuation brief for itself - what it was doing, what it decided, what comes next, in its own words.

• Task instructions can no longer be lost. A background task's original

instructions survive every handoff word-for-word.

• No more re-reading loops. The brief carries the exact code regions the

next step needs, pre-loaded - resuming costs zero extra reads instead of re-opening file after file.

• A stuck loop breaks itself. If context refills right after a fold, the

agent gets more room instead of folding again and again.

• A heads-up before the fold. The agent is warned as the handoff

approaches, so it finishes the step it is on and writes things down first.

Ask for something big - a storefront, an admin panel, order emails - and the agent now breaks it into parts you can follow, instead of leaving you to read a stream of technical steps.

• A plan card in the chat. The parts of your order in your own words,

each one pending, building, or done. On full-stack apps, a part only turns done after the server checks that its page actually loads - and every finished part carries an Open button with the real address, so "the admin panel is ready" is a click, not a path to guess.

• One line while it works. During a build, a quiet line above the

message box shows which part is in progress and for how long - real elapsed time, not a guess.

• The plan opens as its own page. Click it to read the full plan,

nicely rendered with diagrams, without leaving the chat. When the agent updates the plan, you see what changed - changed sections are marked, and a history lets you read any earlier version. Every plan change is a real commit in your project's git history.

• The preview stops playing dead. While the agent rebuilds your app,

the preview keeps the last good page dimmed under one line - "Rebuilding this page - it comes back by itself" - instead of flashing white. A new health check catches blank pages the old green light missed. When nothing is running, real errors still show as errors.

• The agent answers in your language. Switching the app language now

reliably carries into the agent's replies, plan titles, and progress notes.

• Bring your own instructions and skills. A project's AGENTS.md is

now read automatically by every agent working on it - same rules as other AI coding tools, whole file, no silent truncation - and projects can carry their own skills in .agents/skills/, listed and loadable like built-ins.

On long builds the agent periodically compacts older conversation history to stay fast. Until now it compacted early enough that big tasks - many files, long sessions - could lose track of files it had just read and re-read them.

• The default Context level is now High (was Medium). On models with large

context windows the agent keeps roughly 2.5x more of the conversation before compacting, so long builds stay coherent instead of looping over the same files.

• No extra confirmation for the default. The one-tap cost acknowledgment

now appears only when you raise Context above High (Extra High or Max).

• Your explicit choice is untouched. If you set Medium (or any level)

yourself, that choice stays exactly as you set it.

You can still change Context per chat in the build-quality dialog, or set your own default in Settings → You → AI defaults.

When your app emails an address that has not confirmed it wants mail yet, that message is Held - stored safely, waiting on a verification. Until today, a held message looked just like normal captured mail, and it was easy to miss that real messages were waiting on you. That is fixed, end to end:

• A new Held status. Held messages show an amber Held chip with the exact reason on the row - clearly separate from mail that is simply captured by design.
• A standing notice in the editor. While anything is held, the panel shows "N messages waiting on you" with a direct door to Settings > Email.
• An email to you. The first time a message is held for an address, the project owner gets an email naming the address - so a contact form filling up overnight can no longer wait silently. Repeats fold into at most one summary a day.
• Deliver held mail in one click. Once the address verifies, Settings shows how many messages were held and a Deliver held button. Nothing ever sends without you.

Two more changes in the same area:

• The Mailbox panel is now called Emails - a clearer name for what it is: every email your app sent, with its delivery status. Playcode Email sends mail; it does not receive it.
• A new help page, What emails can your app send, explains the transactional-only sending policy in plain language.

When the assistant starts a long job - a build, an app-store submission, a big install - the chat now stays yours.

• You can always talk. A message you send while a job runs reaches the

assistant immediately, mid-work, instead of waiting in silence until the job ends.

• Stop means stop. Pressing Stop lands in about two seconds, even during a

long wait - and the assistant stays quiet afterwards until you speak.

• Finished jobs report back on their own. When a background job completes,

a small note appears in the chat and the assistant picks the result up and continues - even if it had already handed the chat back to you. A running job can no longer be forgotten.

• One question, one answer. A message sent at just the wrong moment no

longer risks two competing replies.

When something has to reach your phone - opening your app in Expo Go, checking a preview on a real device - the assistant now draws a QR code in the chat instead of asking you to type a long address across two screens.

• The address stays printed under the code as selectable text, so on a desktop

you can still copy it in one click.

• The code carries the Playcode mark in the middle, and it is rendered to be

scannable rather than decorative: it sizes itself to the address it holds, and in a column too narrow to scan from it steps aside and leaves you the text.

• It works the same in dark and light themes.

Only for addresses that genuinely have to cross to another device. A link you can simply tap stays a link.

If you were signed in but arrived on a device or browser Playcode had never loaded before - a new laptop, a cleared browser, a private window - opening a template link directly (/javascript-template and friends) could leave you staring at an empty editor: no files, no preview, no menu. Reloading did not help.

The editor was starting before your account finished arriving from the server, and then quietly gave up. Two things changed:

• The editor no longer waits on that data to build your project, so a first

visit on a new device opens the same way a returning one does.

• If an open genuinely fails, you now get a clear message with a Retry button

instead of a blank page.

When you upgrade to Max, every project you already have now moves to the larger Max machines automatically - 8 CPU · 16 GB in the editor and bigger production machines with a 200 GB disk - not only the projects you create after upgrading.

• Projects that are asleep pick up the new hardware silently and wake up on

it the next time you open them.

• An editor you are actively using switches on its next idle pause, usually

within minutes.

• Published production apps pause briefly - usually seconds, at most a couple

of minutes - while they move to a bigger machine.

And if you ever move back to Pro: CPU and RAM return to Pro sizes, but any disk space you grew into stays yours. We never shrink your disk.