restore-explicit-codex

Restore explicit Codex executor; Claude optional second

Metadata

Statusdone
Assignedagent-865
Agent identity02e879681e52e0a384106169be043416c4d946e850ab26b2269c57681b52a6e7
Modelpi:openai-codex:gpt-5.6-sol
Created2026-07-26T07:57:30.291577418+00:00
Started2026-07-26T09:40:59.603388671+00:00
Completed2026-07-26T10:11:24.480592088+00:00
Tokens36178415 in / 37998 out

Description

Objective

Restore the native Codex CLI as an explicit first-class WG executor. Codex is the mandatory priority. Restoring Claude CLI is secondary and may be completed in the same change only when it does not delay or weaken Codex restoration.

Codex-first requirements

  • Re-enable explicit handler-first codex:<model> dispatch through the existing native Codex adapter for workers/tasks. Restore supported chat routing if the existing Codex chat bridge is production-safe; otherwise keep Pi chat as default and create a precise follow-up.
  • Add/restore a selectable direct-Codex profile and per-task override. Do not confuse native codex:* execution with pi:openai-codex:*; both must be rendered distinctly.
  • Keep Pi as the recommended default and preserve the current pi-codex profile.
  • Never introduce implicit cross-executor fallback. Explicit Codex failure stays a Codex failure unless the user explicitly configured a same-system fallback.
  • Codex CLI owns authentication and accepts explicit native model IDs as opaque input. Do not revive WG-owned model catalogs or endpoint/auth ownership.
  • Restore exact execution identity/provenance, stream translation, usage accounting, retry, evaluation, and session behavior. Remove contradictory surfaces that advertise Codex while central validation refuses it.

Claude secondary

  • Re-enable explicit claude:<model> through the existing adapter only if it can land without delaying Codex. Otherwise create a separate Claude follow-up; Codex completion must not wait on it.

Validation

  • Failing regression first proves explicit codex:* is currently rejected despite the existing adapter.
  • Explicit Codex worker dispatch reaches the native Codex CLI adapter, not Pi.
  • Direct-Codex profile/task selection works and displays executor/model identity unambiguously.
  • Pi remains the default and pi:openai-codex:* behavior is unchanged.
  • No implicit fallback crosses Pi/Codex/Claude execution systems.
  • Fake-Codex integration tests cover invocation, stream translation, usage/provenance, and failure propagation without credentials.
  • Codex chat is tested live or explicitly deferred with a follow-up task.
  • cargo fmt --check, cargo clippy, focused tests, and a permanent smoke scenario pass.

Depends on

Required by

Messages 3 messages (3 unread)

  1. #1user2026-07-26T08:15:39.126675947+00:00read
    Codex is the mandatory deliverable. Keep Claude secondary and defer it if necessary. Evaluation/FLIP remain disabled during recovery; do not re-enable them. Land and install direct Codex support, validate with fake/direct adapter tests, then report before changing runtime profile.
  2. #2restore-explicit-codex2026-07-26T08:19:55.418741605+00:00read
    Acknowledged — I will land Codex workers/tasks only, keep evaluation/FLIP disabled, defer Codex chat and Claude to follow-ups, install the rebuilt binary, and report before any runtime-profile change. I will not change the active runtime profile.
  3. #3restore-explicit-codex2026-07-26T09:58:58.502529417+00:00read
    Codex worker restoration is committed/pushed/installed and the installed-binary fake-Codex smoke passes. I did not change the active runtime profile; it remains Pi Codex. Chat, Claude, evaluation, and FLIP remain deferred/disabled as requested.

Log