Changelog

Two billing fixes for existing subscribers. Opening the Billing Portal silently failed on mobile (it worked on desktop) - the link is now opened in a way phones don't block. And changing your plan (for example Pro → Business) no longer dead-ends on "redirecting to secure payment" - subscribers are now sent to the billing portal's plan switcher.

Fixes

• Billing Portal opens on mobile - previously nothing happened on phones; the portal now opens reliably
• Plan upgrades work for current subscribers - switching plans routes to the billing portal instead of failing

When Playcode's AI takes on a multi-step job (setting things up, running your tests, building, or publishing), it now tells you what it's doing in plain language as it happens, instead of showing raw technical output. You'll see what it's checking and why, like "Are there already settings files here?", and how a longer step is going, like "Tests about halfway, passing so far", so you're never left watching a blank, frozen screen.

On longer jobs the AI now works more like a teammate at the keyboard: it starts the step, keeps an eye on it, and gives you a quick read every few seconds, flagging early if something looks stuck instead of going quiet until the very end. Clearer, simpler, and written for founders, not engineers.

Sites served on your own custom domain now load over HTTP/2. Browsers can fetch many files at once over a single connection instead of requesting them one after another, which is the same modern protocol your visitors already get on Playcode subdomains.

The effect is most noticeable on mobile, where pages have many scripts and styles to load. In our mobile testing on a custom-domain site:

• Mobile Lighthouse performance: 73 → 85
• Largest Contentful Paint: 4.7s → 3.5s

No setup is needed. Every site published to a custom domain on Playcode Cloud gets this automatically.

Cloud publishing now observes deploy logs in short, bounded checks instead of waiting on one long-running server step. This helps the publish dialog keep up with newer publish and rollback activity, especially when a build step is quiet for a while.

If a publish is cancelled or a deploy step takes longer than expected, Playcode can now notice follow-up publish activity faster instead of appearing stuck with no output.

Cloud project previews now come back much faster after they have gone idle.

For projects with a warm snapshot available, Preview can wake in about 1-2 seconds instead of waiting for a full cold start that can take about a minute. That is up to around 60x faster when you return to a recent Cloud project.

This is most visible when you are iterating on a full-stack app: open the project, wait for Preview, make a change, leave it idle, then come back later. Playcode can now resume the working project state instead of rebuilding the whole dev environment every time.

If a project needs a clean start, for example after an infrastructure update or an expired snapshot, Playcode falls back to the slower cold start path so the project still opens correctly.

GLM 5.2 is now selectable in Playcode's AI model picker. It replaces GLM 5.1 in the visible picker and gives you a newer long-context reasoning option for code-heavy tasks.

Choose it from Menu → Preferences → AI Model when you want to compare GLM against your usual model on the same project.

GLM 5.1 is no longer shown in the picker. Existing history remains intact, and the newer GLM 5.2 option is the one to use going forward.

We fixed a caching issue that could keep the Preview showing old CSS after you changed a cloud project. Cloudflare was telling browsers to keep some Preview stylesheets for too long, so a normal reload could bring back stale styles instead of the latest version from your project.

New Preview requests now respect the project server's cache headers, so CSS changes refresh normally.

If your browser already cached the old response, clear it once: open the affected project or folder, open the browser developer console, go to the Network tab, turn on Disable cache, and reload the page. After that one reload, the stale Preview cache is cleared and future updates should work normally.

Playcode now gets to the usable editor faster. We split more of the heavy editor code into lazy-loaded pieces, load only the current language by default, and delay expensive startup work until the interface is already responsive.

Preview starts more gently. The browser no longer has to spin up the preview worker, bundler, and Service Worker immediately on page load. If you press Run, Preview still starts right away. If you just open a project and begin typing, the heavy work waits briefly so the page stays smooth.

Preview is also more reliable in embedded browsers. Playcode now checks for blocked browser features like Service Workers, cache storage, IndexedDB, cookies, and local storage. When a browser blocks something Preview truly needs, you get a clear message instead of a blank panel or a forever-loading iframe.

Sign-in and onboarding got a cleanup pass. The auth screens are cleaner, Google sign-in fallback behaves better when a browser blocks it, and new users get a smoother first-run flow before landing in the editor.

We also tuned the marketing homepage video so it waits for real user intent instead of competing with the first paint, which makes the first screen feel less stuck on slower devices.

You can now invite friends to Playcode and both of you get credits. Your friend receives 10 welcome credits the moment they sign up with your link, and you receive 40 credits when they subscribe.

Find your personal invite link in the project menu, right under your credits meter. You have 3 invite passes; every time an invited friend subscribes, one pass comes back, so your best invites never run out.

The invite dialog shows who joined and what you have earned, with friends' emails masked for privacy.

Usage History now shows where every AI credit goes. Click the info icon on any row for a full breakdown: input, output, and cache tokens, each with its own credit cost.

It answers the question we hear most: why did a short message still cost credits? The first message in a chat saves your whole prompt and tools to cache once (that is the big number), and every later message reuses it at a large discount. Now you can see exactly that.

The activity list also got a proper Load more button and a running count of how many records you are viewing, so you can browse your full history.