Skip to content
Atuin

atuin threads

Search, read and resume your coding agents’ captured threads

Terminal window
atuin threads <COMMAND>

List captured threads, newest first

Terminal window
atuin threads list [OPTIONS]
  • --style <STYLE>: How output is rendered. Default: auto.
    • auto: Pretty when writing to a terminal, plain otherwise
    • plain
    • pretty
    • json: A single JSON document
    • ndjson: Newline-delimited JSON: one object per line

Show a thread and its messages. Accepts an id, a harness id or latest

Terminal window
atuin threads show [OPTIONS] <ID|latest>
  • <ID|latest>: Id (its last 8 digits, as list shows them, are enough) or harness id (a unique prefix is enough), or latest for the most recently active thread
  • --style <STYLE>: How output is rendered. Default: auto.
    • auto: Pretty when writing to a terminal, plain otherwise
    • plain
    • pretty
    • json: A single JSON document
    • ndjson: Newline-delimited JSON: one object per line

Full-text search across captured threads, most relevant first.

Terminal window
atuin threads search [OPTIONS] <QUERY>...
  • <QUERY>...: Words to look for in thread titles, message text, reasoning, and tool calls; all must appear. Quote words to find them together, in that order. Use -- before a query that starts with -
  • --harness <HARNESS>: Only search threads from this harness
    • claude-code
    • codex
    • copilot
    • grok
    • hermes
    • kiro
    • opencode
    • pi
    • omp
    • amp
  • --limit <N>: Maximum threads to return; 0 for unbounded. Default: 10.
  • --style <STYLE>: How output is rendered. Default: auto.
    • auto: Pretty when writing to a terminal, plain otherwise
    • plain
    • pretty
    • json: A single JSON document
    • ndjson: Newline-delimited JSON: one object per line

Follow threads and messages as they are recorded (until interrupted)

Terminal window
atuin threads tail [OPTIONS]
  • --style <STYLE>: How output is rendered. Default: auto.
    • auto: Pretty when writing to a terminal, plain otherwise
    • plain
    • pretty
    • json: A single JSON document
    • ndjson: Newline-delimited JSON: one object per line

Import every thread the agents have on this machine, including those capture leaves alone: the ones nobody has gone on with since it was turned on

Terminal window
atuin threads import [OPTIONS]
  • --harness <HARNESS>: Only import threads from this harness
    • claude-code
    • codex
    • copilot
    • grok
    • hermes
    • kiro
    • opencode
    • pi
    • omp
    • amp
  • --style <STYLE>: How output is rendered. Default: auto.
    • auto: Pretty when writing to a terminal, plain otherwise
    • plain
    • pretty
    • json: A single JSON document
    • ndjson: Newline-delimited JSON: one object per line

Capture messages an agent hands over, one JSON object per line on stdin, as capture does its transcript’s. Messages already captured are skipped

Terminal window
atuin threads push --harness <HARNESS> --session <SESSION>
  • --harness <HARNESS>: The harness the thread is from. Required.
    • claude-code
    • codex
    • copilot
    • grok
    • hermes
    • kiro
    • opencode
    • pi
    • omp
    • amp
  • --session <SESSION>: The thread’s id, as its harness names it. Required.

Pick a captured thread and resume it

Terminal window
atuin threads resume [OPTIONS] [QUERY]...
  • <QUERY>...: Search text, or a thread id (or unique id prefix) to resume without the picker
  • --print: Print the resume command instead of running it
  • --in <HARNESS>: Continue the thread QUERY names (by id, or a unique id prefix) in another agent: it is written out as a new session there, tool calls carried over as its own where it has a like tool (notes where they weren’t captured whole), and resumed. One that went on separately on several machines needs --branch
    • claude-code
    • codex
    • copilot
    • grok
    • hermes
    • kiro
    • opencode
    • pi
    • omp
  • --fork: Fork the thread QUERY names (by id, or a unique id prefix): it is written out as a new session of the same agent, with the same history, and resumed. The original is left as it is
  • --as-is: Resume this machine’s copy of the thread QUERY names as it is, without catching it up with sync
  • --switch: Switch this machine’s copy of the thread QUERY names to another branch (the one --branch names, else the only one it can be switched to), in place, and resume it: the history it shares with that branch is kept as it is, and the branch’s messages since are appended from sync. The branch it was on stays in atuin, for --fork to bring back, and the copy as it was is kept as a backup. Only when sync holds all of it and no agent here has it open
  • --branch <BRANCH>: The branch of the thread QUERY names to catch up to, to switch to with --switch, to fork from with --fork, or to continue with --in: this, @<host id>, or the start of its head’s id. The newest by default; --in, and --switch with several branches to switch to, need it named
  • --filter-mode <FILTER_MODE>: The filter the picker opens in (default: global)
    • global: Every thread, from every host
    • host: Threads recorded on this host
    • workspace: Threads whose working directory is inside the current git repository
    • directory: Threads started in the current directory
    • branch: Threads on the current git branch of the current repository
  • --inline-height <INLINE_HEIGHT>: Height of the inline picker; 0 for fullscreen