Who owns saved agent context, and how can a reader tell whether it is current, scoped, and safe?
Look for provenance, namespace, retention, no-secrets rules, search scope, compaction visibility, and migration tests.
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.
Provider-specific session identifiers and expiry behavior are kept in typed session state instead of being flattened into one generic transport assumption.
Control-flow interrupts are separated from ordinary failures so a retry layer does not consume the operator's stop or handoff signal.
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.
Compatibility code and tests keep older serialized message history usable while the wire and extension model changes.
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 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 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 framework presents agent dependencies, tool inputs, and structured results through Python types and validation boundaries.
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.
Memory Bank turns saved context into a tested user-scoped capability. different-ai/openwork
Mario Zechner Kept Pi Compaction VisibleCompaction becomes visible maintenance state rather than silent compression. earendil-works/pi
Fenglanhua Made OpenClaw Prove Its Memory MigrationA memory migration becomes credible because the patch adds proof paths. openclaw/openclaw
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
API Discovery: One Reasoning-Effort Dial Across Provider IntegrationsJuly 21, 2026 — LangChain's new reasoning_effort interface lets a builder express an effort choice once across supported chat integrations—provided the selected model profile says that choice exists. langchain-ai/langchain
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
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
The Hard Part of an Agent Protocol Rewrite Is YesterdayJuly 17, 2026 — Tau is replacing its legacy agent protocol with Pi-compatible shapes, but its more consequential promise sits at the JSONL boundary: old sessions are meant to cross without pretending the old runtime still exists. alejandro-ao/tau, earendil-works/pi
Tau's Protocol Rewrite Keeps Yesterday's SessionsJuly 17, 2026 — Tau is choosing Pi-compatible extension and event shapes, but its public migration code makes a more human promise: a user's old session should have a route into the new system. alejandro-ao/tau, earendil-works/pi
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.