openai / openai/codex

Profile “Most used reasoning” shows Max despite exclusively using Ultra

Open
#44,972 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app bug
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

What version of the Codex App are you using (From “About Codex” dialog)?

26.903.71938 (build 8576), verified from the installed app bundle.

What subscription do you have?

Pro

What platform is your computer?

macOS 26.6.2 (build 25G83), Apple Silicon / arm64.

What issue are you seeing?

In Profile → Activity insights, Most used reasoning displays Max · 49%.

I only use Ultra and never select Max, so this does not match my usage. My current local default also reads model_reasoning_effort = "ultra".

What steps can reproduce the bug?

Observed on my existing account:

  1. Use Codex with Ultra selected as the reasoning effort.
  2. Open Settings → Profile.
  3. Look at Activity insights → Most used reasoning.
  4. The displayed value is Max · 49%, despite exclusively selecting Ultra.

I have not tested reproduction on a fresh account.

What is the expected behavior?

The activity summary should reflect the selected reasoning tier, showing Ultra when that is the most-used level. If this statistic intentionally groups or normalizes Ultra into Max, the UI should explain that instead of presenting Max as the tier I selected.

Additional information

The reported label and percentage are transcribed from the profile screenshot. I have not established whether the mismatch comes from labeling, aggregation, or recording the reasoning effort.

Related: #30585 reports Ultra-to-max request normalization with a backend rejection. This report concerns the user-facing Profile statistic and does not establish an execution downgrade.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at Settings → Profile → Activity insights and trace how the Most used reasoning value is recorded, aggregated, and labeled. Compare the displayed Max value with the selected Ultra effort and add regression coverage; done when Ultra is shown for Ultra usage or any intentional grouping is clearly explained in the UI.

Written by the indexing model from the issue text.

Assessment

Tech stack
macos, rust
Domain
desktop, frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.