Convergence
Convergence is a desktop harness for directing many coding agents at once. It is in design. This page records the problem it addresses and the intent that governs how it will be built.
The problem
Working with many agents happens today through interfaces built for one conversation. The operator's entire view of a fleet is a chat stream. What context each agent was given, and what it currently holds, cannot be seen or steered. Parallel branches of work exist only as text scrolling past, so the state of the whole — what is exploring, what is finished, what is waiting on a decision — lives nowhere but the operator's head.
The scarcest input in such a system is the operator's judgment, and it has no tooling at all. There is no way to compare two candidate results side by side, no way to accept one part of the work and freeze it, no way to flag one line and leave the rest untouched. Every judgment is typed into the same chat box as everything else, and nothing the operator decides is kept.
The macrostate
One requirement governs the design: the operator's input lands only at the points where it scales — stating what must be true before the work, and judging what comes back after it — and both are made cheap. Concretely:
Context flow is visible: what each agent was given, what it holds, when it changed. Parallel work appears as branches converging on a trunk through a merge queue, because progress accrues only at the merge. Candidate results arrive in units small enough to judge in seconds, side by side; judgment cost sizes every surface. Accepted work locks, a flag produces an in-place patch, and the work only moves closer to done. And every judgment the operator makes is captured and encoded — a verdict becomes a rule, a rule becomes a check — so taste is paid for once and governs every run that follows.
Resolution with the philosophy
Superagency is causal power through structures, and attention is the input that does not scale. How to work with many agents develops the mental models: macrostates over microstates for the briefing side, convergence to one trunk for the judging side. Shipping is merging locates the control point of agent work at the join, and Encoding judgment as rules shows how a person's decisions govern runs they never see. Convergence is those claims built as one instrument.
Agent engines remain the engine underneath; Convergence is the harness and the visible surface. Status: defined and queued. The first prototype runs as skills and scripts inside the agent CLI, with the interface mocked through MCP; a dedicated application exists for the one capability a hosted assistant cannot provide, which is programmatic control of third-party coding agents.