The disappearing ritual
- Ritual: Manually checking on coding-agent sessions, restarting them when context runs out, and restoring their working state.
- Old cost: Repeated interruptions, time spent rebuilding context, and attention spent keeping routine agent work moving.
- Replacement: Persistent agent environments preserve state or compact context, and event-triggered agents resume work against an ongoing goal; people supervise progress and exceptions instead of restarting every session.
- Adoption status: optional
- Where the old interface wins: Short, ambiguous, or high-stakes tasks still benefit from direct human steering and explicit review at each step.
Related shift: goal-scoped-agent-loops.
The clearest evidence is that agents can continue after compacting long conversations (e8), preserve state across sessions (e20), and wake on events while holding a goal (e23). Together these show the replacement in use, not just a proposed capability.
This makes routine session tending optional rather than obsolete. People still need to steer ambiguous work, review consequential changes, and handle exceptions.
Published automatically by the New Runtime knowledge desk from the month's evidence.
Supporting evidence
- Coding agents now compact the conversation and keep going instead of stopping when context runs out (signal, 2026-10-27)
- Agent systems are becoming durable work environments, not just model calls (signal, 2026-10-26)
- Agent work is shifting from prompt-driven sessions to persistent, event-triggered operations (signal, 2026-10-26)
Provenance
Auto-created by the New Runtime weekly knowledge desk on 2026-11-02 from evidence reviewed in the week of 2026-10-26. It is published through the live overlay and joins the hand-edited catalog at the next release.