AppachiTech/suvadu

Suvadu replaces your shell history with a SQLite-backed store. Every command gets structured context — exit code, duration, directory, executor, session. AI agents can query it via MCP. 100% local.
Measured, not asserted — at 100,000 entries on one M4 Max: 207 µs p95 to record a command, 0.05–15 ms p95 for a judged search over the whole history. One machine, one run — the harness, the corpus and what is still unmeasured are in BENCHMARKS.md
AI agent tracking — full session capture for Claude Code, Codex, OpenCode and Cursor (Cursor without token usage); commands and prompts for pi.dev; commands for Antigravity's agent; command tagging alone for Windsurf, Aider, Continue and Copilot (what each tier means)
Prompt Explorer — trace every recorded command back to the prompt that triggered it
MCP Server — 22 read-only tools, 8 resources and 6 prompts, all read-only by default. The two write tools stay off until you turn their opt-in on. Agent session discovery, project context, failure learning, risk assessment, a shared skills library, your bookmarked command templates. Configurable via suv settings
100% local — no cloud, no telemetry, no account. The only request Suvadu makes on its own is a once-a-day check for a newer release, which you can turn off. MIT licensed.
> Website & Docs: suvadu.sh · CLI Reference: suvadu.sh/cli · Blog: suvadu.sh/blog · What's new: CHANGELOG
## Install
bash
# Homebrew (macOS & Linux)
brew tap AppachiTech/suvadu && brew install suvadu
# Install script (macOS & Linux)
curl -fsSL https://downloads.appachi.tech/suvadu/install.sh | bash
# Install script, into ~/.local/bin without sudo
curl -fsSL https://downloads.appachi.tech/suvadu/install.sh | bash -s -- --user
# Cargo (Rust 1.95 or newer)
cargo install suvadu
The install script puts suv in /usr/local/bin, using sudo only when that
directory is not writable; --user or --dir DIR (or SUVADUINSTALLDIR)
choose another place. Re-running it updates a script-installed suv where it
already is — recognised by the suvadu link the script puts beside it — and
when nothing has changed it downloads nothing but still repairs that link. If
the suv on your PATH came from Homebrew or Cargo, it stops and names that
package manager's update command; any other suv it did not install is left
alone, and --user or --dir installs a separate copy on purpose.
Run at a terminal, it offers to add the shell hook below to ~/.zshrc (or
~/.bashrc on Linux): it shows the line first, writes nothing unless you type
y, keeps a copy of the file as .suvadu-backup, and never adds the hook
twice. --no-modify-rc turns the offer off.
Then add shell hooks:
bash
# Zsh
echo 'eval "$(suv init zsh)"' >> ~/.zshrc && source ~/.zshrc
# Bash
echo 'eval "$(suv init bash)"' >> ~/.bashrc && source ~/.bashrc
Verify: suv status
Each command is recorded with its directory and, inside a git repository, the
branch it started on (the short commit hash for a detached HEAD). The branch
is read from the repository's files — no git runs at your prompt — and shows
in recall's detail pane. A command that changes directory, like cd ../other,
is filed under the branch it was typed on; one that switches branches, under