Topic

Runtime

The layer agents run on: sessions, turns, recovery and compaction.

All technical writing

2026

  1. A browser that writes down the form instead of sending it

    An agent-first browser engine runs a click the way page code expects, then records a form submission and stops, leaving network access, protocol transport, threads and session state with the application that embeds it.

    BrowsersAgent systemsRuntimeArchitecture

  2. Keeping a coordinator responsive while its workers are busy

    When a coordinator shares a process with its workers, load and every recovery action land on both. How the deciding agent was separated from the process that holds the tree, sandboxes and workers, what the relay between them costs.

    SelectedAgent systemsOrchestrationArchitectureRuntime

  3. Keeping long agent turns steerable and within their context budget

    A steer could wait 40 minutes behind a foreground command, and a rule meant to spare people from summaries let threads overflow. Bounded yields and a budget judged on the request actually sent address both.

    Agent systemsRuntimeContextCompaction

  4. Recovering a service deployment after its visible work has already happened

    What a deployment controller has to do when a route has gone out and the catalog write fails: why a completed saga step can't be trusted on resume, how a retry recognises its own intent, and why cleanup is bound to the version it read.

    RuntimeVerificationDeploymentReliability