jif-oai e0e304b123 cli: remove legacy profile v1 plumbing (#23886) ...

## Why

[#23883](https://github.com/openai/codex/pull/23883) moved the
user-facing `--profile` flag onto profile v2. The shared CLI option
layer still carried the old `config_profile` slot and several CLI
entrypoints still copied that value into legacy config overrides.
Leaving that path around makes the CLI surface look like it still
selects legacy `[profiles.*]` state even though `--profile` now means
`$CODEX_HOME/<name>.config.toml`.

## What

- Remove the legacy `config_profile` field and merge/copy path from
[`SharedCliOptions`](https://github.com/openai/codex/blob/95baaf72920c8db22097df8d15a0bb76c84528b6/codex-rs/utils/cli/src/shared_options.rs#L8-L177).
- Stop forwarding profile-v1 overrides from CLI, exec, TUI, doctor,
debug, feature, and exec-server paths; runtime profile selection remains
on `config_profile_v2` through
[`loader_overrides_for_profile`](https://github.com/openai/codex/blob/95baaf72920c8db22097df8d15a0bb76c84528b6/codex-rs/cli/src/main.rs#L1606-L1619).
- Resolve local OSS provider selection from the base config in exec and
TUI now that the legacy profile argument is gone.

## Testing

- Not run (cleanup-only follow-up to #23883).

e0e304b123 · 2026-05-21 17:21:37 +02:00

History

..

src

cli: remove legacy profile v1 plumbing (#23886)

2026-05-21 17:21:37 +02:00

tests

[codex] Add plugin id to MCP tool call items (#23737)

2026-05-20 17:02:10 -07:00

BUILD.bazel

[codex] Shard exec Bazel integration test (#19862)

2026-04-27 21:22:53 +00:00

Cargo.toml

permissions: support workspace roots in profiles (#22610)

2026-05-14 18:25:23 -07:00