Set up local client folders, save outputs to disk, track raw documents, and organize files.
Local Client Folders
Armbrain can create and manage a structured folder for each client on your machine. This organizes briefs, content, notes, reports, strategy, and handoffs.
Set Up a Local Folder
"Set up a local folder for Acme at ~/Clients/Acme Corp"
This sets the client's local folder and creates an Armbrain/ subfolder structure:
~/Clients/Acme Corp/
Armbrain/
Briefs/
Content/
Meetings/
Reports/
Strategy/
Handoff/
The path is stored on the client mind and persists across sessions.
How It Gets Used
Once a local folder is set, anything Armbrain generates lands in the right subfolder automatically:
- Meeting briefs go to
Briefs/ - Content pieces go to
Content/ - Meeting notes and follow-ups go to
Meetings/ - Performance reports go to
Reports/ - Strategy documents go to
Strategy/ - Handoff exports go to
Handoff/
Saving Output
When you ask Armbrain to save something, it writes the document to the client's local Armbrain folder.
Save a Brief
"Save that meeting brief to disk"
Armbrain writes the content to Armbrain/Briefs/2026-03-20-brief.md (auto-generated filename based on date and type).
Save with a Custom Filename
"Save the strategy document as q2-strategy-final.md"
Output Types
| Type | Subfolder | Use Case |
|---|---|---|
brief | Briefs/ | Meeting prep briefs |
content | Content/ | Blog posts, emails, social media drafts |
meeting | Meetings/ | Meeting notes, follow-up emails |
report | Reports/ | Client performance reports |
strategy | Strategy/ | Strategy decks, planning docs |
handoff | Handoff/ | Client handoff documents |
When No Local Path Is Set
Without a local folder, Armbrain skips saving with a note. You never lose work, but files won't write to disk.
Raw Document Tracking
When you ingest a document, Armbrain keeps the full original text, not just extracted memories:
- Traceability: Every memory links back to the document it came from
- Re-extraction: Armbrain can re-process the original later with improved prompts to pull out more
- Audit trail: You can see exactly what was ingested and when
List Stored Documents
"Show me the documents stored for Acme"
You see recent source documents with their origin, size, process count, and last processed date.
Document-to-Memory Links
Every memory links back to its source document. The same link applies to manual notes.
Watch Paths (Future)
You'll be able to point Armbrain at extra folders to watch for new documents, so files dropped there get ingested automatically. To set one up:
"Watch ~/Dropbox/Acme/Meeting Notes for new documents"
Practical Example: Organized Client Workflow
Setup (once per client):
"Set up a local folder for Acme at ~/Clients/Acme Corp"
After a meeting:
"Prep my meeting with Acme and save it"
Brief saved to ~/Clients/Acme Corp/Armbrain/Briefs/2026-03-20-brief.md.
Writing content:
"Write a follow-up email to Sarah about the Q3 budget discussion"
"Save that as a meeting note"
Email saved to ~/Clients/Acme Corp/Armbrain/Meetings/2026-03-20-meeting.md.
End of engagement:
"Generate a handoff document for Acme"
Handoff saved to ~/Clients/Acme Corp/Armbrain/Handoff/2026-03-20-handoff.md.
All outputs are organized, dated, and findable without Armbrain running.
Error Reference
| Problem | Cause | Fix |
|---|---|---|
| "Nothing was saved" | The output type wasn't recognized, or there was nothing to save | Ask again with a clear document type (brief, content, report, etc.) |
| "No client selected" | You haven't switched to a client | Switch to the target client first |
| The file didn't appear on disk | Disk full, a permissions issue, or the folder path is too long | Check that the client's local folder exists and is writable |