Agents drift. Someone should be able to prove why.
Teams running LLM agents in production can't see when behavior drifts, can't reproduce the exact state the agent was in last week, and can't prove what it was allowed to do. agentsnap exists to close that gap — starting with the sharpest piece: which change caused this?
Why this, why now
Every serious engineering discipline eventually got version control for the thing that actually controls behavior. Code got git. Infrastructure got Terraform state. ML models got registries. AI agents got — a prompt in one repo, tool schemas in another, retrieval settings in a config service, a knowledge base that someone refreshed on Thursday, and a model version that quietly bumped underneath all of it.
A 2025 survey of production LLM systems found some 77% of teams running with no monitoring or homegrown scripts. The practitioners I talk to don't dispute it — they tell me about the spreadsheet, the cron job, and the incident where the agent "just started acting different" and the postmortem died in a shrug.
agentsnap is the smallest honest tool that fixes the shrug: version the whole config graph as one artifact, diff any two points in time, and measure — against a real noise floor — which change moved which behavior.
Where we are, honestly
Early. The snapshot, diff, and drift core is built and demoed; secrets redaction shipped; the CLI layer goes open-core on GitHub in July 2026. There are no customer logos on this site because there are no customers yet — there are three design-partner slots instead, and the partners who take them will shape what this becomes. If a site full of borrowed credibility would have worked on you, this tool probably isn't for you anyway.
Aarin Sheth
Solo founder. Final-year student at IIT Kanpur ('27); currently also building digital twins for Jaguar Land Rover as an intern in Bengaluru. Writes every line of agentsnap, runs every discovery call, and answers the email on this site personally.
- Local-first, always. The config never leaves the machine it lives on. This is architecture, not policy.
- Measure our own noise before accusing your config. An alarm without a calibrated baseline is spam.
- Unmeasured is not unchanged. Every report states its coverage. No silent green checkmarks.
- No LLM judges we can't calibrate. Deterministic scoring or nothing.
- Build on demand. Nothing ships until a named team asks for it in a call. The roadmap is a queue of requests, not a vision deck.
Talk to the founder. There's no one else here.
Question, objection, war story about an agent that drifted — all welcome. Replies come from a person, usually within a day.