docslisted

# Docs Docs is the user's filesystem-first document library. Documents can live on the primary machine or another connected host, but the `patcher docs` command handles that routing through named vaults. ## Access documents Start with the smallest useful lookup: ```sh patcher docs vaults --json patcher docs list --vault <vault-id> --json patcher docs read <path> --vault <vault-id> ``` Use the path and vault exactly as returned. Paths are relative to the vault; do not guess an absolute host path or inspect the vault outside `patcher docs`. ## Docs @-mentions A Docs mention resolves at send time and appears in agent context as a `Docs document (<vault>/<path>)` block. Treat that block as user-provided source material from their document library: - Read and use its current contents even if the prompt only says “this” or “the attached doc.” - Preserve its meaning and distinguish its claims from your own inference. - Do not rewrite the mentioned document unless the user asks you to change it. - When your answer refers the user back to it, emit a Docs directive rather than an opaque filesystem path. ## Create and update documents Docs is a good destination for durable plans, specifications, write-ups, and HTML artifacts the user should be able to reopen. ```sh patcher docs pull plans/release-plan.md --vault personal --into ./docs-work # Edit ./docs-work/plans/release-plan.md with normal file tools. patcher docs status ./docs-work --diff patcher docs push ./docs-work