Skip to content
thndrs

Sessions

thndrs writes each run to an append-only JSONL session file in the selected workspace:

.thndrs/sessions/session-YYYYMMDD-HHMMSS.jsonl

Sessions record replayable transcript entries, tool starts and finishes, loaded project-context metadata, token usage, file-write audit metadata, and shell execution metadata.

What Is Stored

Section titled “What Is Stored”
  • User prompts and finalized assistant/reasoning text.
  • Tool names, arguments, statuses, and capped outputs.
  • AGENTS.md paths, scopes, content hashes, byte counts, and truncation state.
  • File write operation, path, before/after hashes, byte counts, and status.
  • Shell command, working directory, exit status, elapsed time, and process kind.

What Is Not Stored

Section titled “What Is Not Stored”

Session metadata does not store full raw provider payloads by default. File-write records do not store full file contents. Shell stdout and stderr are capped and redacted before being recorded through tool output.

Recovery

Section titled “Recovery”

Use normal repository tools such as git diff for file recovery and review. The session file explains what tool ran, what file was targeted, and whether an edit or command succeeded.

Browse and Resume

Section titled “Browse and Resume”

Both session and sessions name the same CLI command group.

Session ids accept an exact id or a unique prefix. An ambiguous prefix is rejected with the matching ids rather than picking one arbitrarily. Lists are newest first.

Terminal window
thndrs sessions list
thndrs sessions show session-20260710-120000
thndrs sessions resume session-20260710

resume acquires an exclusive local writer lock before it can append.

It restores the saved transcript and token totals, but never restores a running tool, pending permission, queued input, or other live process state.

Inside the TUI, use /history, /session <id>, /resume <id>, /context, and /tokens to take a look at your usage.

/context shows item state, policy reason, protection, replacement, and recovery availability.

/tokens distinguishes the local estimate from provider-reported components and normalized input.

Export the current bounded context projection with /context export:

/context export context.json
/context export context.md markdown
/context export context.json --artifacts

Exports are versioned and redact sensitive information.

Artifact bodies are excluded unless --artifacts is explicitly supplied.

Unselected source content and unredacted provider payloads are never exported.

The read-only commands leave the prompt draft intact when lookup or file reading fails.

Inspection and export

Section titled “Inspection and export”

inspect produces a stable, renderer-independent JSON projection. export emits one redacted JSON record per line, in durable sequence order. Neither operation replays a tool, compaction, or any other side effect.

Terminal window
thndrs sessions inspect session-20260710 --format json
thndrs sessions export session-20260710 --format jsonl > session.jsonl

The projection includes transcript, tool audit, usage, context, skill, and configuration evidence already stored in the session.

It omits raw provider payloads, file bodies, and unrecorded live state. Secret values are redacted (best-effort) in inspection and export output.

Debug logs

Section titled “Debug logs”

Diagnostic readers are bounded and redact secret-looking values:

Terminal window
thndrs debug tail --lines 100
thndrs debug session-log session-20260710 --lines 100

/debug log [session-id] reads the corresponding per-session log in the TUI.