Codex Performance issue after update to latest version - on Mac
Nobody has claimed this yet.
- 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.818.61809
What subscription do you have?
Plus
What platform is your computer?
MacBook Pro 26.5.2
What issue are you seeing?
Yes—I pulled the available statistics from your recent Codex task history.
Across 34 completed turns in 8 tasks:
- Median duration: 5m 15s
- Average: 11m 03s
- 75th percentile: 15m 01s
- 90th percentile: 30m 12s
- Maximum: 44m 21s
- 13 of 34 turns exceeded 10 minutes
- 6 of 34 exceeded 20 minutes
The strongest regression signal:
- Latest 10 turns: median 8m 58s
- Previous 10 turns: median 2m 41s
- That is approximately 3.3× slower by median
- Mean increased from 9m 20s to 11m 21s
Your last simple support question also took approximately 40 seconds.
What steps can reproduce the bug?
Yes—I pulled the available statistics from your recent Codex task history.
Across 34 completed turns in 8 tasks:
- Median duration: 5m 15s
- Average: 11m 03s
- 75th percentile: 15m 01s
- 90th percentile: 30m 12s
- Maximum: 44m 21s
- 13 of 34 turns exceeded 10 minutes
- 6 of 34 exceeded 20 minutes
The strongest regression signal:
- Latest 10 turns: median 8m 58s
- Previous 10 turns: median 2m 41s
- That is approximately 3.3× slower by median
- Mean increased from 9m 20s to 11m 21s
Your last simple support question also took approximately 40 seconds.
What is the expected behavior?
No response
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 report concerns Codex App version 26.818.61809 on a MacBook Pro 26.5.2 and includes timing statistics from 34 turns across 8 tasks. Start by investigating the reported post-update slowdown and determine whether the regression can be reproduced; completion requires a confirmed cause or reproducible performance comparison, since no expected behavior is specified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100