RELEASE — VARN V0.3.0 · SEPTEMBER 2026
Varn: Local Filesystem Checkpointing and Safe Rollback for AI Agents and Automated Tools
Capture a known state, see exactly what changed, restore it safely — entirely offline, coexisting with Git, with machine-readable output for agents.
curl -fsSL https://raw.githubusercontent.com/flawme/varn/main/install.sh | shLinux · macOS · Windows — x86_64 and aarch64 · MIT OR Apache-2.0
The install script covers Linux and macOS. On Windows, grab the binary from the releases page or use cargo install.
1Highlights
Safety checkpoint before every restore
Restore captures the current state first, so even a bad restore can be undone with one command.
Conflict detection with explicit confirmation
Files modified or added since the checkpoint are flagged. Varn never silently overwrites or deletes.
Hash-verified, all-or-nothing execution
Every object is re-verified against its SHA-256 before touching the disk; a pre-flight check means a restore can fail, but never halfway.
Built for agents
First-class --json output on every command, idempotent checkpointing, incremental scanning — and zero network calls.
2How a rollback works
1. Plan
Compare the target snapshot with the current filesystem; enumerate every action and conflict.
2. Confirm
Conflicts require explicit confirmation — or the --yes flag.
3. Execute
Capture a safety checkpoint, then restore contents, links, and metadata.
4. Verify
Re-scan and confirm the filesystem matches the snapshot.
varn init
varn checkpoint "before changes"
# ... make changes ...
varn diff <checkpoint-id>
varn restore <checkpoint-id>3Evaluation
| Test suite | 442 tests, all platforms, on every commit |
| Regression tree | 114+ named tests — one per field-reported bug, organized by OS |
| Platforms | Linux, macOS, Windows — x86_64 and aarch64 |
| Network calls | 0 — no telemetry, no accounts, no cloud |
varn.flawme.sbs — full technical overview, CLI reference, and safety model