Color code model / reasoning in App
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What variant of Codex are you using?
App
What feature would you like to see?
Use colors to make it clear which model is running in the app. This makes it easy to understand at a glance when more usage is going to be used by accident.
When flipping between many threads, it's often easy to have a different model or reasoning level, and a color would be a easy to notice way of highlighting this pain point.
The negative effects of the wrong choice are the obvious ones - excessive token usage for tasks that don't need it, and on the flip side worse results compared to what you needed for more difficult tasks.
For color blind people it's worth using some form of symbol in addition.
This makes the UX glancable, rather than requiring reading every single element.
Please consider using the thumbs up button rather than commenting. It's unlikely that this needs more details. Codex team prioritizes work by votes.
Additional information
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Begin in the App UI where threads expose the active model and reasoning level, and review how those controls are rendered. Done means the active choices are distinguishable at a glance with color plus a non-color symbol, including a color-blind-friendly treatment.
Written by the indexing model from the issue text.
Assessment
- Domain
- accessibility, design, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100