Changelog

Site subdomain names now use hyphens (my-app.playcode.site) instead of underscores. Underscores are not valid in web hostnames, so my_app.playcode.site could never load in a browser - the editor just didn't tell you. Every published site with an underscore name has been renamed to its hyphen twin automatically, old underscore links now redirect permanently to the new address, and your numeric address keeps working as before.

GLM 5.3 Flash is now in the model picker. It is one of the cheapest models we offer, with reasoning quality close to models many times its price, a 1M-token context window, and image understanding. It thinks before every answer, so it is thorough rather than instant - pick it for budget builds where a little patience is fine.

Since March, signing in with GitHub or Microsoft from the Playcode sign-in or sign-up page brought you back to that page, even though you were already signed in. From September 17 to 28 the same buttons led to an error page instead. Both are fixed: you now land in Playcode.

If you started signing up with your email and never finished, signing in with GitHub or Microsoft now finishes it, as long as that account uses the same email address and GitHub or Microsoft has confirmed it.

Your apps and your tools can now talk to Playcode directly - three releases in one day:

• @playcode/sdk 0.3 (npm) - the official SDK for your app's backend. Zero dependencies, fully typed, works in any Node or edge runtime. Send email, call every management operation, and - new today - generate images: pc.media.image({ prompt }) returns a finished image hosted on Playcode, paid per image from your workspace credits. Video generation (pc.media.video()) rides the same way.
• @playcode/cli (npm) - npm i -g @playcode/cli, then playcode login signs in through your browser. List projects, read and run things on a project's computer, publish, and reach every management operation as playcode <family> <operation> - new operations appear in the CLI the moment they exist, no update needed.
• An MCP server for your coding agent. playcode mcp runs a local MCP server over your own sign-in, built for Claude Code, Cursor, and Claude Desktop: your agent discovers Playcode operations by searching, reads the exact argument shapes, and executes - with everything scoped to the permissions you granted at sign-in.

New projects created from today's template get the SDK preinstalled. This is the start of the platform surface - more capabilities land on the same three doors.

Claude Sonnet 5.5 - Anthropic's newest Sonnet, "the best combination of speed and intelligence" - is now on the Quality chip in the model picker, at the same price as Claude Sonnet 5. Sonnet 5 is superseded; if you had it pinned, your pin keeps working.

AI used inside your hosted apps is now priced per model, exactly like the in-chat prices - one price book everywhere. Most models move to the standard rate; the flagship cards keep their premium pricing unchanged.

For almost two weeks, starting September 16, signing up with email on the Playcode website did not work. Sign-in codes had just become six digits long as part of a round of security hardening, and the code box on our website still accepted only five. The last digit was cut off, so the code could never go through. Sign-up inside the app was not affected.

It's fixed. If you tried to sign up in those days, go back to playcode.io and use the same email. The code works now.

We're sorry. Our automated tests missed this because they still typed an old five-digit test code. They type six digits now, the same as you.

One less switch to find. When your app's sending domain verifies, Send to anyone now comes on with it - your app can email customers right away, from your own domain, with one-click unsubscribe on every mail to a non-member. Before, verified-domain projects still had to discover the switch in Settings > Email; every one of them turned it on.

The switch stays where it was, as the off lever: turn it off and it stays off - for every app of the project, including ones created later. Nothing else changes: without a verified domain, delivery still goes only to recipients who confirmed their address, and the daily caps, suppression and unsubscribe protections run exactly as before.

We chased down a family of rare but painful loading failures - the kind where Playcode showed a spinner and simply never finished. All fixed today:

• A freeze on certain networks and privacy settings. A stylesheet request could block the whole page from rendering on devices where third-party requests hang. Pages now render regardless, every time.
• The editor recovers stuck browser storage by itself. If your browser's local database wedges (an old tab holding a lock, strict privacy modes), Playcode now detects it in seconds, repairs it, and continues - your work lives on our servers, so nothing is lost.
• The preview says so instead of spinning. If the preview engine can't start on a slow connection, you now get a clear retry button within seconds instead of an endless spinner.
• Clearer sign-in errors. If an ad blocker or filtered network breaks Google sign-in or the human-check, the dialog now tells you what to do instead of silently resetting.

If loading ever felt stuck for you before - it wasn't your device, and it's fixed. Thanks to the users whose reports led us straight to it.

Your server can now hear Playcode. In Workspace settings, Developers gained Webhooks: add an endpoint and we POST every matching event to it - a domain changed, a publish started, mail delivered or bounced. Every delivery is signed with a secret we show you once; verify it, and replay protection comes from the delivery id. Failures retry on their own for about three days, and Send again runs one now. Filter by type, like domain.*, or take everything.

Beside it, Activity: every write in the workspace, the moment it happens - who did it, through which door (the app, the CLI, the API, an assistant), and what it touched. It is the audit answer for a token or a tool you let act as you.

The same ledger is on the API as eventSearch, so a script can follow your workspace with a cursor instead of polling each resource.