Skip to content

Inventory and port Every Code features onto Codex base #386

@shiny-code-bot

Description

@shiny-code-bot

Finish Line

Every Code's distinctive features are inventoried and ported onto the Codex-base substrate in a deliberate order, with explicit keep/drop/defer decisions for each surface.

Current Status

State: Inventory landed, but the purpose is now required-overlay selection for a Codex CLI fork, not wholesale Every Code product restoration.

Decision update, 2026-06-06:

  • Every Code is moving into maintenance mode as a standalone product direction.
  • The active repo direction is Codex CLI fork compatibility first, then selected Every Code overlays.
  • A feature from the old Every Code workspace should be ported only if it is classified as required overlay, low-risk compatibility support, or explicitly validated product value.
  • Features can also be retired, deferred, or replaced with Codex-native behavior; absence from the new Codex-base workspace is not automatically a regression.

Current overlay candidates:

  • Preserve/additive unless a specific issue closes them out: code command UX, Every Code harness/runtime dogfooding, Code Bridge/browser control, multi-agent workflows, Auto Drive, GitHub automation, auto-review/planning, token/burn diagnostics, and local build/release workflows.
  • Compatibility-sensitive surfaces such as app-server/session/protocol/config/TUI should stay Codex-shaped unless an additive overlay is required and tested.
  • Remote-inbox backend and Discord presentation remain gated by Decide remote inbox and Discord UI for Codex-base session continuity #388; do not remove or re-port blindly before external-session discovery/resume/approval evidence exists.

Recent evidence:

Next action:

  • Reclassify the inventory table into: Codex compatibility, required Every Code overlay, deferred, retired, or replaced-by-Codex.
  • Use that classification to prevent both regression-by-omission and accidental resurrection of no-longer-needed Every Code product behavior.

Acceptance Criteria

  • Create a tracked inventory table of Every Code-only/heavily-extended features with source files/crates, owner domain, risk, and port status.
  • Decide must-port vs can-drop vs defer for each domain.
  • Port order starts with substrate-safe domains before high-conflict TUI/event-loop work.
  • Auto Drive/token diagnostics/auto-review are preserved or explicitly re-scoped with tests.
  • Browser/control and Code Bridge are preserved or explicitly re-scoped with tests.
  • Git/patch harness behavior is preserved or intentionally replaced with Codex-native equivalents.
  • Remote-inbox backend/session-continuity is preserved until Decide remote inbox and Discord UI for Codex-base session continuity #388 validates a replacement for GitHub/LaunchPlane-created sessions.
  • Discord-specific UI wording/presentation is only removed after Decide remote inbox and Discord UI for Codex-base session continuity #388 proves an alternate UI can discover, resume/continue, and handle approval/reply flow for externally-created sessions.
  • Each port slice has focused validation and ends with ./build-fast.sh passing.

Initial Port Domains

  • Auto Drive and token/burn diagnostics.
  • Auto Review and proof metrics.
  • Remote inbox and Discord surface decision.
  • Account/token accounting and auth/account switching.
  • TUI extensions and approval UX.
  • Protocol/app-server Every Code extensions.
  • Browser/control and Code Bridge.
  • Exec/sandboxing/git/patch harness.
  • Model providers, cloud tasks, observability, utilities.

Relationships

Metadata

Metadata

Assignees

No one assigned

    Labels

    planDurable planning issueplan:waitingPlan is waiting on non-issue evidence or decision

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions