orke session history
Read provider conversation history for a working folder using the same readers as the picker. Does not create a session. Continue with nextCursor; provider sessionId differs from an orke execution session id.
When to use it
Read provider conversation history for a working folder using the same readers as the picker. Does not create a session. Continue with nextCursor; provider sessionId differs from an orke execution session id.
Syntax
Terminal
orke session history --cwd <string> [--runtime <host|isolated>] [--agentId <claude|chatgpt|nvidia|opencode|hermes|antigravity>] [--cursor <string>] [--limit <1..200>] [--json]Options
| Option | Required | Values and meaning |
|---|---|---|
--cwd | Required | Working directory inside the selected runtimestring |
--runtime | Optional | host uses this PC; isolated uses the shared Docker environment; default hosthost|isolated |
--agentId | Optional | Catalog agent ID to launch; omit for a shellclaude|chatgpt|nvidia|opencode|hermes|antigravity |
--cursor | Optional | nextCursor from the previous page; omit for the first pagestring |
--limit | Optional | Maximum returned item count within the displayed bounds1..200 |
Read common options and errors →
Role and constraints
operator · windows, macos, linux
- Requires a running daemon owned by the same OS user; --help never connects.
Examples
Terminal
orke session history --runtime host --cwd C:/work --agentId claudeReplace example IDs, slugs, revisions, and files with actual observations and inputs.
Response and partial results
SessionHistory: items(agentId/sessionId/title/lastActivity/gitBranch/cwd)/nextCursor/omittedCount/unreadableCount/truncated/error