source@89a335e
codex-2026-08-10-source- Surface
- cli
- Freshness
- current
Codex
Diff
The automatic diff compares only Registry mechanism sets, Claims, Source Maps, and evidence types. Without a reviewed change record, structural differences are never labeled as changed behavior.
Both records were observed on the same day. This compares evidence boundaries, not release chronology.
source@89a335e
codex-2026-08-10-app-server- Surface
- server
- Freshness
- current
Added mechanism records
Removed from this evidence boundary
Evidence type shifted
No evidence-type shift exists on retained mechanisms.
Behavior change is not inferred
A separate human-reviewed diff record is required before labeling behavior as changed.
SOURCE MAP DIFF
Path changes
Path changes describe the inspection boundary, not a change in file behavior.
codex-rs/app-server/src/lib.rscodex-rs/app-server/src/message_processor.rscodex-rs/app-server/src/transport.rs
codex-rs/core/src/agent/control/spawn.rscodex-rs/core/src/compact.rscodex-rs/core/src/hook_runtime.rscodex-rs/core/src/session/turn.rscodex-rs/core/src/tasks/regular.rscodex-rs/core/src/tools/approvals.rscodex-rs/core/src/tools/handlers/multi_agents_v2/spawn.rscodex-rs/core/src/tools/registry.rscodex-rs/core/src/tools/router.rscodex-rs/core/src/tools/sandboxing.rscodex-rs/protocol/src/protocol.rs
CLAIM RECORD SETS
Atomic claims on both sides
agent-loopAt the pinned Codex source revision, run_turn repeatedly samples the model, executes requested function calls, feeds results into later samples, accepts steering input, and stops when follow-up work is no longer required or a stop/error path wins.context-compactionThe pinned Codex turn loop checks context limits before and after sampling and can replace history through local or remote compaction before resuming the same turn.event-streamThe pinned Codex protocol defines typed events for turn lifecycle, streamed content, tools, approvals, compaction, hooks, and collaborative-agent activity, and the turn implementation emits those events through the session boundary.execution-policyThe pinned Codex core models approval decisions separately from sandbox transformation, with policy-dependent outcomes that can forbid, request approval for, skip approval for, or sandbox a tool attempt.extension-runtimeAt the pinned revision, Codex assembles selected skills and plugins into turn context and runs typed lifecycle hooks around session start, tool use, permissions, stop, compaction, and session end.subagent-orchestrationThe pinned Codex core registers multi-agent tools for spawning and communicating with child agents and implements spawn through a dedicated agent-control boundary rather than inside the main sampling loop.tool-dispatchThe pinned Codex core separates model-visible tool specifications in ToolRouter from runtime registration and collision handling in ToolRegistry, then resolves each parsed call to its registered runtime.client-server-protocolThe pinned Codex App Server accepts JSON-RPC requests and notifications over selectable stdio, Unix-socket, or WebSocket transports and dispatches typed requests through dedicated processors.