Skip to main content
Last updated: 2026-09-06
orca sessions inspects sessions, the persisted state an agent keeps across runs. Sessions are created by orca run; pass --session <id> to orca run to continue one. Every subcommand accepts the global flags. orca sessions get takes a required <id>; there is no interactive picker.

​
orca sessions list

Lists sessions. --agent is an exact profile-name match, sent to the server as a filter so the paging total reflects the filtered set; the CLI also filters client-side for servers that predate the filter.
Plain (piped) output is one tab-separated row per session: id, profile, runtime, status, lastUsedAt (as YYYY-MM-DD HH:MM), runCount. --json prints an array of session objects with id, profile, runtime, status (idle, running, errored, or shutdown), createdAt, lastUsedAt, runCount, and, when the server has them, lastPrompt, lastRunStartedAt, lastRunFinishedAt, and lastRunStatus. The terminal view adds a last used and runs column and a status glyph. When there are no sessions, stdout stays empty and a hint goes to stderr.

​
orca sessions get

Shows one session with its run history. The history comes from a second request; if that request fails the session still prints, with an empty runs array in JSON and no recent-runs table in the terminal.
--json prints the session object plus a runs array of run summaries (id, subTask, status, startedAt, finishedAt). The plain view prints tab-separated key and value rows for id, profile, runtime, status, created, lastUsed, runCount, and lastRunStatus (- when absent); the run list is not part of plain output. The terminal view shows the same fields as a panel, plus the last prompt and up to 5 recent runs (id, status, started, duration).
Verified against orca-cli cli-v0.5.0.