Documentation

Start with one local setup.

Claude Code, Codex, Cursor, and the rest each keep their own memory in their own format, so everything you explained to one of them is invisible to the others. Docmancer reads what they already wrote, keeps the durable parts as readable local Markdown, and delivers the relevant files back to every agent you connect.

$ pipx install docmancerFive-minute setup

Understand the workflow

See how agent delivery, discovery, the Shared Memory scaffold, and grounded Ask fit together.

How Docmancer works

Connect your agents

Install skills, optional recall hooks, separate capture hooks, or the packaged local MCP.

Agent integrations

Use the CLI directly

Find the everyday commands first, then move into memory, docs, agent, and Cloud controls.

CLI reference

Restore your coding environment

Protect Claude Code and Codex history, restore it safely, and review the useful context that should become shared memory.

Backup and restore guide

The core path

  1. 01

    Install and discover

    Run setup to index supported agent memory and connect detected tools.

  2. 02

    Ask with evidence

    Query the full local corpus and inspect the sources behind each answer.

  3. 03

    Browse Shared Memory

    Inspect every canonical file, its arrangement, and the source metadata behind it.

  4. 04

    Deliver it

    Use installed skills, optional hooks, local MCP, or encrypted continuity when needed.