What is Consoles?
Consoles is a web workspace where the coding agents you already use run substantial workloads, and where the files, code, and results stay afterwards.
Workbooks and Sessions#
Consoles has two independent objects. A workbook is the durable place where work is saved. A session is captured evidence of how an external agent worked.
| Workbooks | Sessions | |
|---|---|---|
| What it is | An editable space for one body of work | Captured evidence from a supported external agent |
| What it holds | Documents, source files, executable code, execution history, and retained results | Conversation, tool, and lifecycle events the agent emitted, grouped into turns |
| How it starts | You create it explicitly from Workbooks | You set up capture for a project from Sessions |
| Compute | Optional, and only when you start it | None; a session is a record, not a machine |
| Read more | Workbooks | Sessions |
Neither one implies the other. Capturing sessions never creates a workbook, and creating a workbook never starts capture. You can link a session to a workbook when both describe the same work, but the link is only a reference between them.
Choose a path#
The loop is the same whichever way you start: an agent does work, heavy steps run remotely, you inspect and edit the results, then ask the same agent to continue. There is no Consoles chat interface to move into.
- Build in a workbook. Create one, run something, and keep the result: Quickstart.
- Connect an agent. Give an agent scoped MCP access to a workbook: Connect an agent.
- Capture sessions. Keep evidence from Codex or Claude Code as you work locally: Sessions, set up from Connect an agent.
- Start from a recipe. Open a prepared workbook for video, Blender rendering, GPU training, or ComfyUI: Recipes.
What Consoles does not do#
- It does not add another chat interface or agent harness. You keep using Codex, Claude Code, or another MCP client.
- It does not turn a local command, file read, or captured tool call into a workbook execution.
- It does not copy a file because a document or session mentions its path.
- It does not restore a stopped process, its memory, or GPU state. Save the files and setup instructions a later runtime needs.
- A runtime badge such as CPU or Linux is a capability summary. It is not a promise of a particular cloud vendor or Linux distribution.
Some collaboration and API features are not available at launch. Troubleshooting lists them alongside fixes for common setup, compute, and retention problems.