The inbox and compiling
What the inbox is, how to add transcripts and notes to it, what a compile does, and how to run a compile on a schedule in each AI app.
The inbox holds raw material: call notes, meeting transcripts, pasted email threads. A compile is a run in which your AI reads new inbox notes, files what they say into organized pages and records, and marks each note as compiled. Some people call this "dreaming": like sleep, it turns the day's raw notes into lasting knowledge.
Adding to the inbox
- From your AI: "Add this call transcript to the Baffin inbox." Any connection with read and write access can do this.
- From the web app (owners): open Library, choose Add, then Paste notes for AI to organize, and paste the text, or upload a .txt, .md, .srt or .vtt file. Exports from Otter, Granola and Fireflies work. Add a Title (optional) and choose Add to inbox. One note can be up to 960 KB.
Inbox notes appear under Inbox in the Library. Search leaves them out until they are compiled. If your writing rules protect the inbox, a new note waits in Review first. Writing has to be set up before anything can be added. See AI instructions.
What a compile does
- Your AI lists the inbox notes that haven't been compiled yet.
- It reads each one and creates or updates pages and records, following Baffin's steps and your compile rules.
- It adds a short "Compiled" section to each note, listing what it produced.
A note and everything made from it publish together. If one part needs review, they wait in Review together. A note that's already marked is skipped next time, so running a compile twice does no harm.
Shaping compiles
Owners set this up in Settings, then AI instructions:
- Turning notes into pages: plain sentences about where things go, what to extract and which formats to use. For example: "File supplier agreements under Suppliers, one page per supplier."
- Maintenance tasks: pages kept up to date during compiles. Use Add from template to pick a TODO roll-up, a Contacts directory, a Structural review (propose only) or Connections between topics. Or use Add a custom task. Each task is off until you switch it On, writes only the pages it lists, and runs on Every compile or Only when asked.
Choose Save when you're done.
Running a compile
On the same tab, choose Copy routine prompt. This copies a one-line prompt that names your knowledge base. Paste it into any connected AI with read and write access, and it runs one compile.
Running it on a schedule
Baffin doesn't run compiles on its own. Your AI app runs them. Use the copied prompt as the instructions for a scheduled task, or ask your AI to "get me started with Baffin" and it walks you through scheduling. It confirms the time and your time zone first, and it should say a schedule exists only once your app has created it.
- Claude Code:
/schedulecreates a routine that runs in Anthropic's cloud. It uses the connectors on your Claude account, so also add Baffin as a custom connector at claude.ai, not only in Claude Code. - Claude.ai: if your plan offers scheduled routines, give the routine the prompt. Baffin must be connected there as a custom connector.
- Claude Desktop: scheduled tasks run on your computer, so they run only while it is awake.
- ChatGPT: check whether scheduled tasks can use connectors on your plan. If they can't, run the prompt by hand.
- Codex, Cursor and VS Code: we don't know of a built-in way to run a scheduled task that uses Baffin. Run the prompt by hand, for example each morning.
Once a day is usually enough.
Checking results
Open Library, then More, then Library health. The Inbox section lists notes still waiting to be compiled, and Compile runs lists recent runs. Changes that need approval are in Review. See Review AI changes.