Can the operator see enough of the agent system to steer, review, stop, and resume work?
Inspect review surfaces, status indicators, session threads, branch summaries, pending work, and evidence rendering.
A project appears here because the boundary is relevant to its documented or reported architecture. The evidence label says how far this Atlas has checked the mechanism.
The runtime can inspect pending input, resolve permissions and tool mode, run hooks, and add higher-authority context before a model invocation is assembled.
BeforeAgent and related hook boundaries let the runtime attach delimited context or block a run before the next agent step.
Release and issue trails distinguish account, network, proxy, authentication, and CLI behavior when the implementation surface is not equally open.
Provider-specific session identifiers and expiry behavior are kept in typed session state instead of being flattened into one generic transport assumption.
Recovery rebuilds the client registry as a coherent unit instead of leaving a partially alive tool menu in place.
Thread-local approval state narrows the risk that consent for one task becomes ambient authority for another.
Diff evidence becomes trustworthy only when the runtime records enough repository state to distinguish agent output from a guessed comparison.
An adapter can turn a public API description into model-visible tools while keeping schema validation, credentials, execution, and result handling separate.
A sign-in flow remains pending with a claim link and explicit state instead of turning an operator action into an arbitrary elapsed-time failure.
ACP support is tied to release evidence so compatibility is more than a capability claim in documentation.
Compatibility code and tests keep older serialized message history usable while the wire and extension model changes.
A retained run keeps changes beside the working tree until a reviewer selects, applies, releases, or discards the output once.
The project repeatedly merges Codex upstream while owning release, installer, cache, documentation, and harness changes for a different product bet.
The project documents an automation mode in which permission prompts are disabled, making the trust placed in the surrounding CI or sandbox environment explicit.
The documented daemon mode serves one agent session to multiple clients over HTTP and server-sent events, turning client identity and session ownership into protocol questions.
The project documents a Plan mode for investigation and strategy, an Act mode for execution, per-action approvals, optional auto-approval, diffs, and reversible checkpoints.
The project documents a local Rust agent that connects provider choices and external capabilities through standard extension contracts instead of baking every integration into one model path.
The same control surface can connect to an agent running directly on a host, in Docker, on a VM, or in a cloud service; the README explicitly warns that an unsandboxed server has full filesystem access.
The agent can complete a web action while still violating the user's intended destination, account, or consequence; evaluation must inspect the effect, not only task completion.
Review panels make agent output easier to inspect before acceptance. anomalyco/opencode
Mario Zechner Makes Pi Sessions Render Their Own EvidenceDurable session entries become a place to show proof, not just text. earendil-works/pi
Tau Turns Agent Architecture Into OnboardingArchitecture notes become onboarding infrastructure for contributors and agents. alejandro-ao/tau
July 21, 2026 — Pi's latest accounting patch treats compaction, branch summaries, and tool-result hooks as model work with receipts—not invisible overhead beneath an agent's final answer. earendil-works/pi
An Agent's Sign-In Link Is Not a TimeoutJuly 21, 2026 — OpenWork's newest MCP work carries a provider's structured authorization link through a failed tool call, so the person who owns the account can act instead of watching an agent retry the wrong problem. different-ai/openwork
The Diff Can't Be Guesswork Once an Agent WritesJuly 20, 2026 — OpenClaw is making a simple rule explicit: when an agent writes a file, a review surface should show the patch it can prove—and show uncertainty when it cannot. openclaw/openclaw, openai/codex
Codex Stops Asking Its Subagents the Same Question TwiceJuly 20, 2026 — A Codex TUI patch cuts duplicate status reads by treating new, resumed, and actively streaming agent threads as different lifecycle states. openai/codex, NousResearch/hermes-agent
API Discovery: Tail a Delegated Hermes Agent at WorkJuly 20, 2026 — Hermes' public delegate_task surface can now return a live, local log for each child—useful when a background fan-out needs observation without flooding the parent conversation. NousResearch/hermes-agent
A Computer-Use Agent Needs a Second Meaning of SuccessJuly 19, 2026 — Hermes now tells a desktop-driving agent whether an input merely reached a driver or was actually confirmed to have changed the interface—and it makes foreground escalation a separate decision. NousResearch/hermes-agent
Gemini CLI’s Caretaker Has Permission to Read, Not to ActJuly 18, 2026 — Gemini CLI’s new issue-triage worker gives its model a read-only repository view, then keeps labels, comments, retries, and escalation in a separate validated program. google-gemini/gemini-cli
Builder Work: When an MCP Session Dies, Rebuild the Whole RegistryJuly 18, 2026 — Crush’s agent-attributed MCP recovery work teaches a hard-earned rule: a connection is not back until every capability it advertises is back too. charmbracelet/crush
This is a mechanism comparison, not a feature score. “Reporting underway” means the Atlas has not verified the relevant path; it does not mean the project lacks it.