nodrift

Flight recorder + bisect for AI agent behavior. Your agent got worse overnight — find out why in 10 seconds.

Agent behavior is determined by a composite nobody version-controls as a system: CLAUDE.md, skills, .cursor/rules, MCP server versions, harness/CLI version, model. Any of these can change without you — marketplace skills auto-update, harnesses ship silent changes, providers update models. nodrift snapshots the full composite, shows you exactly what changed, ranks the suspects, and rolls back the culprit.

Status: pre-release. First public release targeted before 2026-07-28 (the MCP spec RC ships six breaking changes that day — nodrift scan mcp will tell you what breaks for you).

Quick start (once released)

npx @nodrift/cli init      # snapshot your full agent-config composite, <60s, no login
nodrift diff          # git status for your agent config — incl. global files
nodrift blame --since "last friday"   # ranked candidate causes for "it got worse"
nodrift rollback skill:<name> --to <version>
nodrift scan mcp      # what the 2026-07-28 MCP RC breaks in your config

What it does — and what it honestly can't

• blame produces candidate causes, not verdicts — correlation from timing, change magnitude, and source. Verdicts require running your eval suite across states (bisect, coming in v1.1).
• Harness internals are unobservable: we can detect that behavior-determining state changed, not always what a vendor changed inside a release.
• Canary evals (v1.1) are smoke detectors, not MRIs: they catch gross regressions (ignored instructions, skills not firing), not every subtle shift.

Supported harnesses

Claude Code and Cursor at launch; Codex CLI and Copilot next. Adapters are read-only — nodrift never wraps, hooks, or instruments your agent at runtime.

Telemetry

Opt-in only, and inspectable: nodrift telemetry --show-payload prints exactly what would be sent (event names, config hashes, version strings — never file contents, paths, or prompts). --no-telemetry, config, and NODRIFT_TELEMETRY=0 are all honored, forever.

Docs

• Roadmap — what's coming, in order
• Decisions — public architecture decision records
• Contributing · Security

License

MIT. Contributions accepted under the Developer Certificate of Origin.