Suvadu runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 20 Oct 2026.
Local shell history and AI agent sessions over MCP: search commands, failures, risk and git changes
What the code does
We read the source, 1 d ago · rules 995398eba69f
Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.
"rm -rf ./target",
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found things in this code
Code changes quietly between releases, and nobody reads the diff of a dependency. We do, on every release — watch Suvadu and you get told the day something new turns up.
Alternatives to Suvadu
same job, measured the same wayDesktop MCP workspace for AI agents: file edits, commands, Git status, resumable history sessions.
Local Git-history memory for coding agents: reverts, suppressions, hotspots, and annotations.
GEDCOM CLI and MCP server for AI-assisted family-history research with reviewable changesets.
Record debug sessions, commands, failed attempts, and successful fixes in local SQLite storage.
Record debug sessions, commands, failed attempts, and successful fixes in local SQLite storage.
Local-first memory for AI coding agents: shell history with exit codes, git diffs, docs, MCP.
Stateful, structured, safe shell sessions for AI agents over local, SSH, and Docker.
Lossless archive and search for AI agent sessions across clients, exposed to agents over MCP.
Suvadu — questions
Answers built from our own checks of this server.