The reason that deal closed, the phrasing that lands — scattered across six tools, none searchable by AI.
Without a shared context, each prompt drifts. Outputs read like ten different vendors wrote them.
You pay, upload PDFs, pray. No visibility into what was chunked, what was retrieved, or why an answer was wrong.
Notion pages never get reviewed. Markdown-in-git does — and every edit is blamed, dated, and reversible.
Context is just files. `companies/acme.md`, `signals/pipeline-health/`, `sequences/linkedin-post-signal.md`. Open any editor — it just works.
Point at a git repo and every agent edit becomes a commit. Review in your PR tool, merge on approve.
Agents locate files by path and ripgrep, then read with full fidelity. No mystery chunk boundaries, no vector drift.
The Context panel has a full-height editor with ⌘↵ to save. No 320px chat-box clipping, no modal dance.
When an agent proposes a change — new case study, updated ICP — you see the diff before accepting.
Gong transcripts, reply threads, deal post-mortems can be piped into Context automatically, tagged and deduped.
If you ever cancel Black Magic AI, Context is a folder of markdown files. Walk away with everything.
Every agent reads the same Context. Update the ICP once, every outbound, qualification, and reply agent picks it up instantly.
Agents locate by filename, not cosine similarity. That means predictable retrieval — and reproducible outputs.
YAML frontmatter (`model:`, `audience:`, `updated_at:`) is parsed by every agent — lets you steer behavior per-file.
Ships with starter files for ICP, brand voice, objection library, case studies, competitor sheets — fill in the blanks.
Long-form research, product docs, battle cards sit alongside operational context — same store, same rules.
Pin exactly which sub-folder an agent may read or write. Reply Guy never touches your deal records.
Lives in `~/Library/Application Support/BlackMagic/context` (or your repo). Sync to cloud only if you opt in.
Edit in VS Code, Cursor, Obsidian, vim. Black Magic AI watches the directory and reloads agents as you save.
Because your team already reads and writes markdown in PRs, Notion, Linear. Databases need tooling. Files need nothing — and git gives you history, blame, review, and rollback for free.
Vault was the old name. As of 0.5.19 (April 2026) it is called Context everywhere — same store, clearer word.
Yes. Set `context_path` to any directory. A git-tracked folder is ideal — every agent edit becomes a reviewable commit.
Tested up to 50k files / 2 GB. Larger stores should be split by concern (ops, content, knowledge) so retrieval stays fast.
