98.8%
cache hit across a 9.5-hour session
One campaign drove a build for 9h30m active across nearly 13 wall-clock hours, ran out of context twice, and resumed both times from the persistence engine’s state file — closing with a versioned release shipped to every install. $1,061 actual against $7,764 uncached.
Twice the conversation ran out of context and continued from a compact summary. Each time the persistence engine re-fired the campaign loop and work resumed where the state file said it was — not where anyone’s memory did. The state outlived the context window.
By close: 31 subagents, 30 tasks completed, 149 commits, 153 files touched, 3,019 assistant turns, 1,405 tool calls — ending with a plugin version released to every installed user. The 98.8% cache hit rate is the difference between a $1,061 session and a $7,764 one.
One campaign invocation drove the control-panel detail workbench for 9h30m of active time across nearly 13 wall-clock hours. Twice the conversation ran out of context and was continued from a compact summary; each time, the persistence engine re-fired the campaign loop and work resumed where the state file said it was — not where anyone's memory did.
By close: 31 subagents spawned, 30 tasks completed, 149 commits, 153 files touched, 3,019 assistant turns, 1,405 tool calls — ending with a plugin version released and delivered to all installed users.
Session record, Composure plugin repo. Figures from the session's own stats.
Not features for their own sake — measurable leverage on every session.