terma session subcommands give you full access to individual sessions from the terminal. You can list sessions by person or time window, pull a cost and token roll-up for a single session, replay every tool call in order, and see exactly which commits and pull requests a session produced.
terma session list
List sessions for your project, most recently active first. Filter by user, time window, agent source, or model to narrow the results. Usagestring
Filter to sessions owned by a specific person. Matches name, email, alias, or user ID.
string
Show sessions active after this time. Accepts RFC 3339, a date, a relative age (
24h, 7d), or today / yesterday.string
Filter by agent source — for example
claude-code, codex, or opencode.string
Filter by model name.
string
Output format:
table (default), json, yaml, csv.terma session get
Show the roll-up for a single session: cost, token counts, model used, number of files touched, and high-level stats. Usageterma session events
Replay a session’s events in the order they occurred — prompts, tool calls, responses, and errors. Use--tools-only to focus on tool calls without the surrounding conversation, or --errors-only to surface failures quickly.
Usage
string
Specify the agent source to disambiguate when a routing key appears in more than one harness.
flag
Show only tool-call events, hiding prompts and plain responses.
flag
Show only events that resulted in an error or non-success status.
terma session git
Show the git and GitHub actions a session performed: commits created, pull requests opened or commented on, and files staged during the session. Usagestring
Specify the agent source.
The
<routing-key> is the session identifier shown in the ID column of terma session list output. You can also copy it from the session URL in the Terma dashboard.