Session Workspace
The session workspace — toolbar actions, session details, the live preview, and how the controls change with session state.
The session workspace is where you watch an agent work and drive its sandbox. It has three regions: a slim toolbar across the top, the agent pane on the left (chat or terminal), and the preview on the right.
Toolbar
The toolbar keeps only the controls you reach for most. Everything else lives one click away.
Identity & session details
The left of the toolbar shows the session id, the agent badge (e.g. Claude Code, Codex), and a status dot. Click this cluster to open the session details popover, which holds the ambient context that doesn't need to be on-screen all the time:
- Usage — total tokens and estimated cost
- Sandbox — the sandbox id
- Forked from — a link to the parent session, if this one was forked
- Branch — the working branch
- Pull request — a link to the PR, once one exists
- Tags — add or remove tags inline
Primary actions
These stay visible because they're the controls you use during a session:
| Control | When it appears | What it does |
|---|---|---|
| Chat / Terminal | Running, Claude Code | Switch the left pane between the agent chat and a raw terminal |
| Files | Running | Toggle the file browser |
| Pause | Running | Freeze the sandbox so you can resume later |
| Resume | Paused / auto-paused | Wake a frozen sandbox |
| Deploy | Stopped, with a deploy target | Deploy the project to its configured target (Vercel / Fly.io) |
More actions (the ⋯ menu)
Secondary actions collapse into the overflow menu, grouped so related actions sit together:
- Git — Pull (
git pull --ff-onlyin the sandbox) · Push (commit changes and open a branch/PR) - Session — Bookmark · Share (generate a public read-only link) · Export (download a completed session)
- Snapshot / Fork — Snapshot or Save env (persist the sandbox state back to its template/project, or as a new environment) · Fork (snapshot the current state and boot a new session from it)
- Destroy — isolated at the bottom in red. Permanently deletes the sandbox and its working tree. Asks for confirmation first; this cannot be undone.
Which actions appear depends on the session's state — for example, Pull/Snapshot/Fork are only available while a session is running, Resume only while paused, and Deploy only on a stopped session whose project has a deploy target.
Preview
The right pane previews your running app. When a port starts listening inside the sandbox, the preview opens automatically — bind your dev server to 0.0.0.0 so it's reachable.
Before a port is detected, the pane shows a quiet Waiting for your app… state. You can also:
- Detect — scan for a listening port on demand
- Enter a port manually — use the + control next to Detect if you want to point the preview at a specific port
Below the preview is a console with persisted shell tabs. If Raziel detects a dev command (e.g. npm run dev), it offers a one-click ▸ run button to start it in the active shell.