更新履歴

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.

We reshaped the paid plans around one idea: a dollar buys the same 4 AI credits everywhere, and the plans differ in how much you get - not in what a credit costs.

• Pro is now one simple plan. $25/month, 100 credits, 3 full-stack cloud

apps, custom domains. No size picker - a heavy month is covered by top-ups.

• Meet Max (formerly Business). For people who need more of everything:

5 cloud apps, larger VMs (8 CPU · 16 GB editor), 1 TB/month bandwidth - and now with double the credits at the same prices. $100/month includes 400 credits, $200 includes 800, $400 includes 1,600, and new sizes reach $2,500/month with 10,000 credits.

• Top-ups are one rate for everyone. $1 = 4 credits on every plan, with

the same volume bonuses (+5% at $50, +10% at $100, +20% at $200).

Existing subscribers keep their current plan and price; Business subscribers get the doubled credits automatically from their next renewal.

Connecting a custom domain to a Cloud app now explains itself better - especially for root domains.

• Squarespace DNS is now recognized. If your domain runs on Squarespace

nameservers, the wizard shows the exact ALIAS record their panel expects.

• The wizard names your DNS provider. When a root domain can't point at

Playcode, the wizard now tells you which DNS service it detected and which nameservers prove it - no more guessing whether the check is right. This especially helps domains bought at Google Domains and moved to Squarespace, which often still run on Google's nameservers behind the scenes.

• Unknown providers are never a dead end. If we can't identify your DNS

host, the wizard now shows the ALIAS record to try instead of blocking you - and still recommends the www address that works everywhere.

Browser projects now have Checkpoints - restore points you can save at any moment and return to instantly.

• Save a restore point. Open the project menu and choose **Checkpoint

history, then New checkpoint**. It captures all your files exactly as they are - instantly, without using any credits.

• Name your checkpoints. Rename any checkpoint so "Before the redesign"

is easier to find than a date.

• Restore instantly - and undo it. Restoring puts every file back the way

it was. Playcode saves a safety checkpoint of your current state first, so a restore is never a one-way door. The page does not reload, and your chats stay exactly where they are.

• Publish keeps you covered. Every publish automatically saves a

checkpoint of what went live, so you can always get back to a published state.

You can keep up to 20 checkpoints per project. At the limit, Playcode asks before making room by deleting the oldest one.

Want to explore two directions side by side? Use Duplicate project - the copy gets its own files, chats, and published site.

Email on Playcode Cloud grows up: on paid plans, your app's emails are now really delivered - not just captured in the Mailbox.

• Deliver to verified recipients. Your own address works instantly (you

verified it when you signed up), and your team's addresses too. Add anyone else in Settings > Email - they get a verification link, and once they click it your app can reach their real inbox.

• Honest status on every message. Mailbox messages now show their real

fate: Sending, Delivered, Bounced, or Marked as spam - with the reason, so debugging "the email didn't arrive" takes one glance instead of guesswork.

• New apps send from day one. A fresh full-stack app now emails a

welcome message to its very first registered user - so you see your mail pipeline working before writing a single line of email code.

• Fair pricing. Emails to yourself and your team are always free.

Beyond your plan's monthly allowance, delivery is pay-as-you-go with credits - priced in line with the leading email APIs.

Free projects keep the full capture experience: every email lands in the Mailbox, rendered with working links, ready to test end to end.

Playcode can now build presentations, and it asks one question first: do you want a link you open in the browser and present fullscreen, or a .pptx file you download and edit? They are different things, so it settles that before writing a single slide.

The .pptx is a real one. Actual text boxes you can click and retype, real tables, real speaker notes, charts that carry their own data sheet. It opens in PowerPoint, Keynote and Google Slides, and Cyrillic, Japanese and emoji come out exactly as they went in. This is not a picture of a slide wrapped in a PowerPoint file, which is what most "export to PPTX" buttons hand you.

The more interesting version is a deck generator. Describe the presentation you rebuild every cycle - the monthly client report, the one-pager per prospect, the board update - and Playcode builds you an app that produces it. Your spreadsheet, database or CRM export goes in; finished decks come out, one or two hundred of them, on brand every time because the brand is written into the code. Next month you press the button instead of rebuilding the deck.

A few things worth knowing:

• Generating files needs a full-stack app, since a static site has nowhere to write one. Playcode will offer to set that up.
• Ask for both and you get both from one source: a browser deck to present from, plus a download. Change a slide once and both update.
• Slides use fonts that exist on the machine opening them, so nothing reflows into a substitute when you send the file to a client.