Your AI session
library.
Every Claude, Codex, and Gemini session in one place. Browsable, pinnable, searchable — and never leaves your machine.
AI Session Library
One project, every agent, one view.
Spool watches Claude, Codex, and Gemini session directories today — and we're adding more agents as fast as they ship. Sessions are grouped by working directory, so opening a project shows everything you discussed there, regardless of which agent you used.
/Users/you/code/harborThe ten that matter, on top.
One click pins a session in its project — and onto the global Library Home. The ones you keep coming back to stay where you'll find them. No folders, no tags, no ceremony.
⌘K from anywhere — Fast or AI.
Fast runs FTS5 across every indexed session, instantly. AI hands the query to an agent on your machine, which synthesizes an answer with sources. The local label never goes away.
Your agent reads your library too.
Drop the /spool skill into Claude Code and ask things like "build on the auth-middleware discussion from last week." It shells out to spool search, returns matching fragments, and lets the agent load any session in full. Any tool-using agent can do the same via the CLI.
01 — Ask what it ought to know.
"Build on the auth-middleware discussion from last week." Claude invokes /spool, the skill runs spool search against your local index, and matching fragments flow back into the conversation.
02 — Sources don't decide retrievability.
A Claude session, an old Codex run, a Gemini brainstorm — all indexed under the same project, all returned by the same search. Whichever agent later asks gets all of it.
03 — The CLI is the public surface.
The skill is a thin wrapper around spool search --json. Any tool-using agent — or any script — can talk to your library the same way. Local in, local out.
Four things we won't compromise.
Spool's defaults aren't accidents. These are the four lines we won't cross.
Library, not search box.
The shell is the home — sidebar of projects, main pane of sessions. ⌘K is one entry point among several, not the whole product.
Local, always.
On-device index, on-device queries, on-device inference. Your machine is the only place your sessions ever live.
First-person metadata.
"You discussed this · Mar 15" beats "Claude Code · Mar 15." The library is yours; the language should say so.
Agents read it too.
Anything humans can browse, an agent can query. The /spool skill ships with the repo; the same JSON CLI is your public surface.
finally findable.