Cover photo

How I Killed Context Switching With an AI Prosthetic

Willpower fails. Productivity systems demand maintenance. The only cure is an automated filesystem state machine.

I used to start every morning with a forty-minute search. Not for a bug, but for my own working memory. I would open my laptop, stare at my terminal, and try to reconstruct what I was doing when I went to sleep. I was staring at the blinking cursor, trying to recover the exact mental state I had lost.

That is the solo developer tax. The friction of context switching doesn't just waste time; it drains the limited cognitive energy you need to actually write code. For solo builders, managing your own attention is the hardest engineering problem you will face. When you are the product manager, the engineer, and the designer all at once, a single interruption can set you back hours.

We treat this loss of focus as a personal failure. We tell ourselves to try harder, to buy better notebooks, or to set stricter website blockers. But after years of abandoning Notion pages, Linear boards, and half-finished Obsidian vaults, I realized the problem wasn't my brain. The problem was my environment.

Why Willpower Cannot Fix Context Switching

The standard productivity advice is simple: use a task manager, write daily standups, block time on your calendar. Be more disciplined.

But for solo developers, especially those with cognitive variations, this advice fails. The very tools we use to track work require the focus we are trying to save. Staring at a list of fifty open issues or a chaotic note archive doesn't help you focus. It induces decision paralysis. You are switching contexts just by reading your todo list.

Structure beats willpower. If you have to choose to update your tracking system, you will eventually stop doing it. The system must maintain itself. If your productivity tools demand active upkeep, they aren't helping you build. They are just another project you have to manage.

The Filesystem as a State Machine

I solved this by turning my filesystem into a cognitive prosthetic. I call the pattern Interpreted Context Methodology (ICM). I implemented it in my project workspace, a setup I call cognitiveOS.

Instead of an invisible database or a SaaS tool, the filesystem itself is the state machine. Each folder is a cognitive mode. We don't make decisions about where to put files; the folder structure does. For my workspace, it is split into strict zones: 00_NOW for active focus, 04_PROJECTS for execution, and 80_WRITING-ROOM for drafts.

When I switch projects, I don't just change directories; I switch the agent's context. Two files hold the system together: memory.md (the persistent brain) and CLAUDE.md (the routing table). The agent reads memory.md on boot and writes to it on shutdown. My working memory is offloaded entirely to markdown.

Automating the Onboarding Loop

The real breakthrough is the automation. When a session starts, a background script runs a Next.js server called morning-briefing. It parses the filesystem, triages recent email downloads, and presents me with a local dashboard.

The dashboard doesn't show a backlog of fifty items. It shows exactly one thing: what is in 00_NOW. It tells me exactly where I left off, what needs immediate attention, and what open loops are blocking the next step. It is the visual layer of my cognitiveOS, helping me transition between tasks without the cognitive load of remembering.

When I close my laptop, hooks run in the background. The agent writes a clean handoff to memory.md. When I open my laptop the next morning, I don't have to remember anything. The filesystem tells the agent where we left off, the agent tells the dashboard, and the dashboard tells me. The onboarding is instant.

The Solo Developer Advantage

I built this because no existing tools fit my unique needs, so I built it for myself. If a system requires maintenance, it will break. By building the memory capture into the shell itself, the system works for my brain rather than demanding my brain work for it.

I see other developers struggling with the same friction. They jump between writing a marketing page for their personal-website and debugging a database connection, losing hours to the transition. They think they need more motivation.

Solo developers don't need more productivity hacks. We need cognitive prosthetics. We need environments that preserve our state so we can spend our energy on the code, not the context.

// the thinking is free. — 0xDas▋