Changelog

Your workspace credits are now one balance for everything Playcode runs for you. Until today only the AI chat and agents drew credits.

• Cloud computers use credits while they are awake, for the disk they

keep, and for traffic beyond the included amount. A sleeping computer bills disk only. Each computer's rate is shown next to its hours in Settings > Usage.

• AI in your apps - requests your apps make through the AI Gateway with

their secret key - use credits too, at the model's rate.

• Email beyond your plan's included sends keeps its per-email price.

Settings > Usage now shows all spending in one place: AI chat + agents, one row per project whose apps used the AI Gateway, Email, and one row per cloud computer, each with quantity × rate = credits. The period buttons at the top drive the whole page - today, this week, this month, all time - and the spending list names the period beside its total. Email alone is shown per billing cycle, because its included sends are a cycle allowance.

If your credits run out, AI requests pause until you add credits. Email beyond your plan's included sends is stored but not delivered until you do; included sends and mail to your own team always go out. Cloud computers keep running: we email you, and only if the balance is still empty 72 hours later do they pause. Nothing is deleted, and the same computers start again as soon as credits are added.

Nothing changes about how you buy credits, and your balance shows the same number in the editor, in Billing and in Usage.

If you published an app, or created a new one, after your workspace moved to a paid plan, turning on Send to anyone in Settings > Email could be refused with a message saying the workspace needed a paid plan, even though it had one. The AI assistant repeated that message and suggested upgrading.

Every affected app is fixed, and new apps now start with email delivery matching your plan. If you saw that refusal, Send to anyone works now: turn it on in Settings > Email, or ask the assistant to do it.

Open a JavaScript, TypeScript, React, Python, SQL or any other language template and the code is the first thing you see: the file tabs on top, the file tree on the left, the AI Chat right under the editor, and the live preview with the console beside them.

Before, every template opened with the chat alone and the code sat a click away in the menu.

Website and business templates keep opening chat-first: describe what you want, and the preview updates as you go.

Google's permission screen lets you continue without ticking the Search Console box. Before, Playcode still showed the account as connected, and every request the agent made on it came back with a permission error.

Now that connection is refused on the spot, and the Connections page says which permission to select before you try again. A connection granted that way earlier is marked as revoked within a couple of hours, with the usual Reconnect button.

Mobile projects get a Phone tab beside Preview (View, then Phone; on the phone it is in the project menu). It shows your app the way a phone sees it, a QR code to scan with your phone's camera, and one line that says whether the phone preview is running. The QR opens the app in your phone's browser: nothing to install, no account. A Browser | Expo Go switch turns it into the native preview for Expo Go when you want that; Expo now asks for the same Expo account on the phone and on the dev machine, and the chat walks you through it. When you are already on the phone, the tab has an Open on this phone button, and the address in a chat card is a link you can tap.

Your dev machine now has its own address. Anyone you give it to can use the app while the machine is on: your phone, a teammate, a client on a call, a webhook you are testing. The machine stays awake while the app is in use from any device.

Only you can turn it on: opening the project in Playcode wakes it, and so does the agent while it works for you. It goes to sleep after a quiet while, and after four hours without you or the agent. When the app on your phone finds the machine asleep, it shows a banner with one button that opens the project and wakes it.

The address is not a public link. Publishing still is: a published app keeps its permanent link that works for everyone, whether your dev machine is awake or not.

Your Profile settings now list every browser you are signed in on - the browser and system, when it signed in, when it was last seen - with Sign out on each row and Sign out everywhere else in one click. Signing out really ends that session on our side, so a lost laptop stays out.

Sensitive actions - buying a domain, changing your sign-in email, creating or revoking a token - now ask you to confirm it's you with the sign-in code when it has been a while since you last did. Everyday work never asks.

In Workspace settings, Developers gained a Signed in as you list: the tools you let act as you through Sign in with Playcode, the workspace each one may act in, what it may do, and Revoke to sign a tool out on every computer at once. The project's Secret key pane replaces API keys: the key your app already has, masked, copied on purpose, rotated when it leaks.

When you add your own sending domain in Settings > Email, the DNS records now show every field in full: Name, Value and, for the MX record, Priority, each with its own copy button. Before, the name was cut off on screen and only the value could be copied, so the long DKIM names had to be retyped.

Copy all records puts the whole set on the clipboard as labelled text, for a note or for whoever runs your DNS.

If your domain's DNS runs at GoDaddy or Namecheap, the names are shown the way those providers' Name field expects them, without your domain at the end.

When you move a domain's DNS to Playcode, the certificate for the bare name now follows the nameserver change as soon as it lands, instead of up to an hour later. The check that decides it reads the registry itself on every pass.

Settings > Domains tells you exactly what that check saw: which nameservers answer today, which ones they must be, and when we last looked. The old sentence that promised a fix "within minutes" is gone.

"Finish setup" on a domain whose DNS moved here opens the same three-step switch the connect flow shows: the values to paste, what the world reports while the change spreads, and the done card once everything serves.

Moving DNS to Playcode keeps a www that already points at your Playcode site, and the review list says plainly when an unchecked record would leave a name unanswered after the switch.

Turning on Send to anyone in Settings > Email now applies to your Development and Production computers at once. Before, only the published app was switched on, so a test send from the editor could still be held while the page said delivery was live.

Mail that was held before you switched it on no longer sits there: every held address now shows a Deliver button as soon as your domain is verified and Send to anyone is on, including addresses that were never added to your verified recipients.

Your sending domain verifies within seconds of the records going live, with nothing to click. The assistant can check a domain for you too, and reads each email under the computer it came from.

Adding a customer's address to Verified recipients now warns you first: that list is for your own inboxes, and each add sends the person a permission request. Customers are reached through your own domain.

A cloud computer keeps up to 20 checkpoints you own. When the assistant reached that number it used to refuse to take a new one, and a schema migration could go in without a rollback point. Now, at the cap, the assistant replaces its own oldest checkpoint and tells you which one it replaced. The checkpoints you saved yourself are never the ones replaced.

If the Checkpoint history dialog cannot open, it now says why instead of staying blank.