Changelog

Converting a browser project to a Cloud full-stack app no longer fails when the project carries a large media library.

Projects with many hundreds of images could get stuck at the import step with an unhelpful error, and retrying or restarting the project computer never helped. The importer now transfers big asset sets reliably, and if anything does go wrong during a conversion, the error now names the actual cause instead of a generic failure - so the AI can fix it or route it to us with real detail.

Your signed-in home is rebuilt. Instead of a grid of files with a second, weaker prompt box, Home is now the place you build: a short greeting and the exact same composer you use inside the editor. From the very first screen you can attach files, use your voice, and pick your model and effort - no more stripped-down starter prompt.

• One composer everywhere. The box on Home and the box in the editor are the same tool. Whatever you can do in a chat, you can do the moment you arrive.
• Always know where your message goes. A small target chip on the composer shows whether your prompt will start a new project or continue an existing one. If you have a single project, it points there by default; one tap switches it - so a quick change request never spawns an empty project by accident.
• A project sidebar on every screen. Your projects, their chats, and folders now live in one collapsible sidebar. Open any project or jump straight to a past chat in a single click, drag a project into a folder, and reorder folders to taste. It stays put as you move between Home and the editor, so you never lose your place.
• A template gallery when you want it. "Or start from a template" opens a browsable gallery of ready-made site templates, with coding templates - React, Vue, plain JavaScript, and more - one click away. It is opt-in and never gets in the way of just describing what you want.
• A dedicated Archive. Archived projects have their own page with bulk restore, keeping your active project list clean.
• An editor that earns its chrome. A brand-new project opens clean and quiet. Share, Publish, and other controls appear as your project becomes real - once you have actually built something worth sharing - so the toolbar teaches you the workflow instead of overwhelming you on day one.

Old links to your dashboard bring you straight to the new Home, so nothing you had bookmarked breaks.

Cloud publishing got a stronger guarantee: Publish deploys the exact code that is in your workspace at the moment you press the button - every time, no matter what the AI has been doing with Git behind the scenes.

Previously, if the AI organized its work into a Git branch, a publish could quietly ship an older version of your app, or fail repeatedly with a cryptic Git error that retrying never fixed. That whole class of problems is gone:

• What you see is what ships. Publish captures your current workspace state as a single immutable version - unsaved edits included - and deploys exactly that. Branches, background commits, and Git bookkeeping can no longer change what goes live.
• Every publish shows its source. The publish dialog and history now identify each attempt by its branch and version - so "what exactly is live right now?" always has a clear answer, for you and for the AI.
• Honest errors instead of retry loops. In the rare case your workspace is genuinely out of sync with the published history, Publish stops before touching production and explains what happened in plain words - your live site stays untouched, and the AI can see the same explanation and fix the mismatch for you.

On desktop, the editor no longer carries a top navigation bar. The space it used to take now belongs to your work.

• The project menu moved into the panel row. Rename, settings, and everything you used to reach for up top now sit right next to your tabs, where the rest of your project controls live.
• Publish rides the preview toolbar. The Publish button is now on the preview, exactly where you are already looking when you are ready to ship.
• A taller canvas and a calmer screen. Fewer bars competing for attention means more room for your code and your live preview, and the controls you need are next to the work instead of parked at the top.

Nothing was taken away - every action still has a home, just a better one. On phones and tablets the familiar top bar stays, so smaller screens are unchanged.

The template gallery is now fully stocked. Open "Start from a template" and you land in a browsable library of ready-made starting points - more than 50 of them - so you rarely have to begin from a blank screen.

• Site templates for landing pages, portfolios, and other static sites you can publish as-is and then reshape by describing the changes you want.
• Coding starters for full-stack apps - React, Vue, plain JavaScript, and more - including clean Empty starters for when you want the framework without any demo content.
• Ready in every language. The whole gallery is translated, so template names and descriptions read naturally across all of Playcode's supported languages.

Pick one and you are in the editor with a working project in a single click.

The top of the sidebar now holds a workspace switcher. Your personal space and any team workspaces you belong to are one click apart, and the switcher always shows which one you are working in.

Your account controls moved in behind it - profile, plan, and workspace settings now live under the switcher instead of being scattered around the screen. One tidy corner tells you who you are and where you are building, and gets you between workspaces without hunting for a menu.

On desktop, each project in the sidebar now shows a thumbnail - a screenshot of the project itself - so you recognize the one you want by sight instead of reading down a list of names.

Hover a project and a larger preview pops up, giving you a fuller look before you open it. Finding the right project across a long list is now a glance, not a hunt.

The project sidebar is now resizable. Drag its edge to make it as wide or as narrow as you like, from a slim strip to a roomy panel. Double-click the edge to snap back to the default width.

Playcode remembers the width you chose and brings it back every time you return, on every screen.

Settings is now one word. Everything that used to hide in the Preferences and Appearance menus - theme, language, editor options, AI defaults - lives in a single Settings modal you can open from anywhere.

The modal is grouped by scope, so it is always clear who a setting affects:

• Project - name, archive, publish address and custom domains, plus how the project runs: watermark, live reload, SPA mode, live view delay, loop protection, and production build options. This group appears when you open Settings from inside a project.
• You - profile, appearance, editor preferences, and your AI defaults (model tier, effort, context, voice input). These follow you across all workspaces.
• Workspace - general settings, people and teams, billing and plans, usage, and the affiliate program.

Two behaviors worth knowing:

• A chat keeps whatever quality settings you give it; a new chat starts from your defaults in Settings.
• To make the current chat's setup your default, use Set as my default right in the build-quality dialog - one tap, no extra dialog.

The project menu now holds only actions. Every knob has a home in Settings.

Playcode now asks for confirmation before you increase context above Medium, switch to Ultra, or move from a stronger model to Economy.

Each dialog explains the practical trade-off without discouraging the choice. Economy highlights lower credit use and explains what to do if a complex task starts repeating; larger context and Ultra explain their higher credit use. Re-selecting the current mode, lowering context, or leaving Ultra remains immediate.