Skip to main content
The right side of the chat window is the workspace. It is not one fixed area but a set of tabs that coexist — panels appear on their own as the expert works, and you can open the ones you need yourself.

​
The panels

The ”+” menu offers Trajectory, Files, Preview, Browser, and Video — plus Code on desktop. The rest are triggered by specific actions.

​
The preview panel

The one you will open most often while building a site.
The panel does not start the dev server. The only entry point for that is the expert’s website_init tool (lazy start — if you are not building a site, you never pay that cost). The panel’s job is to obtain the URL and display it.

​
Startup sequence

On mount the panel probes the current port (5173 by default). If the probe returns ready, that URL is used. Otherwise it issues a start request. Failures split into two classes: Auto-retry runs at most 3 times, 2 seconds apart. While retrying you see “Still starting (check N/3)…”. Once running, a drift guard keeps watch: a heartbeat every 20 seconds, with probes no more often than every 15 seconds, confirming the iframe is still serving your project.

​
States you will see

One sandbox holds one preview at a time. Multiple site projects in the same session will displace each other — that is where “Preview is in use by another project” comes from. It is not a fault.

​
The files panel

Lists every file in the session by category (sheets, slides, documents, code, images, video, music, audio, data, other) and distinguishes source: uploaded by you versus delivered by the AI. Each file can be downloaded, previewed inline, copied, opened in a new window, and inspected for version history. You can also select text and quote it straight back into the chat.

​
Types with inline preview

Office preview boundaries: Office Online rendering is tried first and falls back to a local renderer after 8 seconds without a response. Size ceilings: 5 MB for xlsx, 10 MB for other Office documents — anything larger goes straight to local rendering. PDFs never use Office Online (Microsoft retired that capability) and always render with pdf.js.

​
The widget panel

Opens automatically when an MCP plugin returns a result with a UI. You can also reopen it from the “Open widget” button on the tool card. Widget content is sourced by a four-level priority:
  1. Live sandbox URL — the real-time address while the session is alive
  2. Object storage URL — HTML over 256KB is persisted and served through the /storage/ reverse proxy
  3. Content reference — a server-relayed fallback path
  4. Inline HTML — small HTML embedded directly
Widgets always render with sandbox="allow-scripts" and never allow-same-origin. The object-storage path shares an origin with the main site, so granting same-origin would hand your main-site cookies to a third-party widget. The trade-off: widgets cannot use browser local storage — when they need persistence they call MCP tools to write sandbox files instead.
Loading past 60 seconds shows “Widget is taking too long to load”. With no active widget, the panel reads “Widgets appear when an MCP tool with UI is called”.

​
The browser panel

This shows the remote view of the isolated browser inside the sandbox (the one the profy-browser plugin drives), not your own Chrome. The browser stack starts automatically when the panel mounts with an available sandbox, and you get an address bar plus navigation controls. Without a sandbox it reads “Sandbox not ready, start a conversation first”.

​
Panels and the sandbox lifecycle

Nearly every panel depends on a live sandbox. Sandboxes are reclaimed after 15 minutes idle, after which:
  • The preview panel must be restarted
  • Files that only existed in the sandbox are inaccessible
  • The browser panel must be brought back up
If an artifact matters, have the expert deliver it to the cloud. Cloud-uploaded files remain downloadable from the files panel regardless of sandbox reclamation.

​
Keep reading

Sandbox

Sandbox lifecycle and resource boundaries

Files and cloud drive

Sandbox files versus cloud files

Sites

From preview to a published site

Replay and fork

Which panels still work in a replay