What version of the IDE extension are you using?
Codex VS Code Extension (Version: 5.5)
What subscription do you have?
Tested on both Plus and Go subscriptions (issue reproducible on both)
Which IDE are you using?
VS Code
What platform is your computer?
Microsoft Windows NT 10.0.26100.0 x64
What issue are you seeing?
After updating to Codex 5.5 in the VS Code extension, multiple major regressions appeared:
- Performance Issues
- Significant lag in response generation
- Slower execution even for simple prompts
- VS Code becomes less responsive during Codex operations
- Extremely High Token Consumption
- Tokens are exhausted within 3–4 hours of normal usage
- Previously, even 8–10 hours of heavy usage did not exhaust limits
- Consumption rate feels disproportionately high relative to task complexity
- Degraded Output Quality
- Lower accuracy and reliability
- More retries required
- Increased need for manual correction
- Cross-Account Reproducibility
- Same issue observed on two separate accounts (Plus + Go)
- Indicates issue is not account-specific
What steps can reproduce the bug?
- Open VS Code with Codex extension (v5.5)
- Start working on a normal coding workflow (moderate tasks)
- Continue usage for a few hours
- Observe:
- Gradual lag increase
- Rapid token depletion
- Decline in response quality
What is the expected behavior?
- Smooth and responsive performance
- Token consumption proportional to workload (similar to pre-5.5 behavior)
- Stable output quality
- No major variance across accounts
Additional information
- Issue started immediately after Codex 5.5 release
- Not project-specific (occurs across different workflows)
- Internet and system performance are stable
What version of the IDE extension are you using?
Codex VS Code Extension (Version: 5.5)
What subscription do you have?
Tested on both Plus and Go subscriptions (issue reproducible on both)
Which IDE are you using?
VS Code
What platform is your computer?
Microsoft Windows NT 10.0.26100.0 x64
What issue are you seeing?
After updating to Codex 5.5 in the VS Code extension, multiple major regressions appeared:
What steps can reproduce the bug?
What is the expected behavior?
Additional information