Personal Sync carries the same canonical Shared Memory tree to every machine you use. Encryption, signing, and decryption happen on your devices. Docmancer Cloud stores encrypted revisions and cannot read your memory.
Agent backup is a separate snapshot path for restoring Claude Code and Codex sessions, memory, and safe setup. See Agent backup and restore when you want the complete coding environment rather than only the Shared Memory tree.
The complete single-machine product stays free. Personal Sync is for continuity between machines, managed history, and recovery.
Connect the machine that has your memory
Install Docmancer, combine your local agent memory, and connect:
pipx install docmancer
docmancer setup
docmancer cloud connect
uv tool install docmancer works instead of pipx. You can also choose Connect this device under Cloud and billing in docmancer web.
The browser asks you to sign in and authorize the device. Back on your machine, Docmancer then:
- Creates the encrypted workspace and approves the first device.
- Creates and cryptographically checks a version 2 recovery kit.
- Shows the recovery kit once for you to save offline.
- Starts the first encrypted sync automatically.
The initial upload uses a 15-minute setup window so it can finish while you move from device authorization to billing. The account page detects the new workspace and asks you to add a payment method, which starts the 30-day trial. After the setup window, further uploads require an active trial or subscription.
There is no separate recovery verification or first-sync step. docmancer cloud sync remains available as a manual retry when a connection is interrupted.
Add your VPS or another machine
On the VPS, install and set up Docmancer, then connect with the same account:
pipx install docmancer
docmancer setup
docmancer cloud connect
The new device displays a four-word pairing code. On an already connected machine, run docmancer cloud connect. Confirm that the four words match and approve the new device. Run docmancer cloud connect once more on the VPS to finish and pull the encrypted Shared Memory tree.
This is the normal two-device journey. Device IDs and cryptographic fingerprints remain available under advanced details, but you do not need to copy them manually.
Replace a lost device
If no connected machine is available, use the recovery kit when connecting the replacement:
docmancer cloud connect --recover
The command prompts without echoing the kit. A version 2 kit restores the workspace key and signs a short-lived approval for that specific pending device. The hosted service verifies the approval but never receives the recovery secret or plaintext key.
Older version 1 recovery keys remain valid for decryption but cannot approve a replacement. From a connected device, create a new version 2 kit before relying on device replacement.
What happens after the trial
The card-backed trial lasts 30 days. Unless you cancel, the selected monthly or yearly plan begins when the trial ends.
If a renewal payment fails, uploads continue during a fixed 7-day grace period. After grace, the workspace becomes read-only: local Docmancer keeps working, while pull and encrypted export remain available for 30 more days. The hosted workspace is then scheduled for deletion. Restoring billing before deletion resumes sync without changing local memory.
Canceling ends paid sync at the end of the current billing period. It never disables local Ask, Shared Memory, CLI, MCP, agent integrations, or docmancer web.
Account and local boundaries
Your account shows the subscription, lifecycle deadline, devices, recovery-wrapper availability, encrypted export, and remote deletion controls. It cannot browse memory, inspect local paths, retrieve the recovery kit, or confirm a local queue from the website.
Use docmancer cloud status for detailed local diagnostics and docmancer cloud sync to retry a transfer. These are diagnostic controls, not required onboarding steps.
Disconnect
docmancer cloud pause
docmancer cloud disconnect
Pausing stops transfer while retaining the resumable device identity and Cloud credentials. Disconnecting revokes this device and removes its local Cloud credentials. Neither action changes your local Markdown tree or cancels a workspace subscription used by other devices.