Docmancer Cloud is optional. Local recall, capture, MCP, the TUI, Git team memory, audit, and export work without an account.
Connect an account
docmancer cloud connect --base-url https://api.docmancer.dev --create-recovery
docmancer cloud sync
docmancer cloud devices
The CLI shows a verification code and opens the account approval page. Store the recovery key offline. A connected device can sync encrypted revisions, inspect its device registration, and approve a new device after checking the displayed fingerprint. These responses do not contain memory text or local paths.
Use the browser workbench
After the browser is approved, it unwraps the workspace key and decrypts synced atoms, relations, overrides, history, context packs, and proposals locally. Browser-native changes are encrypted and signed before upload. The API stores and relays ciphertext, not decrypted memory.
Some TUI actions need files, indexes, hooks, documentation, or credentials that exist only on a machine. Start the local relay on the device that owns that state:
docmancer cloud relay --project "$PWD"
The relay polls outbound over HTTPS and does not open a local port. It accepts a fixed Docmancer action allowlist, not arbitrary Python methods or shell commands. Requests and results are encrypted with the workspace key and signed by the sending device, so the service sees delivery metadata and ciphertext.
Read actions are enabled by default. To let confirmed browser actions change local files, records, settings, or indexes, restart it with a second local opt-in:
docmancer cloud relay --project "$PWD" --allow-writes
A write still requires confirmation in the browser. Closing the command stops new local work. Browser requests expire after two minutes, the server accepts no expiry beyond five minutes, and expired relay ciphertext is pruned after 24 hours.
Work offline
Local writes create immutable revisions and queue encrypted envelopes. When connectivity returns, the client retries idempotently, verifies device signatures and ciphertext, writes decrypted records durably, and only then advances the transport cursor. Local recall, capture, the TUI, MCP, docs, audit, and Git memory continue without Cloud.
Disconnect
docmancer cloud disconnect
Disconnecting does not delete local records. Remote export and deletion are separate explicit account operations.