Chat
Run agent sessions in the browser. One list across every project, with the runtime and its cost in view the whole time.
Chat is where you talk to an agent without leaving the browser. Open it and you get every session you have run in this workspace, newest first, whichever project it belongs to.
The screen is two panes. On the left, the session list. On the right, whatever you have open: a conversation, or the composer that starts a new one. The header above the thread names the project you are in and the runtime it is running on.
The list is not partitioned by project
Section titled “The list is not partitioned by project”Every session belongs to a project, and the row says which. The list spans the workspace, and the project dropdown above it narrows the view when you want that. Clicking a row from another project takes you there; the URL, the header, and the runtime all follow.
This matters because runtimes are per project. Two rows next to each other can be two different sandboxes, and opening one may cost you a cold start where the other does not. Each row says which, next to the project name:
| Row reads | Opening it |
|---|---|
running | Attaches to a sandbox that is already up |
paused | Resumes a suspended sandbox and restarts the meter |
idle | Starts a sandbox, which takes about 25 seconds and bills |
no runtime | Same, and there is no runtime record in that project yet |
The pages in this section
Section titled “The pages in this section”Chat and the TUI
Section titled “Chat and the TUI”Sessions are platform records, not browser state. A session started from the terminal or the SDK appears in this list too, and opening it here shows its transcript. The surfaces differ in ergonomics: the TUI is keyboard-driven and has screens Chat does not, and Chat spans every project in the workspace rather than the one you are working in. Both show your own sessions; Agents › Sessions is the view that spans owners. See Sessions in the TUI for the terminal side.