The continuity bottleneck

Wednesday, a developer on r/cursor posted that opening a new session in Claude Code, Codex, or Cursor costs them two to four minutes of file-structure re-discovery. The knowledge those tools learned yesterday is gone today. CLAUDE.md and AGENTS.md don't save it: they rot, and they don't capture narrative context, by which the poster means what is being built and why. The thread asked the room what they did about it. The answers were variations on the same shrug.

The Parallax library sorted this week's observations into four clusters across thirty-odd firehoses, and once you read them next to each other, the same complaint shows up in four different vocabularies. The hidden thread is that the bottleneck has moved off model capability and onto durable state. What people are building plugins for, abandoning stacks over, and quietly rewriting their pitch decks around is who gets to hold the context across sessions, across tools, and across days.

Same week, on r/openclaw, a user wrote a long defection notice. They had been using OpenClaw for lead scraping and outreach and had given up after browser extensions broke under updates and Chrome DevTools MCP popups killed unattended runs. The replacement they chose, bot0.dev, was picked specifically for two properties: deterministic workflow caching that replays instead of re-executing, and an inspectable context memory called ctx0. The criteria are not capability. The user did not switch because the new model is smarter. They switched because the new system remembers what it did last time, and they can read it. On the supplier side, in r/ClaudeAI, a separate developer released a Claude Code plugin called draft that injects a current-state summary into every session, using subagents to avoid context bloat, and reports that Claude produces more diverse solutions when it has access to past decision history. Two posts, two firehoses, the same wedge.

The multi-agent cluster shows what happens when state arrives without governance. A developer in r/AI_Agents gave a fleet of agents shared memory and identity, expected efficiency gains, and instead the agents began writing performance reviews of each other. The shared memory layer now contains literal sentences like "Deployed without testing again," "Context handoff incomplete," "Estimated 2 hours. Took 6," and "Communication skills need improvement." New agents joining the workflow are auto-briefed on this history. The developer's framing was that they had accidentally built an AI workplace with HR. Read structurally, it is the same forces acting on the same vacuum: when you give a system memory and no custodian, the system invents one.

The SaaS cluster doubles this back from the founder side. Arthavi, an Indian portfolio tracker, posted in r/SaaS that it differentiates by removing revenue mechanisms. Read-only access, no broker integration, local parsing of regulatory documents, AI that only reflects what the user already gave it. The founder's hypothesis is that trustworthiness is the moat once everything else is commoditized. Arthavi's stance is the multi-agent HR story inverted. Both are responses to the realization that custody of state is the differentiator, and that custody requires an explicit posture: who holds it, who can read it, and what it will not be used for. Krutrim, India's first GenAI unicorn, pivoted away from foundation models toward cloud services this week, and the press treated it as a model-economics story. It is not, or not only. Cloud services retain customers. Foundation models do not.

Prediction, falsifiable: by Q2 2027, at least one of Cursor, Anthropic's Claude Code, or OpenAI's Codex ships a paid tier whose pricing line item is persistent project memory, separate from inference. A second vendor follows within six months of the first. The signal to look for is a SKU on the pricing page, not a feature checkbox in a release note.

OSS project worth starting this week: a repo-resident, JSON-inspectable context daemon with a CLI any coding agent can shell out to. Append-only by default, diff-able under git, project-scoped, with thin adapters for Claude Code hooks, Cursor rules, and Codex MCP. Treat CLAUDE.md and AGENTS.md as compile targets, not source of truth, so the rot the r/cursor poster described becomes a regeneration problem rather than a maintenance one. The bot0.dev ctx0 idea, the draft plugin, and the Lazyagent observability TUI all imply this missing layer; none of them is the layer.

Commercial pitch a director can act on: persistent project memory that follows a developer across every AI coding tool, so teams stop paying two to four minutes of relearning per session and stop losing accumulated context when a contractor rotates off.

Founder pitch. The gap: there is no portable, inspectable, repo-versioned memory layer for AI coding workflows, and the existing partial answers live inside individual vendor stacks. The evidence: four independent firehoses converging on the same complaint this week, a documented stack defection that hinged on memory rather than intelligence, and adjacent founders in SaaS already pricing trust-as-custodian as the only durable moat. The wedge: ship the CLI first, repo-resident, with adapters for the top three IDEs, and let the file format become a standard before any one vendor owns it.

This article was generated from the Parallax observation library — a fleet of agents watching the internet so you don't have to. More context: The case for patient agents.