atuin threads
Search, read and resume your coding agents’ captured threads
atuin threads <COMMAND>atuin threads list
Section titled “atuin threads list”List captured threads, newest first
atuin threads list [OPTIONS]Options
Section titled “Options”--style <STYLE>: How output is rendered. Default:auto.auto: Pretty when writing to a terminal, plain otherwiseplainprettyjson: A single JSON documentndjson: Newline-delimited JSON: one object per line
atuin threads show
Section titled “atuin threads show”Show a thread and its messages. Accepts an id, a harness id or latest
atuin threads show [OPTIONS] <ID|latest>Arguments
Section titled “Arguments”<ID|latest>: Id (its last 8 digits, aslistshows them, are enough) or harness id (a unique prefix is enough), orlatestfor the most recently active thread
Options
Section titled “Options”--style <STYLE>: How output is rendered. Default:auto.auto: Pretty when writing to a terminal, plain otherwiseplainprettyjson: A single JSON documentndjson: Newline-delimited JSON: one object per line
atuin threads search
Section titled “atuin threads search”Full-text search across captured threads, most relevant first.
atuin threads search [OPTIONS] <QUERY>...Arguments
Section titled “Arguments”<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-
Options
Section titled “Options”--harness <HARNESS>: Only search threads from this harnessclaude-codecodexcopilotgrokhermeskiroopencodepiompamp
--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 otherwiseplainprettyjson: A single JSON documentndjson: Newline-delimited JSON: one object per line
atuin threads tail
Section titled “atuin threads tail”Follow threads and messages as they are recorded (until interrupted)
atuin threads tail [OPTIONS]Options
Section titled “Options”--style <STYLE>: How output is rendered. Default:auto.auto: Pretty when writing to a terminal, plain otherwiseplainprettyjson: A single JSON documentndjson: Newline-delimited JSON: one object per line
atuin threads import
Section titled “atuin threads import”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
atuin threads import [OPTIONS]Options
Section titled “Options”--harness <HARNESS>: Only import threads from this harnessclaude-codecodexcopilotgrokhermeskiroopencodepiompamp
--style <STYLE>: How output is rendered. Default:auto.auto: Pretty when writing to a terminal, plain otherwiseplainprettyjson: A single JSON documentndjson: Newline-delimited JSON: one object per line
atuin threads push
Section titled “atuin threads push”Capture messages an agent hands over, one JSON object per line on stdin, as capture does its transcript’s. Messages already captured are skipped
atuin threads push --harness <HARNESS> --session <SESSION>Options
Section titled “Options”--harness <HARNESS>: The harness the thread is from. Required.claude-codecodexcopilotgrokhermeskiroopencodepiompamp
--session <SESSION>: The thread’s id, as its harness names it. Required.
atuin threads resume
Section titled “atuin threads resume”Pick a captured thread and resume it
atuin threads resume [OPTIONS] [QUERY]...Arguments
Section titled “Arguments”<QUERY>...: Search text, or a thread id (or unique id prefix) to resume without the picker
Options
Section titled “Options”--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--branchclaude-codecodexcopilotgrokhermeskiroopencodepiomp
--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--branchnames, 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--forkto 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--switchwith 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 hosthost: Threads recorded on this hostworkspace: Threads whose working directory is inside the current git repositorydirectory: Threads started in the current directorybranch: Threads on the current git branch of the current repository
--inline-height <INLINE_HEIGHT>: Height of the inline picker; 0 for fullscreen