Bug Report: Repeated “Stream disconnected before completion” rate-limit error as a subscription user

What version of the Codex App are you using (From “About Codex” dialog)?

Version 26.803.81509

What subscription do you have?

Pro 5x

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

I am repeatedly encountering the following error while using gpt-daybreak-blue-latest:

stream disconnected before completion: Rate limit reached for gpt-daybreak-blue-latest (for limit gpt-5.6-sol) in organization org-BOvpEHVcDPTe8h4lZnwMO5Ly on tokens per min (TPM): Limit 40000000, Used 40000000, Requested 24866. Please try again in 37ms.

I am a ChatGPT subscription user and I do not have or manage the organization referenced in this error (org-BOvpEHVcDPTe8h4lZnwMO5Ly). I am also not intentionally making requests through my own API organization.

This issue occurs repeatedly and causes active responses to stop before completion.

Expected behavior

Responses should complete normally under my ChatGPT subscription limits. Internal infrastructure or organization-level rate limits should not cause the response stream to disconnect unexpectedly.

Actual behavior

The response is interrupted with:

stream disconnected before completion

The accompanying error references an organization that does not belong to me and reports that the full 40,000,000 TPM limit has already been consumed.

Additional details
Model: gpt-daybreak-blue-latest
Rate-limit bucket shown: gpt-5.6-sol
TPM limit: 40,000,000
TPM used: 40,000,000
Requested: 24,866
Retry-after shown: approximately 37ms
Organization shown in the error: org-BOvpEHVcDPTe8h4lZnwMO5Ly
Account type: ChatGPT subscription user, not an API organization owner

Since the organization shown in the error is not mine, this may indicate an issue with internal rate-limit routing, accounting, or error handling for subscription users.

Could you please investigate why this internal organization-level rate limit is being exposed to me and why it is repeatedly terminating my generations?

What steps can reproduce the bug?

Feedback ID: 019ff15c-903f-7e40-bcf5-e80be6ab7f89

What is the expected behavior?

The model should finish generating the response normally without the stream disconnecting.

Additional information

_No response_