Tasks & sessions
A session is one delegated task: your prompt, the agent’s work, and everything it produced. Sessions are cloud-side — they continue after you disconnect.
What a session can reach
Section titled “What a session can reach”- The connectors selected at launch (defaults to everything you have). The server intersects your selection with your actual grants — a session can never widen your access.
- Its workspace: a per-person directory shared between your sessions so runs can build on each other’s files. Tick isolated workspace for a clean room.
- The public internet only through the egress proxy — allowlisted hosts, every call logged with byte counts and a decision.
The two views
Section titled “The two views”- Chat — your messages on the right, the agent’s answers as text, activity lines for tool work. Markdown links to workspace HTML files render as inline previews with open ↗ and download.
- tech — the runtime trace: model and runtime metadata, policy checks, every tool call and result, token/cost counters.
Statuses
Section titled “Statuses”queued → working… → done — or failed — reply to retry (a reply relaunches
with your guidance), paused: daily limit (budget caps), stopped.