Vault and Agents
What is documented about agents reading the Vault, how to point one at a document, and how to tell whether a draft actually used it.
The Vault is not a setting you switch on. It is a set of documents an agent can read.
Readers and Writers Are Not the Same Set
The Connections panel lists what writes into the Vault. What reads it is a different list, and the heaviest reader is not on the panel at all.
| Reader | What it reads |
|---|---|
| The writer pipeline, behind Campaign Agents | The most of anything. Compiling a brief preloads your Company document, Agent notes/Style learnings.md, Agent notes/Team knowledge.md and Agent notes/Editorial guardrails.md, then gets live list, read and search tools over the rest of the Vault. Drafting loads the style documents every run and fails outright if Style learnings.md is missing |
| SAM | Reads before it drafts, and reads whatever you name: "draft this using brand/voice.md". It reaches the Vault as an ordinary MCP client on /mcp, using the same four tools anyone else gets in the default connection |
| Your own agents | The same four vault MCP tools, in the default connection |
And one that looks like a reader and is not:
| Not a reader | What it actually does |
|---|---|
| Competitor Monitoring | A producer. It writes Competitors/<domain>/. The only thing it reads is the list of paths, to decide whether a document is a create or an update |
Beyond the four documents the brief compiler preloads, which folders an agent reaches for and when is not documented. Do not build a folder on the assumption that a particular agent will find it. Name the path in the prompt instead, and check the output.
Telling Whether It Was Used
SAM usually names the documents it pulled from, in a line under the draft. If you get no such line, test it:
Run the prompt once
Ask for the draft as you normally would.
Add the one document you think is missing
A single objection, a single voice rule, one customer number.
Run the identical prompt again
If the draft changed, the document reached it. If nothing changed, name the path in the prompt and run it a third time. SAM says so directly when it found no voice rules to follow.
A Wrong Document Is Worse than a Missing One
Nothing checks a Vault document against your product. If a document asserts a capability you do not ship, agents will draft that claim, confidently, until someone edits the document.
Treat Vault documents as publishable claims. Anything you would not put on a slide in front of a customer should not be in a document an agent drafts from.
Vault over MCP
The four Vault tools ship in the default MCP connection:
| Tool | Use |
|---|---|
browse_vault | List or search documents. Takes query, pathPrefix, cursor, limit. |
read_vault_documents | Read up to 10 documents, and get the revision an edit will need. Takes offset and maxChars per document. |
create_vault | Build the first Vault from a public website URL. |
apply_vault_changes | Create, update, move or delete up to 20 documents atomically. |
For a coding agent: browse_vault with a pathPrefix, read_vault_documents
on the two or three that matter, then write.
Ready to Get Started?
See it on your own site, or open the app and build the first form.