Docs / workspace

The workspace

The workspace is the page you build on: chat on the left, your running app in the middle, your code on the right. Here is what every panel and control does.

Three panels

Open a project and you get three columns:

  • Chat on the left — your prompts and everything the AI did about them.
  • The center panel — your app running, plus the design and mobile views.
  • Code on the right — the files the AI wrote. It starts collapsed.

Drag the divider between two panels to resize them. Every panel header has a fullscreen button that expands that panel over the whole workspace; press Esc to go back to three columns.

The code panel is collapsed to a narrow rail on the right edge, labelled Code. Click the rail — or the Code button at the far right of the status bar — to open and close it.

Panel widths and whether the code panel is open are remembered per project, in the browser you are using.

The center tabs

Preview is the default view. A tab strip appears in the panel header as soon as there is more than one view to switch between:

TabWhen it appears
PreviewAlways — your app on a private dev server
DesignOnce the project has a design round, from the first proposal onward
MobileOn every project, including before a mobile app exists

The panel also switches tabs by itself at the moments that matter: it moves to Design when the AI proposes screens or starts drawing mockups, and back to Preview once you approve a design and the build begins. You can switch back by hand at any point — an automatic switch only happens when the design phase changes.

The chat panel

The panel header shows your credit counter for the current period, in the form 12.4 / 150 credits.

Below it is the thread. Each prompt gets its own block with a status badge, a live activity list while it runs, and a cost chip when it settles. Steps of a plan are nested inside the plan they belong to rather than listed flat. The thread follows new output automatically, unless you have scrolled up to read something.

The composer sits at the bottom, with the Ask first and Design first toggles, the model chip, and the paperclip for attachments. When your allowance is used up the composer is disabled and reads Out of credits this period — unless you are holding top-up credits, which keep paying and leave the composer open.

If the live connection drops you can still send prompts — only the streaming updates pause, and they resume when the connection returns.

The code panel

The file tree is on the left, the viewer on the right. Click a file and it opens as a tab; several tabs can stay open at once.

The viewer is read-only. There is no editing and no right-click menu — code changes go through a prompt, or through exporting the project and working locally.

The tree refreshes itself when a run finishes, so files the AI just wrote appear without a reload. Files a later prompt deleted drop out of the tree and close their tab.

Some files cannot be shown: anything over 512 KB reports File too large, and binary files (images, archives, compiled output) report Binary file. Both still exist in your repository — they are only unviewable here.

The header

On the left: the Poleved mark and the Projects breadcrumb return to your project list, and the project name is a dropdown that switches between your recent projects. Projects created from a scaffold also show a small scenario chip.

On the right, everyone working on the project gets:

  • A Live badge when the project has a live deployment.
  • A database chip (Postgres or MySQL) linking to your database, when the project has one.
  • Deployment history and Collaborators icon buttons.
  • The Publish button, and an avatar menu with Rename / edit and Settings.

Some actions are owner-only: Export, the Showcase button, Download ZIP, and Delete project. If you were invited to the project you see an Editor badge in the header instead, and those controls are absent.

When someone else has the project open, their avatar appears beside yours. It grows a pulsing ring while a prompt of theirs is running.

The status bar

The thin bar along the bottom reports your build environment, the git branch (always main), the runtime, the file count, the tokens used today, and how long ago the project was last deployed. The Code toggle sits at its right end.

Limits & notes

  • The workspace needs a screen at least 1080px wide. Below that you get a notice instead of the three-panel layout — it is not usable on a phone.
  • The code viewer is read-only, and skips files over 512 KB.
  • Panel sizes are stored in your browser, so they do not follow you to another device and are not shared with collaborators.
  • The preview in the center panel is private to you and is not your public URL.