Port Every Code identity and config boundary onto Codex base

[shiny-code-bot]

Finish Line

The Codex-base code binary has Every Code identity and config/state behavior at the product boundary while preserving upstream-compatible app-server/session internals.

Current Status

State: First identity/config boundary slice landed; copied Desktop validation exposed remaining config/version identity gaps.

Landed:

• PR feat: replace Rust substrate with Codex base #390 made the Codex-base workspace build the primary code binary while preserving the foundation home policy: CODE_HOME > CODEX_HOME > ~/.code.
• PR feat: replace Rust substrate with Codex base #390 validated CODE_HOME precedence and ~/.code default with cargo test -p codex-utils-home-dir --locked.
• PR feat: align CLI identity with Every Code #391 aligned the first user-facing CLI layer with Every Code and the code command: top-level help, login examples, MCP/plugin/update/sandbox/apply copy, code exec usage, resume hints, shared config override help, and root package scripts.
• PR feat: align CLI identity with Every Code #391 kept Codex Desktop and Codex Cloud references where they refer to upstream products, and kept internal codex-* crate/package names plus CODEX_* compatibility names where externally meaningful.

Validation:

• ./build-fast.sh passed for PR feat: replace Rust substrate with Codex base #390 and PR feat: align CLI identity with Every Code #391.
• Help spot checks passed for code --help, code exec --help, code mcp add --help, code plugin marketplace --help, and code app-server --help.
• PR feat: align CLI identity with Every Code #391 had two scoped review-agent passes; both review findings were fixed before merge.
• GitHub blob-size policy passed.

Latest #387 findings relevant to #385:

• In the copied Desktop bundle, the embedded current Codex-base Every Code binary still reports codex-cli 0.0.0 for --version; release/version identity remains incomplete.
• Normal dogfood ~/.code/config.toml blocked Desktop startup because the Codex-base parser rejected existing Every Code config shapes, notably tui.alternate_screen = true and another parse error near line 210.
• Relaunching the copied Desktop app with a clean temporary CODE_HOME removed those config/read failures and proved the app-server can initialize, so the blocker is config compatibility/migration, not basic process launch.

Remaining:

• code --version, completion generation, update/release output, and deeper TUI/config/runtime copy still need a deliberate identity sweep as later slices touch those areas.
• Every Code config compatibility needs a focused migration/alias slice so existing dogfood ~/.code/config.toml does not break Codex-base app-server startup.
• Release/build/package metadata beyond the root package scripts should be reviewed with the release workflow slice, not mass-renamed.

Next action:

• Keep Port Every Code identity and config boundary onto Codex base #385 open for the version identity and config compatibility follow-up.
• Under Validate Codex-base Every Code in copied Codex Desktop app #387/Inventory and port Every Code features onto Codex base #386, first implement the narrow Desktop startup app-server compatibility slice so clean-home Desktop validation can proceed toward real chat/session tests.

Acceptance Criteria

• code --version, top-level help, completion generation, update/help text, and release-facing output use Every Code / code terminology where user-facing.
• CODE_HOME is primary, CODEX_HOME remains compatibility fallback, and no-env default is ~/.code.
• Config docs/schema/help text no longer incorrectly says ~/.codex for Every Code-only user-facing paths, while upstream compatibility names remain where externally required.
• build-fast.sh builds the primary code binary from the Codex-base workspace without hardcoding package-prefix assumptions.
• Unit tests cover CODE_HOME > CODEX_HOME > ~/.code resolution.
• ./build-fast.sh passes cleanly.

Relationships

• Parent: Combine Every Code with the Codex Desktop app #377
• Depends on Plan Codex-base substrate migration for Every Code #384 substrate decision.
• Informs Decide public command name before package distribution #187, Move release version ownership out of codex-cli/package.json #296, Use Every Code branding in release notes and release-facing output #297, Document compatibility surfaces kept outside release flow #299.

[shiny-code-bot]

Related #387 update from the Desktop startup compatibility slice:

Clean-home Desktop startup now gets past the prior app-server protocol/schema blockers. This narrows #385's remaining Desktop-facing scope: normal dogfood ~/.code/config.toml compatibility is still a real blocker for using existing Every Code homes, and the embedded binary still reports codex-cli 0.0.0 for --version.

So #385 should stay open for config migration/alias handling and release/version identity. The startup method compatibility itself is being handled separately on feat/desktop-startup-compat.