archgate session-context
Read AI editor session transcripts for the project. Useful for auditing what an AI agent did during a coding session.
archgate session-context <subcommand> [options]Subcommands
Section titled “Subcommands”archgate session-context claude-code
Section titled “archgate session-context claude-code”Read the Claude Code session transcript for the project.
archgate session-context claude-code [options]| Option | Description |
|---|---|
--max-entries <n> | Maximum entries to return (default: 200) |
--skip <n> | Skip the N most recent sessions (useful when running as sub-agent) |
archgate session-context copilot
Section titled “archgate session-context copilot”Read the Copilot CLI session transcript for the project. Sessions are matched by their workspace cwd field.
archgate session-context copilot [options]| Option | Description |
|---|---|
--max-entries <n> | Maximum entries to return (default: 200) |
--skip <n> | Skip the N most recent sessions (useful when running as sub-agent) |
--session-id <id> | Specific session UUID to read |
archgate session-context cursor
Section titled “archgate session-context cursor”Read the Cursor agent session transcript for the project.
archgate session-context cursor [options]| Option | Description |
|---|---|
--max-entries <n> | Maximum entries to return (default: 200) |
--skip <n> | Skip the N most recent sessions (useful when running as sub-agent) |
--session-id <id> | Specific session UUID to read |
archgate session-context opencode
Section titled “archgate session-context opencode”Read the opencode session transcript for the project. Sessions are matched by comparing the session directory field to the project root. opencode records sub-agent runs as child sessions that share the parent’s directory — these are excluded from recency selection, so the most recent top-level session is always the main development session. Use --session-id to read a specific session, including a sub-agent child session.
When several top-level sessions exist for the same directory, recency selection picks the most recently updated one — which may not be the conversation you are part of. If you know a session ID inside the right conversation tree (for example, a sub-agent knows its own child session ID), pass --session-id <id> --root to resolve its top-level ancestor deterministically instead of relying on recency.
archgate session-context opencode [options]| Option | Description |
|---|---|
--max-entries <n> | Maximum entries to return (default: 200) |
--skip <n> | Skip the N most recent top-level sessions (sub-agent sessions always excluded) |
--session-id <id> | Specific session ID to read |
--root | Resolve to the top-level (root) session — with --session-id, walks up from a sub-agent child session |
Examples
Section titled “Examples”Read the latest Claude Code session:
archgate session-context claude-codeRead a specific Cursor session:
archgate session-context cursor --session-id abc123Read the latest Copilot CLI session:
archgate session-context copilotRead the latest opencode session:
archgate session-context opencodeRead the parent session (skip the sub-agent’s own session):
archgate session-context claude-code --skip 1Resolve an opencode sub-agent child session to its top-level ancestor:
archgate session-context opencode --session-id ses_child123 --root