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.
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 launch command configures distinct protocol, context, compaction, state, and permission adapters for Claude Code, Codex, OpenCode, OpenClaw, Hermes, and Pi instead of treating one compatible endpoint as complete agent equivalence.
A BEHAVIOR.md names recurring expected conduct and its failure boundary; prompts, skills, traces, rubrics, and scorers can change around it without silently becoming the source of truth.
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.
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
September 4, 2026 — Hermes is redrawing a deceptively important line: a correction learned while doing one task belongs with that task's skill, while persistent memory is for facts that should matter everywhere. NousResearch/hermes-agent
Before Codex Trusts a Workspace, It Stops Letting the Workspace Choose Its HelpersSeptember 3, 2026 — A merged Codex change moves automatic pre-trust helper lookups to known system locations, sanitizes plugin-sync Git, and makes diagnostics inspect a workspace-influenced path without running what they find. openai/codex, google-gemini/gemini-cli
API Discovery: Let an Agent Notice When Its Reasoning Was DroppedSeptember 3, 2026 — Pydantic AI now carries an Anthropic thinking-block fallback through later turns—but the useful operator move is to expose the loss, then fix the unstable prompt prefix that caused it. pydantic/pydantic-ai
Builder Work: An Approval Must Point to This Exact InvocationSeptember 3, 2026 — Microsoft Agent Framework’s Copilot-assisted approval repair shows the craft worth stealing: authorize one stable local occurrence, not a provider’s reusable tool-call label. microsoft/agent-framework
Builder Work: A Socket Path Is Not a Permission BoundarySeptember 2, 2026 — Qwen Code’s Claude-assisted inbox hardening shows the reusable craft: treat an endpoint and its credential as one capability, then erase both before a child process can inherit them. QwenLM/qwen-code
Kilo’s Migration API Lets Agents Resume Without Shipping Their TranscriptsSeptember 1, 2026 — Kilo Code’s public migration endpoint lets a configured server rediscover Claude Code or Codex history it can read, create a Kilo session per source, and make a normal retry a skip instead of a duplicate. Kilo-Org/kilocode
Builder Work: Mastra Tests Memory Prompts Against Their Own NoiseSeptember 1, 2026 — Mastra’s new memory simulator freezes the data-generating boundary, isolates each prompt arm, and makes a same-prompt A/A run expose the noise that a flashy A/B result might otherwise hide. mastra-ai/mastra
A Completed Agent Run Is Not a Successful OneSeptember 1, 2026 — OpenHands now treats a finished process and a successful task as different facts—so an automation can be completed, blocked, and operationally failing at the same time. OpenHands/OpenHands
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.