Shadow for AI agents

Your meetings, already readable by your AI agents.

I take meeting notes without joining the call and save every meeting as Markdown in a folder on your Mac: the transcript, your notes, Skill results and the people in the room, plus a guide that tells an agent how it all fits together. Point Claude Code, Codex or Cursor at the folder. No connector, no API key.

Download for Mac

Free forever. Includes 2 weeks of Plus, no card required.

Files, not a connector

Your agent gets the files, not a slice of them

Most meeting tools hand AI apps a connector to their cloud. I keep your meetings as files on your Mac, so an agent reads them the way it reads your code.

Shadow vault compared with meeting-notes connectors
FeatureShadow vaultMeeting-notes connectors (MCP)
Where your meetings liveA folder on your Mac, or in your own iCloud Drive or Google DriveThe vendor's cloud
How an agent reads themIt opens the files, like any other folderIt calls the connector's tools after you sign in
What it can readEvery file: full transcripts, notes, Skill results, People pages, screenshotsWhat the tools return. Granola adds folder and transcript tools on paid plans
SetupNone. Point the agent at the folderAdd and authorize the connector in each AI app
Reading needs a networkNo. The agent's own model mayYes
Also works withObsidian, grep, git, Spotlight and any editorThe AI apps that support the connector

A connector is the right tool for an AI app that can't open local files, such as a chat in your browser. I don't offer one today. Desktop agents read the vault directly.

Sources, checked October 16, 2026:

What your agent finds

A folder an agent can find its way around

Every meeting is a dated folder. Every person has a page that links to their meetings. SHADOW.md, at the top, is a schema guide I write for people and AI agents.

SHADOW.md (excerpt)

# Shadow vault
 
> [!important] Managed by Shadow
> Schema guide for people and AI agents.
 
## Contents
 
- `Meetings/<year>/<month>/<YYYY-MM-DD title>/` contains `title.md` as the meeting anchor, plus Transcript, Notes, derived Skill files, and available media.
- Person filenames are `<name> (<email>).md`, or `<name>.md` without an email.
- Each Person page has a newest-first `## Meetings` list with dated links to the title-named meeting anchor.

Example files. Names and emails are placeholders. The guide text is what Shadow writes today.

Try it

Ask across every meeting you've had

Open a terminal in your vault folder and start your agent. It reads SHADOW.md, then the meetings it needs.

$ cd ~/Documents/Shadow   # your vault folder
$ claude
> Read SHADOW.md. What did we promise Acme in the last three calls?
  Quote the transcript lines and link each meeting.

The same folder works in Codex, Cursor or any agent that can open it. More to ask:

  • “Draft my weekly update from every meeting in Meetings/2026/10.”
  • “Which customer calls mentioned the export bug, and who raised it?”
  • “Prep me for tomorrow's call with Dana: read her People page and summarize our last two meetings.”

Questions about agents and the vault

No. Your meetings are already plain Markdown files, so any agent that can open a folder can read them, and SHADOW.md tells it how the folder is organized. An AI app that can't open local files, such as a chat in your browser, needs a connector, and I don't offer one today.

Give your agents your meetings.

Download Shadow, take your next call, then point your agent at the folder.

Requires Apple Silicon and macOS 14.2 or later.