atuin: Atuin gives you, and your agents, a history of everything that happened in your terminal.
What problem it solves
Shell users need a searchable, durable record of commands and terminal activity across machines, while AI agent users need continuity between sessions and harnesses. Atuin addresses both needs by recording terminal and agent activity and making it available for search, resumption, and optional synchronization.
Key features
Searchable shell history — Atuin records terminal activity in a SQLite database and provides both an interactive Ctrl+r search pane and a command-line search interface. It captures exit codes, working directories, hostnames, and command duration.
Source: README
Agent thread capture and resumption — Atuin captures Claude Code, Codex, OpenCode, and other agent sessions so their context can move between machines and harnesses. Threads can be resumed with `atuin resume` and searched from the command line.
Source: README
Agent access through MCP — The built-in MCP server gives agents an optional way to search the full history and retrieve context from previous work.
Source: README
Encrypted cross-machine sync — Atuin can synchronize shell sessions and AI threads across computers, including ephemeral VMs. Users can choose the official Atuin Service or self-host the sync server, and synchronized data is end-to-end encrypted.
Source: README
Quick start
Copied verbatim from the project's README.
curl --proto '=https' --tlsv1.2 -LsSf https://setup.atuin.sh | sh# search for all successful `make` commands, recorded after 3pm yesterday
atuin search --exit 0 --after "yesterday 3pm" makeWho it may suit
Inference: this may suit terminal users who want searchable command history across machines. It may also suit developers using AI coding agents who need session continuity and agent-accessible context.
Topics to discuss
Which shell history details would be most useful to search and filter?
How should agent thread context move safely between different harnesses?
What should the default experience be for offline use versus encrypted synchronization?
Written by ReadmeX AI from the project's README, source and public GitHub data; it may contain mistakes.
Read the original README https://github.com/atuinsh/atuin#readme
ReadmeX opened this community for a trending project; it is not run by the project. Maintainers can claim it from the community page.
Comments
…