更新履歴

If your first publish failed, the project could be left unable to publish at all: pressing Publish again would stop immediately, and the project card kept showing "Publishing..." forever. That is fixed. Every publish attempt now ends in a state you can act on, so you can always fix your app and publish again.

When a publish fails its health check, we also now show you your app's own startup log with the error. That is the part that actually explains the failure: your code deploys fine, but the app's server does not come up, so the published URL never responds. Previously that log was not kept, and the deploy log looked clean because the deploy itself had succeeded.

Two related improvements: the publish progress window no longer blocks the editor, so you can keep working while a publish runs or close it if something goes wrong. And if a publish is interrupted and left behind, we now clean it up automatically instead of leaving the project stuck.

If a health check keeps failing, check that your app listens on the path set as healthcheck.path in playcode.yml, or point it at a path your app actually serves.

New subscriptions now start with monthly billing selected, so the first payment matches the monthly price shown in Playcode. Annual billing and its savings remain one click away.

Stripe Checkout also no longer requires everyone to fill in a full billing address. It asks for address details only when they are needed for the selected payment method or tax rules, while the optional business-purchase and tax-ID fields remain available.

The upgrade summary now also names Claude Opus 4.8 correctly as the default Quality model.

Sharing an editable link from a Pro workspace now works the way it should: any number of collaborators can join at the same time, and they do not need a Playcode account - opening the link is enough.

Previously, collaborators who were not signed in could be turned away with a "collaboration limit reached" message even when the project owner was on Pro. That check now runs on our servers against the project's actual plan, so it can no longer misfire.

Free projects keep the existing limit of 2 people at once, and the project owner now sees a notice when someone was turned away - the AI agent working in your project no longer counts toward that limit.

The Quality build tier now runs on Claude Opus 5 by default - Anthropic's newest Opus, with noticeably sharper reasoning on multi-step build and edit work. New chats on Quality pick it up automatically; no setting to change.

Opus 5 thinks before it answers, so expect it to spend a little longer - and a few more credits - on hard tasks than the model it replaces. Claude Opus 4.8 is still one click away if you want the leaner option for everyday pages.

Switch any time in the Choose build quality dialog, or set your account-wide default in Settings -> AI defaults.

When you switch your project's shared link from "can edit" to view-only, everyone who already has the project open now loses edit access within a second - their editor switches to a read-only state with a clear notice. Turning editing back on unlocks connected visitors just as instantly.

Previously the toggle only applied to people who opened the link *after* the change: visitors who were already connected could keep typing until they reloaded the page, which made the setting look broken.

Opening a shared project link without signing in now gives you a way to browse the whole project, not just the files the owner happened to leave open.

The project menu has a new Files entry under View. It opens the file tree in a panel on the left - click any file to open it, exactly like the project's members do. Close the panel with the x in its corner and reopen it from the menu any time.

On read-only links the tree is view-only: you can open files, split the editor, and copy paths, but options that would change the project - creating, renaming, moving, or deleting files - are not shown. Links that allow editing keep the full set.

Kimi K3, Moonshot's flagship model, is now available in the Choose build quality dialog. It brings a 1M-token context window, always-on reasoning, and vision - so it can hold a very large project in context, think through multi-step changes, and read the screenshots or mockups you attach.

Pick it per chat like any other model, or set it as your account-wide default in Settings -> AI defaults. It is a strong fit for large builds where the whole codebase matters.

The Quality build tier now runs on Claude Opus 4.8 by default - our strongest all-round model for building and editing apps. New chats on Quality pick it up automatically; no setting to change.

Prefer a different model? Every option is still one click away in the Choose build quality dialog, and your account-wide default lives in Settings -> AI defaults.

The model you pick in the Choose build quality dialog now applies to that chat only. Open another chat, pick a different model, and run them side by side - one choice no longer follows you across every conversation.

Your account-wide defaults still live in Settings -> AI defaults, and the Set as my default row in the dialog now promotes your current models too, along with mode, effort, and context.

Published browser projects are now served from yourproject.playcode.site (previously on playcode.io). The new address shows up in the editor and dashboard, ready to copy and share.

If you shared an older playcode.io project link, visitors now see a short notice pointing them to the new .site address - reshare the new link wherever you posted the old one. Custom domains you've connected are unaffected and keep working as-is.