Skip to content

Honor server model defaults when starting fresh TUI threads - #50013

Merged
copyberry[bot] merged 1 commit into
mainfrom
copyberry/codex-internal-to-codex-oss/4e2661ba42322a80e2b769a55c62f61a576762b0
Oct 1, 2026
Merged

copyberry[bot] merged 1 commit into
mainfrom
copyberry/codex-internal-to-codex-oss/4e2661ba42322a80e2b769a55c62f61a576762b0

Conversation

@copyberry

@copyberry copyberry Bot commented Oct 1, 2026 •

Copy link
Copy Markdown

Honor server model defaults when starting fresh TUI threads

Why

Fresh TUI threads should use the app server's model settings unless the launch explicitly overrides them. Sending resolved configuration values in thread/start turns defaults into explicit overrides.

What changed

  • Track explicit launch choices for model, model_provider, and model_reasoning_effort, and omit unselected settings from the initial thread/start request.
  • Preserve accepted model migrations as explicit model and reasoning-effort choices.
  • Keep explicit profile launches on the existing resolved-configuration path.

Testing

Update startup request tests to cover omitted defaults, CLI model and provider overrides, repeated model overrides, reasoning-effort overrides, accepted migrations, and explicit profiles.

## Why

Fresh TUI threads should use the app server's model settings unless the launch explicitly overrides them. Sending resolved configuration values in `thread/start` turns defaults into explicit overrides.

## What changed

- Track explicit launch choices for `model`, `model_provider`, and `model_reasoning_effort`, and omit unselected settings from the initial `thread/start` request.
- Preserve accepted model migrations as explicit model and reasoning-effort choices.
- Keep explicit profile launches on the existing resolved-configuration path.

## Testing

Update startup request tests to cover omitted defaults, CLI model and provider overrides, repeated model overrides, reasoning-effort overrides, accepted migrations, and explicit profiles.

GitOrigin-RevId: 4e2661ba42322a80e2b769a55c62f61a576762b0
@copyberry
copyberry Bot force-pushed the copyberry/codex-internal-to-codex-oss/4e2661ba42322a80e2b769a55c62f61a576762b0 branch from aaa3df0 to b527ce4 Compare October 1, 2026 15:47
@copyberry
copyberry Bot merged commit b527ce4 into main Oct 1, 2026
1 check passed
@copyberry
copyberry Bot deleted the copyberry/codex-internal-to-codex-oss/4e2661ba42322a80e2b769a55c62f61a576762b0 branch October 1, 2026 15:47
@github-actions github-actions Bot locked and limited conversation to collaborators Oct 1, 2026
@qiaoronghua
qiaoronghua deployed to issue-triage October 1, 2026 15:48 — with GitHub Actions Active
@qiaoronghua
qiaoronghua deployed to issue-triage October 1, 2026 15:48 — with GitHub Actions Active
@qiaoronghua
qiaoronghua deployed to issue-triage October 1, 2026 15:48 — with GitHub Actions Active
@guangong8888
guangong8888 deployed to issue-triage October 1, 2026 15:54 — with GitHub Actions Active
@guangong8888
guangong8888 deployed to issue-triage October 1, 2026 15:54 — with GitHub Actions Active
@guangong8888
guangong8888 deployed to issue-triage October 1, 2026 15:54 — with GitHub Actions Active
@guangong8888
guangong8888 deployed to issue-triage October 1, 2026 15:56 — with GitHub Actions Active
@spomotive
spomotive deployed to issue-triage October 1, 2026 15:56 — with GitHub Actions Active
@spomotive
spomotive deployed to issue-triage October 1, 2026 15:56 — with GitHub Actions Active
@spomotive
spomotive deployed to issue-triage October 1, 2026 15:56 — with GitHub Actions Active

This branch was successfully deployed

1 active deployment
issue-triage — b527ce47 Deployed Oct 1, 2026 by spomotive via Identify potential duplicates (all issues) #50593
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants