Files
dev/patches
zeekayandHanzo Dev eee9d628b3 fix: the CLI stops naming the engine it was built from
Four surfaces still printed the upstream product. Found by running every
subcommand and reading the output rather than by grepping the sources, which
is why they survived the earlier sweep: three live in help text that only
clap assembles, and one is a JSON key.

  --profile        $CODEX_HOME/<name>.config.toml
  --ignore-user-config  $CODEX_HOME/config.toml
  doctor           "rerun codex doctor", "CODEX_HOME was resolved"
  doctor --json    "codexVersion"
  sandbox          the sandbox-state capability name

$CODEX_HOME was not only off-brand, it was wrong: initialize reads DEV_HOME and
writes CODEX_HOME, so a reader who followed the help and set CODEX_HOME had it
overwritten. The name that is ours is also the one that works.

doctor --json is a machine surface, so its key is a contract; both report
shapes carry it and both are renamed. The sandbox capability is a wire
identifier and keeps its value — only the sentence describing it changes.

Co-authored-by: Hanzo Dev <[email protected]>
2026-09-08 00:29:36 -07:00
..