Docmancer

Your AI coding environment, restored on every machine.

Website  ·  Documentation  ·  Blog  ·  Changelog  ·  Discussions

Your coding agents remember what happened on one machine

Agent backup and restore are development-preview commands. Local encrypted archives are available now. Managed Cloud snapshots remain gated on migration and recovery acceptance.

Docmancer securely restores their sessions, memory, and setup, then makes the useful project context available to every agent you use.

Claude Code and Codex can search the files they already wrote on one machine. A normal dotfile tool can copy directories. Neither gives you an agent-aware, secret-stripped backup with structural verification, project mapping, conflict quarantine, and a reviewed path from raw history to shared project memory.

Start by seeing what Docmancer can protect:

docmancer backup --dry-run

Create a free passphrase-encrypted local archive:

docmancer backup --local --to ~/Backups/agents.dmbak

On a new machine, close Claude Code and Codex and preview the restore:

docmancer restore ~/Backups/agents.dmbak --dry-run
docmancer restore ~/Backups/agents.dmbak

Docmancer restores missing history, skips identical files, merges only safe configuration, and quarantines divergent sessions. It never copies authentication stores, .env files, literal MCP environment values, caches, logs, telemetry, or machine keys.

After backup or restore, local consolidation finds durable decisions and constraints in the protected histories. Every proposal links to exact transcript evidence and waits for review:

docmancer consolidate
docmancer consolidate --review PROPOSAL_ID
docmancer consolidate --approve PROPOSAL_ID

Your agents already learned this. They just cannot tell each other.

Claude Code knows why you moved off Railway. Codex learned your migration convention. Cursor is still following a rule you overruled two months ago. Each agent wrote something down, none of them agree, and none of it is anywhere you can read.

That knowledge is real, and it is already on your disk. It is sitting in CLAUDE.md files, AGENTS.md files, Cursor rules, agent memory directories, and session history, in a different place and a different format for every tool you use.

Docmancer is built around two questions, in this order:

1. I re-explain my project to every coding agent. How do I get them all working from the same context? Docmancer arranges the durable parts as plain local Markdown you can read and edit, then delivers the relevant files to every agent you connect, so a decision you record once reaches all of them.
2. What do my coding agents already know about me and my working style? Docmancer indexes the memory, instructions, and rules they wrote on this machine, and keeps the contributing source attached to every claim, so you can read the answer instead of guessing at it.

Nothing leaves your machine unless you ask it to. There is no telemetry, no account, and no API key needed for the core product.

Install