Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix VS Code extension repeatedly logs telemetry 403 errors for /ces/v1/rgstr and prompt is lagging [1 comments, 2 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#19371•Fetched 2026-04-25 06:10:33
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Author
duncanmclduncanmcl
Participants
duncanmclduncanmclgithub-actions[bot]github-actions[bot]
Timeline (top)
labeled ×4commented ×1

Error Message

[error] Error fetching httpStatus=403 statusText=Forbidden url=https://chatgpt.com/ces/v1/rgstr?<redacted>

Root Cause

The prompt input may also be stalling because the extension keeps doing background work after failed requests.

RAW_BUFFERClick to expand / collapse

What version of the IDE extension are you using?

2.1.119

What subscription do you have?

Pro

Which IDE are you using?

VS Code

What platform is your computer?

Linux 6.8.0-107-generic x86_64 x86_64

What issue are you seeing?

The Codex VS Code extension becomes laggy when typing prompts, while the Codex log rapidly fills with repeated warnings and telemetry errors.

The main warning is:

[warning] [IpcClient] Received broadcast but no handler is configured method=thread-stream-state-changed In my current log, this warning reached 7974 entries.

I also see repeated telemetry/analytics 403 errors:

text

[error] Error fetching httpStatus=403 statusText=Forbidden url=https://chatgpt.com/ces/v1/rgstr?<redacted> I am not sure whether the 403 /ces/v1/rgstr telemetry errors directly cause the Received broadcast but no handler is configured warnings. They may be separate bugs. However, they happen during the same laggy period, while the Codex extension/app-server has high CPU and the log grows quickly.

What steps can reproduce the bug?

Type prompts into the Codex prompt box.

What is the expected behavior?

  • Internal broadcast messages should have a handler, or should be ignored quietly if no handler is needed.
  • The extension should not log thousands of repeated Received broadcast but no handler is configured warnings.
  • Telemetry 403 Forbidden failures should not be repeatedly logged as user-visible errors.
  • Failed telemetry requests should back off or be disabled for the session.
  • These background warnings/errors should not cause high CPU usage or prompt input lag.

Additional information

The prompt input may also be stalling because the extension keeps doing background work after failed requests.

I am not sure if the lag is caused directly by the repeated 403 /ces/v1/rgstr telemetry failures, but while the lag happens, the log keeps growing with telemetry 403 errors and many broadcast warnings:

Also getting this warning:

[warning] [IpcClient] Received broadcast but no handler is configured method=thread-stream-state-changed

extent analysis

TL;DR

The issue can be mitigated by disabling telemetry or configuring the Codex extension to handle broadcast messages, which may reduce the high CPU usage and lag caused by repeated warnings and errors.

Guidance

  • Investigate the Received broadcast but no handler is configured warning and determine if a handler is needed for the thread-stream-state-changed method. If not, configure the extension to ignore this message.
  • Check if the telemetry errors are causing the lag and consider disabling telemetry temporarily to see if it improves performance.
  • Review the extension's configuration and code to ensure that failed requests are properly handled and do not cause excessive logging or CPU usage.
  • Consider implementing a backoff strategy for failed telemetry requests to prevent repeated errors.

Example

No code snippet is provided as the issue does not contain sufficient information about the extension's code or configuration.

Notes

The relationship between the telemetry errors and the broadcast warnings is unclear, and further investigation is needed to determine the root cause of the issue. Disabling telemetry or configuring the extension to handle broadcast messages may not completely resolve the issue but can help mitigate the symptoms.

Recommendation

Apply workaround: Disable telemetry temporarily to see if it improves performance, as it may be contributing to the high CPU usage and lag.

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…
#api#authentication issue#prompt issue#agent setup#task chaining

Still need to ship something?

×6

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

Back to top recommendations

TRENDING