Inside Coding Agents
v0.2 preview
SNAPSHOT DIFF · STRUCTURAL, NOT SEMANTIC

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.

SAME-SURFACE COMPARISON

Both records were observed on the same day. This compares evidence boundaries, not release chronology.

FROM · 2026-08-10

docs-observation

codex-2026-08-10-cli
Surface
cli
Freshness
current
Open snapshot →
TO · 2026-08-10

source@89a335e

codex-2026-08-10-source
Surface
cli
Freshness
current
Open snapshot →
REMOVED · STRUCTURAL0

Removed from this evidence boundary

No mechanism records were removed.

EVIDENCE-ONLY CANDIDATE1

Evidence type shifted

CHANGED · REVIEW REQUIRED—

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.

+ 11 paths
  • codex-rs/core/src/agent/control/spawn.rs
  • codex-rs/core/src/compact.rs
  • codex-rs/core/src/hook_runtime.rs
  • codex-rs/core/src/session/turn.rs
  • codex-rs/core/src/tasks/regular.rs
  • codex-rs/core/src/tools/approvals.rs
  • codex-rs/core/src/tools/handlers/multi_agents_v2/spawn.rs
  • codex-rs/core/src/tools/registry.rs
  • codex-rs/core/src/tools/router.rs
  • codex-rs/core/src/tools/sandboxing.rs
  • codex-rs/protocol/src/protocol.rs
− 0 paths

    None

    CLAIM RECORD SETS

    Atomic claims on both sides

    TO · 7 claimsagent-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.
    Back to Timeline →Open Evidence Explorer →