Session Panels
The right-rail panels available while a session is open, Task, Agent Todos, Session & usage, Repo files, and Source Control.
While a session is open, CDE's right rail switches between several panels. This page documents the ones specific to agent sessions and tasks, for background bash and tool-call orchestration inside the chat itself, see Origin Agent.
Task and Agent Todos
When a session is linked to a Studio task, the right rail shows a Task / Agent Todos tab pair.
Task shows the linked task's detail:
| Field | What it shows |
|---|---|
| Status, Priority, Assignee, Labels, Created | The task's current metadata, mirrored from Studio |
| Description | The task description the session was started from |
| Activity | A log of changes, assignment, status changes, priority changes, and label edits, each attributed to the person who made it |
| Comments | Task-level comments |
This is a read view into Studio's task board, edits made here (or in Studio) sync both ways since it's the same underlying task.
Session & usage
The Session & usage panel gives you a live readout of the current session's cost and consumption:
| Section | What it shows |
|---|---|
| Session | Session name, message count |
| Model | Provider, model, and context limit for the session |
| Tokens | Usage as a percentage of context limit, plus total, input, output, reasoning, and cache (read/write) token counts |
| Messages | User message count, assistant message count, and total cost for the session |
| Timeline | When the session was created and its last activity timestamp |
Use this panel to catch a session drifting toward its context limit, or to see what a session actually cost before deciding whether to keep going in it or start fresh.
Provider and model here reflect what the session is currently set to, if you switch models mid-session (see Shortcuts: choose model), this panel updates to match.
Repo files and Source Control
Two more right-rail panels round out the session view:
- Repo files: a searchable file tree for the current workspace, modified files are marked
- Source Control: staged and unstaged changes with a commit message box, the same Git integration available from the command palette
Both operate against whichever workspace is active, the local folder in Open Project mode, or the remote sandbox filesystem on a cloud worktree.
Next steps
- Agents: where tasks, subagents, and sessions fit together
- Origin Agent: tool use and background bash inside the chat panel
- Cloud worktrees: the sandbox a cloud session's Repo files and Source Control operate against