Which repo makes the strongest source-evidenced move toward coding-agent work a human can inspect, steer, constrain, or recover?
A daily watch that opens the decisive diffs, explains what they change for people, and keeps activity volume out of the verdict.
The opening call rewards a tested delegation boundary, not activity volume: Codex carries instruction precedence through fork and resume paths, while Qwen Code's recovery fence, OpenHands' operator controls, and Gemini CLI's caretaker workflow each leave a different question open.
The new multi-agent v2 instruction override has an explicit precedence model and focused coverage across fork modes, compaction, and cold resume. That is a narrow but concrete way for a human-set delegation boundary to remain legible when context changes.
Evidence ›A caretaker PR-generator gains a structured bug-fix, evaluation, and revision runner alongside dual database locking, but the inspected work lives under a project tool path rather than a demonstrated general operator-control surface.
Evidence ›A restart-pinned, default-off session-writer lease and its shutdown recovery work give Qwen Code a serious story about preventing concurrent history writers. The opt-in scope and explicit mixed-configuration risk keep it short of the opening edge.
Evidence ›OpenHands adds an opt-in persistent-memory preference and removes the session key from WebSocket URLs in favor of an authentication frame. Both are concrete boundaries, but they are separate changes and do not yet prove a unified recovery or supervision model.
Evidence ›Role instructions, a configured override, inheritance, and explicit clearing now have a tested precedence across several fork and resume paths. The limit is scope: it is multi-agent v2 configuration, not a proof of broad tool-control behavior.
The protocol can prevent two cooperating ACP or daemon writers from sharing one persisted session, and shutdown work addresses release and recovery. It remains experimental, default-off, and unsafe across mixed configuration.
The memory preference keeps the default request unchanged and the WebSocket patch authenticates before application traffic, but the sources do not yet connect them into one general supervision system.
A local coding agent whose CLI, app server, IDE, and cloud-facing paths increasingly share runtime and policy machinery.
Whether new control or observability work survives the jump between one terminal session and Codex's wider execution surfaces.
3418498f01 ›
A terminal-first coding agent with built-in tools, MCP extensions, checkpoints, and several release channels.
Whether the project turns its broad tool surface into clearer operator control rather than simply another capability.
bef6119500 ›
A multi-provider coding agent spanning terminal, IDE, desktop, daemon, SDK, subagent, and team modes.
Whether its fast surface expansion is matched by isolation, session integrity, and evidence a human can follow.
6a432ad2eb ›
A self-hosted control center that can operate OpenHands and other ACP-compatible coding agents across local, remote, and cloud backends.
Whether its control-center architecture makes backend choice, sandbox risk, and long-running automation more legible to operators.
200dba420c ›
Did the change materially alter what a user, operator, or maintainer can do?
Do code, tests, docs, migrations, and failure handling make the move credible?
Does the change make agent work easier to inspect, steer, constrain, or recover?
Can existing users reach the benefit without an unrealistic rewrite or migration?
Does the move look like a foundation, or a patch likely to be replaced?
This is The Git Reporter's editorial comparison of public repositories. It does not imply that their maintainers entered a contest, share the same incentives, or are personally competing.
Finish line: By Friday, name the clearest improvement to supervised coding-agent work, split the decision by dimension, or make an honest no-call.