Your texts, your mail, your card charges and bills, your browser and YouTube history, what you saved, what you liked, your notes and your calendar, every prompt you ever typed. All the small things that show what you pay attention to.
One shape for all of it: things, events, links. Same page saved in two apps is one record.
charged$1,184.20 to ANA Airlines
received"Your flight to Tokyo is confirmed"
saveda thread on two weeks in Japan
watcheda talk on structured concurrency
sent"landed. dinner?"
paidPG&E, $142.60
visiteda page on commonplace books
likeda post about kerning by hand
prompted"make the sidebar follow the system theme"
commentedon a review: "this allocates on every keystroke"
searched"how did Locke index his notebook"
savedan article about SQLite's write-ahead log
02 why
This is how an agent learns your judgment.
Your taste isn't in any one file. It's in what you saved, what you starred, what you rejected, and how you asked last time. An agent that can search that stops guessing what you mean.
claudemcp · commonplace
youplan the japan trip. same vibe as portugal, under $4k, mid april.agentsearch "portugal" ·timeline --verb charged --since 2025-052025-05-12 txn bank:txn:2c7e40a9(TAP Air Portugal $812.40)2025-05-14 txn bank:txn:5b19f3d2(Casa do Conto $698.00 · 4 nights)2025-05-18 message chat:imessage:c81f4e("that tiny hotel in porto was the best part")2026-09-21 post url:redd.it/1g4x2k(Japan in two weeks: what worked)2026-09-28 txn bank:txn:7a3e9c1d(ANA Airlines $1,184.20)agentPortugal was nine days, $3,120, one small hotel you loved and no tours. You already bought the ANA flight for April 14. A ryokan in Kyoto like the Porto place, and the Reddit itinerary you saved cut to ten days, lands at $3,860. Want the day-by-day?
The more an agent knows about you, the less you have to say, and the more you can hand it.
03 sources
Sources, by how much setup they need.
Three work the moment you sync. Four are on the way. Everything else is one ask away.
Built in
source
what
needs
github
your pull requests, issues and stars
gh signed in
prompts
every prompt you typed into Claude Code and Codex
nothing, read from disk
imessage
your conversations
macOS, Full Disk Access
Coming built in coming
source
what
needs
X archive
your posts, likes, DMs and Grok chats, all of them
the archive from X's settings
X
new posts, likes and bookmarks every day
an X developer app, cents a day
Google Takeout
searches, YouTube, Maps, Chrome, Calendar
a Takeout export
Raindrop
bookmarks and collections
a CSV export or API token
One ask away
Anything with an export, a local database, an API or a CLI. Ask your agent, and the add-source skill has it write the source: one file, usually under 80 lines.
Money
bank and card CSV exportsApple Cardreceipts in Gmail
Browsing
ChromeSafariFirefoxEdgeArcany other browser
Mail and calendar
Gmail via Takeoutany mboxany .ics
Chat
SlackDiscordTelegram exports
Saves
InstagramPinterestRedditReadwise
Notes
Obsidianany folder of markdownApple Notes
Media
YouTube via TakeoutLetterboxdGoodreadsSpotify
claudeskill · add-source
youadd my obsidian vault to commonplaceagentwrote sources/obsidian.ts(61 lines)added it to commonplace.config.ts$ commonplace syncobsidian 2026-10-08 1,204 things 1,204 events
The skill works for any agent that reads files, not just Claude Code.
04 how it works
Three steps, one direction.
Fetch writes. Build reads snapshots. Agents read the database through one door. Nothing goes the other way.
commonplaceCLI ── search · timeline · show · stats└── mcpClaude Code, Codex, Claude Desktop, any MCP client
Fetch.
commonplace sync takes one snapshot per source per day into data/raw/<source>/<date>/. Each one is written through a .partial directory and made read-only, so a crash never leaves half a snapshot. The Claude Code plugin runs it whenever a session ends.
Build.
Every build starts from empty and replays every snapshot into one SQLite database. The same raw/ always gives the same database, so you can fix a source and rebuild years of history.
Read.
The CLI and the MCP server go through the same store, which shows a reader only the sources you allow. search, timeline, show, stats, and read-only sql for you.
05 privacy
What agents see is up to you.
Your data lives in data/, which never enters git. Agents never open the database. They go through the CLI or MCP server, which only show the sources you allow.
is the list of sources any MCP client may read. The --sources github flag on commonplace mcp narrows it for one client. imessage is in sources but not in mcp, so your messages stay local until you add it.
rules keep rows out of the archive entirely. They're never written.
A reader sees a row only if it may read every source that contributed to it, so a hidden source can't leak through a merge.
06 yours
A template you own. Not an app you install.
About a thousand lines of TypeScript in your own repo, next to your own data. Read it in an afternoon. Change anything.
Read it.
src/ is eight files. One schema, one builder, one store, two doors.
src/schema.ts things, events, links, verbs
src/build.ts replays snapshots; the only writer
src/store.ts every read, filtered by what you allow
src/cli.ts one door
src/mcp.ts the other
Change it.
A source is one file with two halves: fetch copies what the service gives, rows turns one snapshot into things, events and links.