restore-explicit-codex-chat — WorksGood live mirror

Metadata

Status	done
Assigned	`agent-874`
Agent identity	`02e879681e52e0a384106169be043416c4d946e850ab26b2269c57681b52a6e7`
Model	`pi:openai-codex:gpt-5.6-sol`
Created	2026-07-26T08:19:43.481131405+00:00
Started	2026-07-26T10:50:34.660349089+00:00
Completed	2026-07-26T11:21:06.807744367+00:00
Tokens	18555637 in / 27298 out

Description

Audit and restore codex:<model> for live chat/TUI routing through the existing codex-handler. Verify session resume, failure visibility, and no Pi crossover. Implement directly — do not decompose further.

Validation

Fake-Codex multi-turn terminal/TUI human-flow test covers first turn and native Codex resume
Explicit Codex failure remains visible and never invokes Pi
Permanent owned smoke scenario passes
cargo fmt --check, cargo clippy, and focused tests pass

## Description
Audit and restore `codex:<model>` for live chat/TUI routing through the existing codex-handler. Verify session resume, failure visibility, and no Pi crossover. Implement directly — do not decompose further.

## Validation
- [ ] Fake-Codex multi-turn terminal/TUI human-flow test covers first turn and native Codex resume
- [ ] Explicit Codex failure remains visible and never invokes Pi
- [ ] Permanent owned smoke scenario passes
- [ ] cargo fmt --check, cargo clippy, and focused tests pass

Depends on

Required by

✉ Messages 3 messages (3 unread)

#1add-atomic-clear2026-07-26T10:14:38.379161665+00:00read

Heads-up from add-atomic-clear: I must make small, surgical additions to src/cli.rs and src/main.rs for . Your Codex chat task may also touch CLI routing; please avoid/coordinate these Edit match/fields. I will not modify chat/Codex paths.

#2add-atomic-clear2026-07-26T10:14:45.708267989+00:00read

Correction: I must make small, surgical additions to src/cli.rs and src/main.rs for the new wg edit clear-route-pin flag. Please avoid/coordinate the Edit match/fields; I will not modify chat/Codex paths.

#3restore-explicit-codex-chat2026-07-26T10:50:48.592015950+00:00read

Acknowledged add-atomic-clear coordination notes — I will keep any cli.rs/main.rs changes surgical and Codex-chat-specific; their clear-route-pin work is now committed upstream.

Log

2026-07-26T08:19:43.469683485+00:00 Task paused
2026-07-26T08:19:43.552774980+00:00 Task published
2026-07-26T10:12:02.919831033+00:00 Spawn failed (attempt 1/5): build-heavy admission budget full (1/1). exec_mode=default, executor=pi
2026-07-26T10:12:03.605731903+00:00 Spawn failed (attempt 2/5): build-heavy admission budget full (1/1). exec_mode=default, executor=pi
2026-07-26T10:12:08.178814373+00:00 Spawn failed (attempt 3/5): build-heavy admission budget full (1/1). exec_mode=default, executor=pi
2026-07-26T10:12:13.186820699+00:00 Spawn failed (attempt 4/5): build-heavy admission budget full (1/1). exec_mode=default, executor=pi
2026-07-26T10:12:14.707826432+00:00 Spawn failed (attempt 5/5): build-heavy admission budget full (1/1). exec_mode=default, executor=pi
2026-07-26T10:12:14.707826432+00:00 Circuit breaker tripped: spawn failed 5 times. Last error: build-heavy admission budget full (1/1). exec_mode=default, executor=pi. Task marked incomplete for evaluator review.
2026-07-26T10:14:31.974226811+00:00 Retry route pinned at command time: profile=pi-codex generation=b3:c3378a663ed5ba39c43dd9ce64c5c84104f997323e3e2e6448f7d30d551674ea selected_at=2026-07-26T09:40:46.099962708+00:00 executor=pi model=pi:openai-codex:gpt-5.6-sol reasoning=high (stale task route/profile/session selection cleared)
2026-07-26T10:14:31.974239001+00:00 Task reset for retry from incomplete (attempt #1) — reason: Retry after build-heavy admission was incorrectly charged as five spawn failures; wait for the active build slot owner to finish.
2026-07-26T10:14:31.974285173+00:00 Minted evaluation pipeline evalp-2ddfb0ca282174f5834af470 for source attempt 2 (resume-in-place retry)
2026-07-26T10:50:34.742193917+00:00 Spawned by coordinator --executor pi --model openai-codex:gpt-5.6-sol --isolation required-worktree
2026-07-26T10:50:48.653628421+00:00 Starting direct implementation: auditing live chat/TUI routing, codex-handler resume, failure visibility, and Pi crossover. FANOUT_DECISION: stay inline — routing and its human-flow smoke are tightly coupled.
2026-07-26T11:11:20.526187085+00:00 Implemented explicit Codex chat routing: graph-only explicit creation no longer trips Pi-plane validation; canonical chat-N receives the coordinator contract; thread ID persists in UUID chat storage; TUI uses native inbox/outbox composer with daemon codex-handler (no direct Codex PTY). Added fake-Codex first-turn/restart-resume/exit-42/no-Pi human-flow smoke; installed-binary scenario passes.
2026-07-26T11:19:22.123093772+00:00 Committed: 3ce321da — pushed to remote
2026-07-26T11:20:51.836119932+00:00 Validated task criteria: installed-binary explicit_codex_chat_resume passes real tmux/TUI first turn, daemon restart, terminal native resume, TUI exit-42 visibility, canonical thread marker, and no Pi crossover; existing explicit_codex_worker + updated chat routing smoke pass.
2026-07-26T11:20:51.879814511+00:00 Validated: cargo fmt --check, cargo build, plain cargo clippy, focused Codex/chat/quickstart/execution-selection tests pass. Full cargo test reached 2989 passes; 7 pre-existing parallel profile::named HOME/lock race failures, and the first failing test passes alone.
2026-07-26T11:21:06.807750337+00:00 Task marked as done