What it does
Suvadu replaces shell history with a SQLite-backed store that records each command with its exit code, duration, directory, executor and session. It exposes 22 read-only tools, 8 resources and 6 prompts over MCP, and its two write tools stay off until enabled. Session capture covers Claude Code, Codex, OpenCode and Cursor, with commands and prompts recorded for pi.dev, and command tagging only for Windsurf, Aider, Continue and Copilot. A Prompt Explorer traces each recorded command back to the prompt that triggered it.
It suits developers who want AI agents to query earlier shell activity, such as past failures, project context or git changes, or who need to find which prompt produced a given command. Inside a git repository, each command is filed under the branch it started on. In zsh, Up and Down recall previously typed commands, and Alt+A also shows agent commands.
Setup uses an install script that places the suv binary in /usr/local/bin, using sudo only when that directory is not writable, or in a directory chosen with a flag. The installer offers to add a shell hook to the shell rc file after showing the line, and writes nothing unless confirmed. Settings are changed with suv settings, and suv status verifies the install. Data stays on the machine; the only outbound request is an optional daily check for a newer release.
Limitations and requirements
Up and Down arrow recall is available only in zsh; the Bash hook binds Ctrl+R only. The two MCP write tools are off by default and must be enabled as an opt-in. Installation needs a shell hook added to the shell rc file, and sudo may be required for the default install directory. A suv installed through Homebrew or Cargo must be updated with that package manager. Session capture depends on the agent tool; Cursor is recorded without token usage, and Windsurf, Aider, Continue and Copilot receive command tagging only.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
Suvadu
Local shell history and AI agent sessions over MCP: search commands, failures, risk and git changes
v0.5.3As shown on registry.modelcontextprotocol.io when we last read it