Codex Lab MVP dogfood plan #28

Finish Line

Codex Lab reaches MVP when one provenance-verified current binary supports the three workflows required for real product dogfood:

1. Automatic Validation runs after relevant code changes, emits bounded structured results, and permits at most one controlled correction cycle. The MVP preserves parser and project-command validation and includes at least one automatically selected changed-file executable provider.
2. Third-party agents launch through the native agent system with workspace/session provenance, bounded status and output, completion/failure/timeout/cancellation cleanup, and terminal-state recovery proven from the current binary.
3. Automatic Background Review runs detached after completed code-changing turns, records durable current findings, avoids duplicate/stale noise, and remains distinct from manual Review and Approval Review/Guardian.

History/resume, auth, provenance, TUI status, and upstream substrate work are MVP requirements only where they are necessary to run these workflows safely. Once the three workflows pass deterministic and bounded current-binary smoke gates, Codex Lab begins real dogfood with Every Code retained as rollback. Broad upstream parity, architecture thinning, polish, and the permanent default-route soak are post-MVP unless a dogfood failure promotes a specific item.

Current Status

The admitted upstream recovery #928 is complete through PR #934 at d83017f. Frozen qualification took 7h48m31s and landing took 9h02m15s from the original unpaused T0. The qualified source passed 20,313 workspace tests, focused regressions, scoped Clippy, CI/artifact checks and actual Opus/Gemini reviews; postmerge CI passed 15 jobs. IDE freshness remains explicitly UNKNOWN and a passing leaky-test observation is preserved. This establishes one recovery's feasibility, not #634 ordinary-refresh automation or comparative speedup.

Direction remains tooling/convergence, lab.8 release preparation and protected #787 Background Review delivery, then broader thinning only when justified by a measured need. #929's additional nonpublishing release gates found one stale test annotation; reviewed one-line PR #937 repairs it while the remaining rehearsal jobs finish. Repaired main needs a fresh successful rehearsal, exact artifact/signature/symbol verification and Opus/Gemini final release review before owner publication approval. No lab.8 artifact, publication or installed acceptance is claimed yet.

#787 is prepared independently in draft PR #936 at 0657684, with 61 focused tests, 4,924 codex-core tests and scoped all-target Clippy passing, plus actual Opus/Gemini source approval. A documented remote-mock retry remains unexplained. Its complete-workspace approval is pending; CI and installed dogfood remain open. This product slice is not a lab.8 publication dependency.

The affected issue graph is being reconciled to these observations. #926 was absorbed into existing plans and closed; #908 was reconciled through #933. #634 remains open for ordinary-refresh/automation proof and #230 owns cadence/lag: canonical upstream was 54 commits beyond the frozen target at 06:20Z, with no new target admitted. Release publication, installation, GUI, native-provider acceptance and code-route activation retain their separate gates. Live evidence and remaining work are owned by #928, #929 and #787.

This closed recovery anchor stays closed; the linked live issues own execution.

Source Material

Use restored cbusillo/code issues and commits as historical source material, not as automatic carry-forward status. Important restored planning issues include:

• Stabilize Every Code parity on Codex CLI fork baseline code#397 - Stabilize Every Code parity on Codex CLI fork baseline.
• Dogfood Parity 1: Daily Driver Baseline code#404 - Dogfood Parity 1: Daily Driver Baseline.
• Inventory and port Every Code features onto Codex base code#386 - Inventory and port Every Code features onto Codex base.
• Validate Codex-base Every Code in copied Codex Desktop app code#387 - Validate Codex-base Every Code in copied Codex Desktop app.
• Decide remote inbox and Discord UI for Codex-base session continuity code#388 - Decide remote inbox and Discord UI for Codex-base session continuity.
• Map Auto Review proof metrics onto Codex review primitives code#400 - Auto Review proof metrics.
• Define Code Bridge and browser control parity boundary code#399 - Code Bridge/browser parity.
• Restore Auto Drive parity fixtures on Codex fork baseline code#398 - Auto Drive parity.
• Audit token and prompt-cache diagnostics parity code#401 - Token/prompt-cache diagnostics.
• Add context source ledger and prompt observability code#92 - Context source ledger and prompt observability.
• Plan Every Code token efficiency and local LLM sandboxing code#43 - Token efficiency and local LLM sandboxing.
• De-duplicate prompt and skill injection overhead code#46 - De-duplicate prompt and skill injection overhead.
• Sandbox local LLMs with LM Studio readiness support code#49 - LM Studio readiness.
• Define natural agent delegation policy code#212 - Natural agent delegation policy.

Recent restored commits worth mining include the Codex substrate migration, Codex Desktop startup compatibility, Every Code identity/config alignment, feature inventory, parity ledger, prompt-cache prefix preservation, auto-review proof metrics, auto-review lifecycle/store/ledger work, agent context file preloading, worktree decision gate hardening, and release/build runner fixes.

Base Platform Decision

Codex Lab remains the product base. Build on the Codex CLI/Desktop/app-server substrate because the hard-to-recreate value is Codex Desktop compatibility, Codex iOS/mobile control of Desktop, Codex subscription auth, upstream openai/codex compatibility, and continuity with the Every Code Codex-base port path.

opencode and other coding harnesses are reference implementations, not the base. Steal ideas when they improve Codex Lab without breaking Codex compatibility and can be validated through the exec harness or focused tests.

Guardrails

• Use fixtures/tests/concepts before broad implementation overlays where feasible.
• Treat missing Every Code behavior as unclassified until this plan or a child issue records Port, Rewrite, Covered, Defer, or Retire.
• Keep openai as fetch-only upstream.
• Avoid direct work on protected/default branches; use focused task branches and PRs for implementation.
• Every code-bearing port slice should include scoped validation evidence.
• The exec harness is mandatory for Codex Lab-specific regressions: skills prompt strength, cached-token stability, thread continuity, Desktop/app-server compatibility, and Every Code workflow expectations.
• Cache-sensitive scenarios should compare input tokens, cached input tokens, cache ratio, and normalized prompt-prefix stability against explicit baselines.

MVP Slices

1. Repo and runner recovery.

   • Verify cbusillo/codex-lab runners after repo move.
   • Keep cbusillo/code runner-free unless a future archival workflow explicitly needs one.

2. Planning source of truth.

   • Make this issue the durable parent plan.
   • Create focused child issues for independent MVP slices.
   • Realign repo AGENTS.md so future agents find this issue instead of relying on local plan files.

3. Exec harness hardening and regression gates.

   • Fix known automation findings: cleanup just argument forwarding and exec-harness workflow path triggers.
   • Add skills-cache-continuity as the first cache-sensitive scenario.
   • Add deterministic fake-Responses coverage first, then local-LLM dogfood and frontier release variants.

4. Skills and prompt-cache protection.

   • Protect against skills becoming less directive or being treated as optional advice.
   • Protect against prompt-stack churn reducing cached-token reuse.

5. Auto Review proof loop.

   • Restore actionable review evidence without broad-review noise.
   • Mine restored Every Code auto-review lifecycle/store/ledger commits and issues before implementation.

6. Agents and third-party agent orchestration.

   • Rebuild configurable agent roles, third-party agents, local LLM roles, and review/validation loops on Codex Lab primitives.

7. Codex Desktop/app-server compatibility.

   • Validate Codex Lab in Desktop and keep app-server behavior upstream-shaped unless an additive extension is explicitly validated.

8. Code Bridge/browser and remote-control workflows.

   • Preserve or replace Code Bridge/browser/control capability with clear Desktop/app-server boundaries.

9. Auto Drive.

   • Rebuild Auto Drive on validated Codex thread/session/worktree/token primitives rather than copying old implementation wholesale.

10. Local LLM dogfood.

    • Make LM Studio/OpenAI-compatible local endpoints first-class for bounded dogfood basics, then graduate roles only after repeated proof.

Opencode And Other References

opencode is the primary near-term reference for plugin/hooks ergonomics, named agents/subagents, LM Studio flow, provider/auth boundaries, permissions UX, run artifacts, GitHub automation presentation, prompt/context controls, and MCP/tool discovery.

Keep a lightweight watch on OpenHands, SWE-agent/mini-SWE-agent, Aider, Cline/Roo Code, Goose, and Continue for product architecture ideas. Separately, keep Terminal-Bench, promptfoo, Inspect AI, SWE-bench, Aider benchmarks, and BrowserGym/WebArena/OSWorld in mind for eval and grading ideas. These are references only.

Next Actions

1. Begin bounded opt-in Codex Lab dogfood from merged source 357b8e4ac06053968ba2a5232c4369bcec849458; keep Every Code available as the immediate rollback route.
2. Record concrete dogfood regressions as focused issues and promote only those defects into blocking work.
3. Continue Define Every Code-owned convergence contracts #126/Upstream sync and Codex Lab feature reclassification #229 upstream classification and synchronization without retroactively reopening the MVP unless a material workflow regression is found.
4. Use Cut over to converged Codex Lab baseline and primary harness #343 for paired quality evaluation, rollback/re-entry, multi-day soak, and the eventual permanent default-route decision.
5. Treat Adopt Background Review terminology across product surfaces #303, Sync TUI, Guardian, and CI substrate #308, Reduce managed approval friction in dogfood workflows #313, Surface structured rate-limit diagnostics for Claude CLI agents #315, and Add a lightweight structured LLM request side channel #319 as post-MVP terminology, presentation, friction, diagnostics, or observability work.

Relationships

• Completed MVP evidence: Preserve Background Review across same-turn commits #302 Automatic Background Review, Prove current-binary third-party-agent dogfood #312 current-binary third-party agents, and Restore Every Code auto-validation loop #284/Characterize Every Code validation provider contracts #309/Restore pluggable changed-file validation providers #310 Automatic Validation.
• Completed build/provenance foundation is recorded through Make dogfood build provenance visible #311 evidence and the exact merged candidate; Make dogfood build provenance visible #311 may continue broader diagnostics independently.
• Post-MVP upstream work: Define Every Code-owned convergence contracts #126 compatibility/adoption ledger and Upstream sync and Codex Lab feature reclassification #229/Sync Codex Lab with current openai/codex substrate #230 convergence.
• Post-MVP graduation: Cut over to converged Codex Lab baseline and primary harness #343 permanent harness cutover, paired result-quality evidence, rollback/re-entry, and soak.
• Post-MVP product polish: Adopt Background Review terminology across product surfaces #303 terminology, Sync TUI, Guardian, and CI substrate #308 TUI/CI integration, Reduce managed approval friction in dogfood workflows #313 approval friction, Surface structured rate-limit diagnostics for Claude CLI agents #315 agent rate-limit diagnostics, and Add a lightweight structured LLM request side channel #319 request observability.
• Design durable goals as the substrate for auto execution #121 durable goals and Expose a generic Work Pulse activity stream #298 Work Pulse are no longer blocked by MVP completion; their own prioritization and dependencies govern next work.
• Closed historical children remain evidence checkpoints, not active blockers.

Post-Cutover Roadmap

As of July 29, 2026, this closed issue remains the durable MVP evidence and historical recovery point. The active post-cutover roadmap is #498.

Current queue:

• Now: Publish and install first post-cutover Codex Lab prerelease #499 private signed post-cutover prerelease and supported installation.
• Next: Bound and compress local session rollout storage #490 bounded session-storage retention/compression.
• Waiting: Sync Codex Lab with current openai/codex substrate #230 steady-state upstream refreshes and Prove persistent Codex Lab engine behind official Mac and iOS clients #385 real-use controller reliability.
• Later: Surface per-account Codex reset credits and reset recommendation #383 account Limits UX, Adopt Background Review terminology across product surfaces #303 terminology clarity, and broader platform/architecture plans.

Future sessions should recover MVP intent here, then use #498 for current direction and sequencing.

Execution Recovery

Execution resumed with owner authorization on September 10. Follow #498 for the roadmap and #902 for the finite frozen-upstream catch-up; upstream target stays a62e98d18c6550e3bea152ed1b89d1e931dca961. Preserved integration reuse plus newer-main conflict resolution produced current source checkpoint 9a71ebdb32ce496dd2ad1b7463ca04a287958eff; 139 upstream conflicts remain, with complete residual/trust allocation recorded in #902. No completed convergence/build claim. Frozen main #903 at 49abf185 is integrated; exact reinspection found unchanged conflict/residual path sets. The complete implementation allocation is recorded in #902. #787 has a bounded first safety-slice design and retains protected harness priority.

Release publication/routing trackers #845 and #879 are now closed after evidence and stale-dependency reconciliation. Lab.6 remains published and installed at 914874727a60168626bc6d720c53cf35d88252cb, bundle 78. #844 records successful supported rollback to lab.5 and restore to lab.6 plus saved-thread continuity; #850 records installed Astra/Sol cache reuse and remaining wire/transport qualification gaps.

Native Gemini acceptance exposed provider CLI lookup failure from the installed supervisor PATH. #904 owns the focused fix in PR #905; source tests pass, IDE evidence is UNKNOWN/stale, Opus/Gemini final reviews and all ordinary CI/app checks passed; the normal merge/provisioning decision and explicit IDE-gap acceptance remain with the owner. No patched provisioning has been applied. #844 also retains GUI coordination with the running official Codex app. The code route stays Every Code; preserve rollback assets and all existing worktrees. Earlier planning-only language and publication waiting steps are historical, not current instructions.