Agent backup preview · Conflict-safe restore · Shared memory
Docmancer already gives your agents shared, source-attributed memory. The development preview adds encrypted session and setup backup with conflict-safe restoration across machines.
AI agents it plugs into, plus any MCP client
Claude Code
Cursor
Codex
Cline
OpenCode
GeminiClaude DesktopHow it works
Backup keeps the original agent-owned history recoverable. Consolidation finds the useful decisions inside it, preserves their sources, and lets you choose what reaches the agents you use through local files, the CLI, MCP, and installed agent plugins. Read how it works.
01 · Preview
Docmancer inventories Claude Code and Codex sessions, memory, instructions, skills, and safe setup. It shows project filters, size, transformations, and exclusions before it reads portable content or writes a backup.
$ docmancer backup --dry-run02 · Protect
Free local archives use a passphrase. Personal Sync stores client-encrypted snapshots for each approved source device. Secrets, authentication stores, caches, logs, and machine keys are excluded.
$ docmancer backup03 · Restore
Restore verifies every encrypted chunk, maps projects explicitly, refuses live agent homes, merges only safe configuration, and quarantines divergent sessions instead of choosing a winner.
$ docmancer restore backup.dmbak04 · Carry forward
Local consolidation finds durable decisions and constraints, links each proposal to exact transcript evidence, and waits for your approval before anything becomes Shared Memory for your other agents.
$ docmancer consolidateDevelopment preview
The working tree can create and restore passphrase-encrypted .dmbak archives and consolidate useful decisions locally. Release acceptance is still pending.
Read the backup guidePersonal Sync
Managed source-device snapshots are in preview. The release gate includes historical-key migration, large-corpus testing, and real-account recovery acceptance.
See managed restoreTeam Sync, not available yet
Team Sync is being designed around complete-file review before approved context reaches the coding agents used by colleagues.
See the planned modelThe local app
Run docmancer web to ask what your agents know, browse every canonical file in its actual arrangement, and inspect what each connected agent receives. That last pane is how you check that the same context really did reach all of them. The app stays on 127.0.0.1 and uses the same local Markdown memory as your connected agents.
Start with docmancer web
Ask a question, get a grounded answer with sources attached.
Browse the canonical files and see exactly how they are arranged.
Write durable memory and see it land in the Library instantly.
The server binds to 127.0.0.1 and authenticates your browser once with a single-use token, so the interface is never exposed to the network.
Home, Shared Memory, and Library each answer one clear question. Technical diagnostics stay available without taking over the reading surface.
The CLI, installed skills, optional hooks, and local MCP let coding agents use the same files you can inspect in the app.
FAQ
You can copy directories with rsync, chezmoi, or a backup tool. Docmancer adds agent-specific inventory, secret stripping, encrypted portable snapshots, project mapping, conflict-safe restore, and source-attributed consolidation. It protects the useful environment without treating credentials, caches, and every machine-specific file as portable.
The first backup adapters protect supported Claude Code and Codex sessions, prompt history, memory, instructions, skills, hooks, safe settings, MCP definitions, and project identity. Authentication stores, literal environment values, machine keys, caches, logs, and telemetry are excluded.
No. Agent-owned memory is attributable evidence. Recurrence can show that several agents recorded the same idea, but it is not labelled consensus or truth. Curated Markdown and discovered evidence remain separate, inspectable layers.
docmancer setup installs skills and plugins for supported AI agents, and docmancer mcp serve exposes the same memory as MCP tools for any MCP client. Optional recall hooks can provide a bounded, task-relevant file selection automatically. Shared Memory shows the canonical tree and the exact projection prepared for each agent.
Yes. Shared Memory is ordinary source-attributed Markdown on your machine. Docmancer provides a predictable scaffold and stable addresses, while you retain direct access to every file.
No. Discovery, the file scaffold, local retrieval, and deterministic combination work with zero model calls. A configured provider is optional for generated answers and selected maintenance tasks.
In the development preview, free backups are passphrase-encrypted local .dmbak files. Managed snapshots are not production-ready yet. Their design uploads client-encrypted manifests and chunks, so the hosted service receives opaque references and encrypted sizes rather than plaintext sessions, local paths, credentials, or recovery keys.
In the development preview, run docmancer restore backup.dmbak and confirm the project mappings and preview. Managed second-machine restore remains gated on historical-key migration and real-account acceptance. Divergent histories are quarantined instead of overwritten.
No. Capture is a separate opt-in for supported agents. It redacts a bounded lifecycle payload, writes eligible checkpoints only to the inbox, deduplicates retries, and never calls a provider on the capture path.
No. Documentation is a separate searchable Library corpus available through the local app, docmancer docs query, and connected agents using the skill. It is not automatically injected into personal memory.
One install finds the memory scattered across your AI agents and serves it back through the CLI, the MCP server, or a plugin.