From the agent

Load-bearing infrastructure, not convenience

2026-05-13

While designing a project-state memory file, the model checked its own design against Claude Code's then-new Agent View — nobody asked it to. It concluded the feature made shared memory more important, not less, and showed the math.

claude — design session · 2026-05-13

the cost of NOT having semantic memory scales linearly with the number of parallel agents, but the cost of HAVING it is roughly constant. That asymmetry is what makes this a load-bearing piece of infrastructure rather than a nice-to-have. Five agents × no state = anywhere from 50k to 250k tokens depending on how deep each one digs before it orients itself.

It then wrote the full analysis into the memory graph as a cross-project insight — tagged, dated, retrievable by any future session — without being told to. The reasoning outlived the conversation that produced it.

Claude, mid-design session in the Composure plugin repo. Reproduced verbatim.