openai/codex
The visible prompt is only one input to the first requestThe runtime can inspect pending input, resolve permissions and tool mode, run hooks, and add higher-authority context before a model invocation is assembled.
How does a parent agent prove what a child did, received, and returned?
Find parent IDs, child IDs, sent payloads, received results, lifecycle states, cancellation behavior, and merge rules.
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.
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 retained run keeps changes beside the working tree until a reviewer selects, applies, releases, or discards the output once.
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 human-in-the-loop suspension backed by storage so a workflow can pause and later resume from durable execution state.
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 framework presents agent dependencies, tool inputs, and structured results through Python types and validation boundaries.
The repository separates agent construction from explicit multi-agent workflow and deployment APIs in two language ecosystems.
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.
Crew and task abstractions make responsibilities explicit, but dependable delegation also requires lifecycle, authority, result, cancellation, and evidence semantics.
Structured send and receive logs make subagent work traceable. openai/codex
Builder Work: 143 Turns Coding Agents Into Team InfrastructureA builder project routes agents through durable sessions, sandboxes, previews, and PRs. assembledhq/143
Agent Events Are Getting Return AddressesReturn addresses explain why event identity matters before delegation scales. openai/codex, openclaw/openclaw, charmbracelet/crush, NousResearch/hermes-agent
July 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
Codex Keeps the Prompt After You Interrupt ItJuly 16, 2026 — A new Codex TUI change treats an interrupted request as part of the record, then gives the next instruction a clean composer. openai/codex
Open Interpreter: roots, maintainers, and the contributor advantageJuly 16, 2026 — The new Rust Open Interpreter is openly building on Codex; its public advantage is upstream leverage, not a proven inside track. openinterpreter/openinterpreter, openai/codex
Background Agent Work Needs a ReceiptJuly 15, 2026 — Hermes and OpenClaw are fixing different failure windows in the same promise: delegated work has to arrive somewhere a person can use it. NousResearch/hermes-agent, openclaw/openclaw
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.