On April 29 I had three Claude Code sessions open across three different repos, and I was losing about ten minutes per switch just re-explaining where I had left off. ITEM-6872 was an event-page redesign on HTO. ITEM-6870 was turning the JIRA backlog page into a real triage cockpit. The third thread was not product work at all. It was me trying to figure out why my own memory across the day had gotten so expensive.
Each agent had partial context. Each switch cost me a paragraph of restated background. By mid-morning I had stopped pretending Google Keep and a stack of browser tabs were holding the line.
the morning I stopped pretending
I opened a fresh session and asked it to help me evaluate multi-window note tools. Not a productivity exercise. A direct response to the fact that I had three agents and four ongoing decisions and no shared surface for any of it.
What I actually needed was not a better notes app. I needed a place agents could read and write that was not inside a work repo. Putting personal context into a project repo is a category error. The repo is for the codebase. Personal coordination, half-formed plans, cross-project memory, none of that belongs there.
So I stood up an Obsidian vault. Local folder, markdown files, no service in the loop. Then I wired it to the agent workflow so a Claude session could read the vault as easily as it reads source code.
The vault is not the interesting part. The wiring is.
what the wiring actually looks like
Three pieces hooked together by the end of the day.
The vault itself, at G:/Projects/vault, organized in PARA folders. Areas, Projects, References, Sessions. Plain markdown so any agent on any machine can grep it.
A ben-chronicle inbox folder that any device can write to. The idea was simple. If I have a half-finished thought on my phone, it lands in ben-chronicle/inbox/. When I sit down at the desktop, the agent there sees it. No app, no sync conflict, just files moving through git.
A small set of Claude skills that knew the vault existed. /note to capture, /log to write to the day file, /next to surface the active thread. The skills do not do anything magic. They just remove the friction of telling the agent “go read this file first.”
Once the three pieces were in place, the context-switch cost dropped. Not to zero. The agent still needs to load whatever the current ticket is. But the meta-state, what I am working on, what is parked, what I decided yesterday and changed my mind about, lives in one place that every session can reach.
the parallel realization on the JIRA side
The reason this mattered so much that day was that I was simultaneously building a different command center for a different problem. ITEM-6870 turned /adminHTO/?p=pmhome into an action surface. Inline notes, comments, links, linked tickets, RICE breakdowns, all in one page. Yes, Comment, Reroute, Park, all without leaving the row.
The technical detail I cared about most was small. IIS was replacing non-200 responses with HTML error pages, which broke the inline action flow. So the endpoint had to return HTTP 200 and carry failure in the JSON body. Ugly, but it was the shape the surrounding system forced on me.
The bigger pattern was that I was building the same thing twice in one day. Once for backlog triage. Once for my own coordination. Both times the problem was the same. AI had made the underlying analysis cheap. The bottleneck had moved to the surface where I decided what to do with the analysis.
When investigation is fast, the cost shifts to the control surface. That is the part nobody warns you about when they sell you on AI productivity gains.
why the vault was infrastructure, not self-help
I have read enough productivity blogs to be suspicious of any post that ends with “and then I built a personal knowledge management system.” Most of those systems are a way of feeling productive without being productive.
This one was different in a specific way. The vault was not for me to read. It was for the agents to read. The point was not to organize my thoughts. The point was to give every Claude session in every repo a shared substrate so they stopped making me the only carrier of cross-project memory.
That changes the cost calculation. A personal Notion that I tend to alone is overhead. A markdown vault that three agents are reading on every session start is leverage. The work I put in once gets paid back every time an agent loads the relevant slice of context without me having to say it.
The ben-chronicle inbox was the same idea applied to time. I do not always know which machine I will be at when a thought arrives. I do not want to lose threads because my phone is not my desktop. A folder that any device can drop a file into, that the next session at any device will pick up, is the lightest possible version of cross-machine continuity.
the closing principle
When AI starts helping you on more than one front at once, your notes stop being optional and start acting like infrastructure. The vault is not a productivity system. It is the persistence layer for a workflow that now spans multiple agents, multiple repos, and multiple machines, and that workflow no longer survives without it.