codex - 💡(How to fix) Fix Severe Performance Degradation and Excessive Token Consumption in Codex 5.5 (VS Code Extension) [2 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#19361Fetched 2026-04-25 06:10:50
View on GitHub
Comments
2
Participants
3
Timeline
8
Reactions
0
Timeline (top)
labeled ×4commented ×2subscribed ×1unlabeled ×1
RAW_BUFFERClick to expand / collapse

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:

  1. Performance Issues
  • Significant lag in response generation
  • Slower execution even for simple prompts
  • VS Code becomes less responsive during Codex operations
  1. 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
  1. Degraded Output Quality
  • Lower accuracy and reliability
  • More retries required
  • Increased need for manual correction
  1. Cross-Account Reproducibility
  • Same issue observed on two separate accounts (Plus + Go)
  • Indicates issue is not account-specific

What steps can reproduce the bug?

  1. Open VS Code with Codex extension (v5.5)
  2. Start working on a normal coding workflow (moderate tasks)
  3. Continue usage for a few hours
  4. Observe:
  • Gradual lag increase
  • Rapid token depletion
  • Decline in response quality

What is the expected behavior?

  1. Smooth and responsive performance
  2. Token consumption proportional to workload (similar to pre-5.5 behavior)
  3. Stable output quality
  4. 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

extent analysis

TL;DR

Downgrade to a previous version of the Codex VS Code Extension or wait for a patch release to address the regressions introduced in version 5.5.

Guidance

  • Verify that the issue is indeed caused by the Codex 5.5 update by checking if the problem persists when using a different version of the extension.
  • Monitor token consumption and performance metrics to better understand the impact of the regressions on your workflow.
  • Consider reaching out to the Codex support team to report the issue and request assistance with troubleshooting or a potential fix.
  • If possible, test the extension on a different platform or IDE to determine if the issue is specific to Windows or VS Code.

Example

No code snippet is provided as the issue is related to the extension's performance and behavior rather than a specific code implementation.

Notes

The issue seems to be specific to the Codex 5.5 update, and downgrading to a previous version may be the most straightforward workaround until a fix is released. However, this may not be a viable long-term solution, and users should continue to monitor the extension's updates and releases for a permanent fix.

Recommendation

Apply workaround: Downgrade to a previous version of the Codex VS Code Extension, as this is likely to mitigate the regressions introduced in version 5.5, allowing for smoother performance, more proportional token consumption, and better output quality.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING