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.
A direct message resolves to a personal scope, a group message to a group scope, and a channel to a channel scope; the resolver then mounts organization state read-only and the active scope read-write before a harness runs.
The monolith writes a future wake epoch, the always-alive dispatcher turns it into a trajectory step, and a backoff policy decides how soon the agent should think again based on whether the last wake produced visible work, only a thought, an idle, or an error.
The bundled code, dependency, and cloud-posture workflows name concrete scanners, require coverage disclosures when a tool is missing, and reserve fixes or cloud changes for reviewable code paths.
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
October 19, 2026 — New request observers expose outcomes and available token usage. Where you put them in the sequence changes when a tool can leave the queue. openai/codex
Pi Can Park Agent Tasks Until the Host Wakes ThemOctober 18, 2026 — Pi’s experimental durable harness now stores a sleeping task’s deadline and next step, letting a host alarm bring execution back later. The change separates continuing work from a continuously running process. earendil-works/pi
Goose Replaces V8 Without Giving Up Tool BatchingOctober 17, 2026 — The agent’s development branch swaps PCTX’s Deno-based runtime for Boa. It keeps the ability to discover tools and compose their results, while removing generated TypeScript and a chain of build workarounds. aaif-goose/goose
How Codex made the assignment the center of the appOctober 16, 2026 — Every’s origin story celebrates a desktop built around agents. The public record reveals the quieter achievement underneath: separating the machinery that does the work from the interface that helps people direct it. openai/codex
Gemini CLI Now Sends Gemini 4 Users to AntigravityOctober 16, 2026 — Google’s open-source terminal agent now warns that it is not optimized for Gemini 4 Argon. The recommendation makes its direction clearer while fresh implementation fixes show a project still being maintained. google-gemini/gemini-cli, google-antigravity/antigravity-cli
QM Drops Two Agent Loops but Keeps ChatGPT AccessOctober 15, 2026 — The shared workplace agent is narrowing its runtime choices to Pi and Claude. Its October 14 code change shows why keeping a model connection does not require keeping the agent software that shares its name. yc-software/qm, different-ai/openwork
Hermes Puts Assembled Agent Instructions into Code ReviewOctober 12, 2026 — A new snapshot shows reviewers the system prompt and tool definitions produced by the code. Nine controlled configurations turn changes in the agent’s instructions into something maintainers can compare directly. NousResearch/hermes-agent
Pi and Crush Tell the Terminal When They Need YouOctober 9, 2026 — Two released coding agents now share a status protocol for working, waiting and finished runs. It gives compatible terminals a way to surface the agent that needs attention—without deciphering each tool’s screen. charmbracelet/crush, earendil-works/pi, charmbracelet/bubbletea, openai/codex
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.