v0.4.1 · MIT · macOS & Linux

Total recall for
your terminal.

Search your shell history. Track AI agent commands.

Keep command context in a local SQLite database. Connect supported AI agents through MCP to query past work.

[su-va-du] Noun · Trace / Footprint

Already use Homebrew?

brew tap AppachiTech/suvadu && brew install suvadu

Then enable shell integration below. Install script and Cargo options are there too.

Using AI coding agents? See a session handoff or inspect captured sessions.

zsh — suv search

Earlier interface shown · Current search guide

Not just history. Memory.

Three layers that turn your terminal history into a structured, queryable, agent-accessible knowledge base.

Structured History

Recorded commands include exit code, duration, directory, session, and executor. Search and filter your history in a terminal UI.

AI Agent Tracking

Identify supported agents in recorded commands. Configure an agent integration to capture prompts and link them to commands where supported.

MCP Agent Memory

Query history and past sessions through MCP, and share reusable instructions with the new skills library. Sync skills into Claude Code, Cursor, and Codex.

Suvadu stores history locally. When you connect an AI client, that client controls how retrieved history is used.

See it in action

Hand off an agent session, then explore search, agent activity, and prompt history.

Hand off an agent session

A Claude Code session stops partway through a task. Suvadu has already imported its prompts, responses, and commands. Open Codex in the same repo and ask it to continue; Codex reads the session over MCP.

1 · zsh — captured sessions
$ suv sessions --list -n 2

  Last active        ID         Type   Tag          Agent / Host     Model                 Tokens   Cmds Duration
  ────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
  2026-09-19 09:14   claude-8   AI     —            claude-code      claude-sonnet-4-5      47330      9    42.0m
  2026-09-19 08:55   4f2a9c1e   Human  api          laptop           —                          —     31    72.0m
2 · Codex — Suvadu MCP

you › Pick up where my Claude Code session left off in this repo.

called list_agent_sessions
called get_agent_session claude-8f3c2a71-…

codex › The last Claude Code session added rate limiting to the login route. Its final npm test run (command-5512) exited 1: two tests in tests/auth.test.ts still expect 200 instead of 429. I'll update those tests first.

Synthetic example. Claude Code, Codex, and OpenCode sessions are imported natively. Other integrations record commands and prompts. A turn still in progress is available after it ends.

Search, agent activity, and prompts

These recordings show an earlier interface and do not include agent sessions. See the CLI docs for current screens and shortcuts.

zsh — suv

Interactive Search

Search recorded commands with substring matching, filters, and an optional context-aware Smart mode.

  • Every word you type must appear in the match
  • Filter by date, exit code, directory, executor
  • Optional Smart mode ranks same-directory matches higher
  • Detail pane with full metadata (Tab)

Why switch?

Add structured context and filtering to your shell history.

Feature Standard History Suvadu
Search
Built-in history search
Substring search with interactive filters
Command context
Commands; timestamps depend on configuration
Exit code, duration, directory, session and executor
Arrow recall
Usually recent commands first
Zsh: recent commands first, directory as a tiebreaker
Filtering
Shell commands and external tools
Date, exit code, directory and executor filters
Storage
A shell history file
A local SQLite database
Analytics
External tools or scripts
Built-in stats and agent dashboards
Recording controls
Shell-specific ignore settings
Ignore patterns, pause and disable controls
Secret redaction
Depends on shell and tooling
Pattern-based redaction for recognized secrets

Shell behavior varies by configuration. Suvadu records commands after integration is enabled; ignore settings apply. Redaction matches known patterns and cannot identify every secret.

Works with your tools

Dedicated integrations and executor detection for supported tools.

Claude Code logo
Claude Code
hooks + MCP ✓
Cursor logo
Cursor
hooks + MCP ✓
Codex logo
Codex
hooks + MCP ✓
OpenCode logo
OpenCode
plugin + MCP ✓
Terminal logo
Terminal
shell hooks ✓
VS Code logo
VS Code
auto-detect ✓
Windsurf logo
Windsurf
auto-detect ✓
Antigravity logo
Antigravity
shell detection ✓

Shell recording, prompt capture and MCP access have different setup requirements. Detection alone does not capture prompts. Choose your agent setup or see the compatibility matrix.

All trademarks belong to their respective owners.

Install Suvadu

macOS & Linux · Zsh 5.1+ or Bash 4+

Install the CLI, enable recording in your shell, then try a search.

  1. Install the CLI

    Choose one method. Each installs the suv command.

    Homebrew

    Recommended if you already use Homebrew on macOS or Linux. Update later with brew upgrade suvadu.

    brew tap AppachiTech/suvadu && brew install suvadu

    Install script

    Linux only for now: the 0.4.1 script requests a macOS file that is not published, so on a Mac use Homebrew or Cargo. Downloads a binary for your architecture, verifies its checksum, and installs to /usr/local/bin using sudo.

    curl -fsSL https://downloads.appachi.tech/suvadu/install.sh | bash
    Read the installer source

    Cargo

    Requires a Rust toolchain. Compiles from source, which can take a few minutes. Make sure ~/.cargo/bin is on your PATH.

    cargo install suvadu
    Requirements and manual installation
  2. Enable shell integration

    Installing the CLI alone does not record commands. Choose the shell you use to enable recording and Ctrl+R search.

    Zsh setup

    Add this line once to ~/.zshrc. If it is already there, keep the existing line.

    eval "$(suv init zsh)"

    Save the file, then run this in your Zsh terminal to activate it:

    source ~/.zshrc

    Bash setup

    Add this line once to ~/.bashrc. If it is already there, keep the existing line.

    eval "$(suv init bash)"

    Save the file, then run this in your Bash terminal to activate it:

    source ~/.bashrc

    Bash 4+ is required. For a login shell, make sure ~/.bash_profile sources ~/.bashrc, or add the hook to the startup file your shell reads. Shell setup details

  3. Check your setup and try a search

    Check your shell, recording state and database. Agent and MCP setup are optional; follow the diagnostic guidance for any issues.

    suv doctor

    Run echo hello, then press Ctrl + R and search for it. Select a result to place it in your prompt; press Enter to run it.

    Need help? Read the diagnostic guide or check shell integration.

What's New

v0.4.1
Full changelog →
v0.4.1 Native session capture for Codex, Claude Code, and OpenCode — prompts, responses, models, and reported token usage; cross-agent MCP session summaries (saving is opt-in); unified `suv sessions` browser with AI timelines and a scrollable summary panel
v0.4.0 Shared skills with native sync; 18 MCP tools, 8 resources, and 3 prompts; `suv guard`; project config; faster indexed search; live filters and interactive bookmark/alias managers