Обновления

Full-stack apps on Playcode Cloud now send email out of the box - no provider signup, no API token, no DNS setup.

• Zero configuration. Password resets, verification emails, order

notifications: your app's email code just works. Playcode provisions the credentials automatically when your app is created.

• The Mailbox panel. Every email your app sends appears in the editor's

new Mailbox panel within seconds - rendered exactly as a recipient would see it, with working links. Trigger a password reset, click the link in the captured email, and complete the flow end to end without leaving Playcode.

• Safe by default. New apps run in capture mode: emails are stored and

shown to you, never delivered to real inboxes - so you can build and test freely. Real delivery to your users is coming next.

• API keys, done properly. The new Settings > API keys page manages

named keys with per-key permissions (send-only or full access), shown once at creation and revocable individually - and Settings > Email shows your sending mode and usage at a glance. A stuck loop that sends the same email over and over is paused automatically; one click resumes it.

Signing up is now one continuous flow instead of a series of popups.

• One setup journey. Answer a couple of quick questions right where you

signed up - no second dialog appearing later, no design jumps.

• Team setups land right. If you choose With my team, your company

workspace is created during setup and your first project is created inside it - together with your welcome credits. Working solo? Everything stays neatly in your personal workspace.

• Your work survives sign-in. Building something before signing up?

Your edits and drafts now survive signing in with GitHub or Microsoft, and your project is saved to your new account exactly as you left it.

Clicking Logout could quietly do nothing: the menu closed, no error appeared, and you were still signed in. It happened when Playcode was open in more than one tab - the sign-out waited on a local data cleanup that a second tab was holding, and then waited forever.

Sign-out no longer waits for anything. Your session ends the moment you click Logout, and the local cleanup happens afterwards where it cannot get in the way.

Two related gaps closed at the same time:

• Every tab. Logging out in one tab now ends the session in your other Playcode tabs too, instead of leaving them signed in with a session that no longer exists. A tab holding unsaved work stays put rather than reloading over it.
• Only your own data. Signing out used to try to clear the cached data of every account that had used the browser. It now clears only yours, so signing out of one account no longer disturbs another on a shared computer.

"How do I share projects with my team?" is the question we get most, so the Help Center now answers all of it - no support chat required:

• How to share a project - invite people by email

with Viewer, Editor, or Admin roles, manage the Access list, and use the public link. Fully rewritten for the current Share tab.

• Workspaces and teams - the difference

between your Personal workspace and a team workspace, inviting members, and granting access to a whole team at once.

• Roles and permissions - the full

reference: what each role can do in projects and workspaces, how overlapping access combines, and how invitations work.

• Move a project to another workspace -

bring existing projects into your new team workspace. Chats, data, and history travel with them; nothing needs to be recreated.

The Learn about sharing link in the editor's Share tab now lands on the rewritten guide.

If you work in a team workspace, the Home screen previously checked your personal credit balance - so it could warn "You're out of credits" even though your team workspace had plenty. Fixed:

• The right wallet. Home's composer now shows the credits of the

workspace your new project will be created in - the same number the workspace menu shows.

• The right button. "Top up" from Home adds credits to that workspace,

and team members without billing access see a note to ask a workspace admin instead of a checkout they can't complete.

• Warnings stay honest. Dismissing a low-credit warning in one

workspace no longer hides a real warning in another.

Every pending invitation in the Share popup now has a Copy invite link button. It copies the exact accept link from the invitation email, so you can send it over Slack, WhatsApp, or any other channel.

This helps when an invitation email gets caught by a spam filter or a strict corporate mail gateway: instead of re-sending the email and hoping, copy the link and deliver it yourself. The link is only visible to people who manage the invitation - the project owner and workspace admins.

Available in both the browser editor and the Cloud editor, on desktop and mobile.

When we ship a new build, Playcode offers to reload so you get it. That reload used to happen immediately - and if you had a browser project you hadn't saved yet, it went with the page.

Now the reload saves first. If you're signed in, your project is written to your account before anything else happens, and edits still syncing get a moment to land. If it can't be saved - you're signed out, for instance - Playcode asks before reloading instead of deciding for you.

Two related gaps closed at the same time:

• Other tabs. Reloading in one tab used to reload the rest instantly. A tab holding unsaved work now keeps it and waits for you.
• Closing or refreshing the page. The browser's "leave site?" warning now appears for an unsaved project on any exit, not only when moving between pages inside Playcode.

Projects created with the AI builder and Cloud projects were never affected - those save to your account continuously.

Picking a plan on the pricing page while signed out now opens a one-click sign-in right there - your chosen plan is saved server-side and checkout continues automatically the moment you're in. No more dead ends for visitors who weren't signed in, and subscriptions always land on your own account.

We also fixed a frustrating loss: if you typed a prompt and signed up mid-send, some paths could drop it. The prompt now survives sign-in everywhere - including sign-ins that reload the page - and lands back in your composer or sends as intended.

Payment flows no longer show the signup survey; it can wait until after you're building.

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.