DocmancerHelp
A short guide

Use the web UI. Let agents use the CLI.

Docmancer gives you a human place to understand memory, while coding agents use skills, hooks, CLI, and MCP behind the scenes.

The basic loop

  1. Connect your coding agents.
  2. Index what they already know.
  3. Ask questions or request one memory update.
  4. Review and approve complete-file action cards.
  5. Keep working. Connected agents recall the relevant files automatically.
Start everythingdocmancer setup

Index existing memory and install detected agent integrations.

Open shared memorydocmancer web

Inspect the canonical filesystem and agent delivery from the local workbench.

Write durable memorydocmancer write "# Release\n\nUse the release script." --path decisions/release.md

Save a project decision into the standard scaffold.

Ask from a terminaldocmancer ask "What do my agents know about deployment?"

Use the same memory from the CLI.

Propose a memory updatedocmancer ask "Remember that releases require a smoke test"

Review one complete-file proposal, then approve it explicitly.