Documents

The documents surface is a working area for arbitrary notes and files inside Dispatch. Unlike preferences (a single global file) or people (one per contact), documents have no fixed shape. They are whatever you and the agent want them to be: a draft, a research dossier, a meeting recap, a decision log.

Documents live under /documents/ and are accessed through the same file tools the agent uses for everything else.

What it does

• Stores arbitrary notes. Anything that doesn't fit in preferences, people, daily notes, or todos.
• Read and write through tools. The agent uses read_file, write_file, and edit_file against /documents/ paths.
• Survives across runs. Documents are durable and queryable across sessions.
• Surfaces in search. The agent's search tool indexes documents alongside other entity types.

How to use it

The most common pattern is to start a document by asking the agent to write one.

• "Write a one-pager on what we know about the Acme deal so far."
• "Save this thread as a document so I can come back to it."
• "Update the offsite-planning doc with what we decided today."

Documents the agent creates appear in /documents/ with a slug derived from the topic. You can also create one directly.

Limits and behavior

• Free-form path structure. Subdirectories under /documents/ are allowed. The agent picks reasonable slugs by default; you can rename.
• Per-organization. Scoped to the current organization, like all memory.
• Not a wiki. Documents are not designed for collaborative real-time editing across users; they are a working area Dispatch uses on your behalf.

Related

• Preferences: for standing instructions, not arbitrary notes.
• Daily notes: for time-bounded journal entries.

For agents

• Documents live under /documents/ and are read/written via the standard file tools.
• No fixed schema; the surface is for arbitrary notes, dossiers, drafts, and recaps.
• Indexed by the search tool alongside other entity types.
• Per-organization; not cross-user collaborative.