Skip to content

Restore fresh transcript attachment for modern Codex rollouts - #41

Merged
Juliusolsson05 merged 32 commits into
mainfrom
fix/ordered-rollout-prompt-evidence
Aug 26, 2026
Merged

Juliusolsson05 merged 32 commits into
mainfrom
fix/ordered-rollout-prompt-evidence

Conversation

@Juliusolsson05

@Juliusolsson05 Juliusolsson05 commented Aug 24, 2026 •

Copy link
Copy Markdown
Owner

Summary

  • restore modern Codex fresh transcript attachment using process-wide, fail-closed rollout ownership built from seven sanitized real recordings
  • reconcile fresh prompt and resume-lineage evidence through one coordinator with pre-spawn exact ownership, ordered generation snapshots, bounded retention, and content-safe diagnostics
  • reconstruct submitted prompts from real xterm chunks using Codex 0.149.1 editing semantics and provider-proven Tab queue state
  • bind accepted fresh, exact-resume, and copied-lineage tails to the verified filesystem generation
  • isolate diagnostic/error observers from lease and queue semantics and close watcher, participant, path, preparation, and raw transport-cache lifetimes

Root cause

Modern codex-tui rollouts no longer emit the legacy event_msg.user_message shape. The old claimant inspected the first injected role-user item rather than the later submitted prompt, so the candidate stayed held and the committed tail never started. Real interactive typing exposed a second boundary bug: xterm forwards key chunks independently, while ownership only recognized one atomic prompt write. The seventh exact-head review also found that accepted inode evidence was discarded before the pathname-based physical tail opened.

Safety

Ownership remains positive proof and fails closed under same-CWD ambiguity, identical prompts, copied resume lineage, stale/unknown-age generations, inode replacement, truncated prefixes, unsupported key mappings, and callback failure. Process-global state stores HMAC evidence rather than raw prompts, CWDs, provider IDs, roots, or retained inactive paths.

Verification

  • red-first recorded/system corpus for every independent review finding
  • 92/92 tests, contract, TypeScript, build, packed-artifact verification, and accepted/latest upstream check at Codex 0.149.1
  • downstream parser check 94/94, live-probe typecheck, Agent Code typecheck, and focused readiness 9/9
  • real Codex 0.149.1: typed fresh turn committed 12 entries, exact prepared resume committed 21, and provider-backed Tab queue committed 29; exact prompt/response evidence and zero rollout errors in all three
  • backward-compatibility live sequence against repository Codex 0.144.4: 14/23/32 entries and zero rollout errors
  • exact-head GitHub package matrix and eighth independent review are required before merge

Tracks Juliusolsson05/agent-code#632 and is pinned by Agent Code PR #634.

@Juliusolsson05
Juliusolsson05 force-pushed the fix/ordered-rollout-prompt-evidence branch from 5cad5fd to 434d553 Compare August 26, 2026 16:55
@Juliusolsson05
Juliusolsson05 merged commit d57d0c6 into main Aug 26, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant