Changelog

Workspaces now have teams - named groups of people you can share with in one step.

Create a team from Settings -> People -> Teams and add workspace members to it. Then, in the Share popup, grant access to the team the same way you would to a person: everyone in the team gets that access at once.

Teams stay live as your group changes. Add someone to a team and they immediately get everything the team has been given; remove them and that access goes away just as fast. No more re-sharing a dozen projects when a new person joins.

The Share popup shows exactly where access comes from: grants received through a team are labeled "via team", and the team's access level is edited in one place - on the team grant itself. A direct personal share and a team share can coexist; the more permissive one wins.

A workspace is no longer tied to the one person who clicked "Create".

Any number of admins. Promote as many teammates to admin as you need - every admin can manage members, sharing, settings, and billing with equal rights. There is no single "super owner" anymore; the person who created the workspace is simply its first admin.

Ownership is transferable. Handing a workspace over is now just a role change: make the new person an admin, and they can take it from there - including if the original creator later leaves the company. Playcode always keeps at least one admin in place, so a workspace can never lock itself out.

Nothing changes for your personal workspace - it stays yours.

Give a teammate Admin on a single project and they can now run it end to end.

Publish, snapshot, restore. A project admin can publish and unpublish the project, create and restore checkpoints, retry provisioning, and manage its published subdomain - without needing to be a workspace admin.

Destructive actions stay protected. Deleting or moving a project, and attaching custom domains, still require the project's creator or a workspace admin. So you can hand someone the keys to operate a project without risking that it gets erased or relocated.

Workspaces now have their own billing. A team workspace can subscribe to Pro or Business, buy credits, and manage its payment method - independently of anyone's personal plan.

Every workspace has its own credit balance. Work done in a team project uses the team's credits, not yours - and a teammate on a free personal plan gets the full power of the workspace's plan while building there, including the best AI models. Your personal workspace keeps its own plan and credits, exactly as before.

Everyone sees the team's credit meter. Members can always check how many credits the workspace has left and when they refresh. Payment details stay private: only the workspace owner and admins can see the card, change the plan, buy credits, or configure auto-recharge - members who run low see who to ask instead of a dead end.

Upgrading is contextual. Open pricing from inside a team workspace and the subscription goes to the team; open it from your personal workspace and it's yours. Each workspace gets its own invoices and billing portal.

Existing subscriptions carried over automatically - if you were subscribed, your personal workspace has the same plan, credits, card, and invoice history as before, with no action needed.

Playcode now has workspaces - shared spaces where your whole team builds together.

Create or switch workspaces from the main dashboard menu and invite teammates by email - they don't need a Playcode account yet; the invitation walks them through signing up. On phones, projects, folders, and the workspace menu share one sidebar, so navigation never stacks drawers. Everyone in the workspace sees its projects live: when a teammate creates or edits a project, it appears for you in real time.

Sharing got personal, too. The Share popup in the editor now works the way you'd expect from tools like Notion: type an email, pick a role (Viewer or Editor), and that one person gets access to that one project - whether or not they're in your workspace. Projects shared with you show up in a new "Shared with me" section in the sidebar.

Viewer access is consistently read-only across code, chat, publishing, and Cloud controls. Editors can change project content without receiving owner-only sharing or lifecycle controls, and any direct collaborator can leave a shared project from the Share popup.

Each workspace has its own settings area: manage People (roles, pending invitations), rename or leave the workspace, inspect Usage per member, and open Billing as its own section. Owners and admins can filter usage by period, inspect individual AI requests, and understand input, output, and cache credit use. Billing controls stay role-aware: owners and admins manage the workspace plan while members get a clear read-only explanation. Paid features and Upgrade prompts follow the active workspace, so teammates receive the plan their team is actually paying for.

Your personal projects are untouched - everything you've built lives in your personal workspace, exactly as before. And when a project should belong to the team, Move to workspace in the project menu brings it - chats, history, and all.

Playcode's AI model picker just got the newest models from OpenAI and xAI, plus a cleanup so the list stays easy to choose from.

OpenAI GPT-5.6 arrives as three tiers you can pick per task:

• GPT-5.6 Sol - the flagship. Highest quality of the family, for the hardest builds.
• GPT-5.6 Terra - the balanced everyday pick. GPT-5.5-level quality at lower credit use, so it's the new default GPT for most work.
• GPT-5.6 Luna - fast and light. Great for simple pages and quick edits where you'd rather iterate than wait.

Grok 4.5 from xAI joins too - an "Opus-class" model that's fast and unusually token-efficient, so long AI builds tend to cost less.

Each model's picker badge reflects its expected credit use, so you can trade quality for cost with your eyes open. Start on Terra, reach for Sol when a build is genuinely hard, and drop to Luna or Grok 4.5 for quick, cheap passes.

We also retired older models from the picker (earlier GPT-5.x, Grok 4.1, and a few others) so the choices you see are the ones worth using. Nothing you've already built is affected.

The projects dashboard now lets you work on many projects at once - a real help once you have more than a handful.

On desktop, drag a box across empty space to rubber-band a group of projects (it auto-scrolls when you reach the edge), or hold Shift to extend a range. On a phone, tap the checkbox on each card. Once you've selected some, a bar appears with the actions that fit: Move to folder, Archive, or - for already-archived projects - Restore and Delete permanently.

We tidied the dashboard around it, too. Each card now shows whether it's a Static or Cloud project, the filter row carries live counts for your Cloud usage and your Archive, and the views - All, Live, Drafts, Cloud, Archive - moved into one clear switcher at the top while the sidebar stays focused on your folders.

Ask Playcode's AI to check your site's speed and it now runs a real Google PageSpeed Insights (Lighthouse) audit on your live page - the same signals Google uses to rank sites.

You get your Performance, Accessibility, Best Practices, and SEO scores, your Core Web Vitals (Largest Contentful Paint, Cumulative Layout Shift, and more), and a ranked list of concrete fixes with estimated time savings. The AI can measure, apply improvements, and measure again to prove your site actually got faster.

Publish your site first, then just ask - for example, "How fast is my site, and how do I speed it up?"

It's a step toward Playcode helping your site succeed, not just get built: fast pages that are ready for Google, all in the same chat.

We rebuilt the storage system behind Playcode Cloud - the layer that keeps your full-stack app's data and files safe while it runs.

The payoff is more predictable performance and stronger reliability, especially for apps that read and write a lot of data. Most of it is invisible by design: your app just runs more smoothly, with fewer surprises under load.

Nothing to change on your side. Existing Cloud apps get it automatically.

Your Cloud terminal now keeps running as long as its tab is open.

Before, switching to another tab and back would drop the session and start a fresh shell - losing whatever was running and your command history. Now you can move between the terminal, preview, and AI Chat freely: the terminal stays connected in the background, and switching back brings you right back to the same session, scrollback and history intact. Dragging the terminal to another panel keeps it too.

Closing the terminal tab still ends the session. And if you leave the whole app for a while, idle terminals disconnect on their own to keep things tidy - reconnecting the moment you come back.