Summary
Desktop realtime voice repeatedly stops with You have reached your usage limit. while a contemporaneous account limit query reports 27% of the weekly Codex allowance remaining and ordinaryUsageAllowed: true. Text interaction and tool calls continue to work.
Environment
- Windows, Microsoft Store/MSIX package OpenAI.Codex
- Installed package version: 26.924.6891.0
- ChatGPT Pro
- Voice opened in an existing Codex task
- Observed on September 29, 2026
Steps observed
- Start realtime voice in an existing Codex task.
- Receive a spoken warning that Codex usage is nearly exhausted.
- Voice subsequently terminates with a usage-limit error.
- Read account limits immediately afterward: weekly usage is 73% used / 27% remaining, ordinary usage is allowed.
- Restart voice: the same failure occurs again.
Evidence (sanitized)
Desktop log contains both events:
2026-09-29T18:20:40.527Z error [electron-message-handler] Realtime voice session failed message="You have reached your usage limit."
2026-09-29T18:22:09.392Z error [electron-message-handler] Realtime voice session failed message="You have reached your usage limit."
Account query at approximately 18:21:32 UTC and subsequent queries:
{
"ordinaryUsageAllowed": true,
"limitId": "codex",
"primary": {"usedPercent": 73, "windowDurationMins": 10080},
"secondary": null,
"credits": {"hasCredits": false, "unlimited": false, "balance": "0"},
"spendControlReached": false,
"planType": "pro",
"rateLimitReachedType": null
}Zero additional credits are included as a potentially relevant observation, not a proven cause. No separate voice allowance or reset time is exposed by this query.
Expected behavior
If included usage remains available to voice, the session should continue. If a separate voice restriction applies, show the actual exhausted allowance, its reset time, and explain why it differs from the reported Codex allowance.
The current pricing documentation says desktop voice and tasks share the plan's usage limits:
https://learn.chatgpt.com/docs/pricing#how-much-does-voice-cost
Related reports / distinction
Please investigate the voice quota/entitlement check and its consistency with account/rateLimits/read. The precise backend cause is unknown. No credentials, account identifiers, conversation contents, or full logs are included.
Summary
Desktop realtime voice repeatedly stops with
You have reached your usage limit.while a contemporaneous account limit query reports 27% of the weekly Codex allowance remaining andordinaryUsageAllowed: true. Text interaction and tool calls continue to work.Environment
Steps observed
Evidence (sanitized)
Desktop log contains both events:
Account query at approximately 18:21:32 UTC and subsequent queries:
{ "ordinaryUsageAllowed": true, "limitId": "codex", "primary": {"usedPercent": 73, "windowDurationMins": 10080}, "secondary": null, "credits": {"hasCredits": false, "unlimited": false, "balance": "0"}, "spendControlReached": false, "planType": "pro", "rateLimitReachedType": null }Zero additional credits are included as a potentially relevant observation, not a proven cause. No separate voice allowance or reset time is exposed by this query.
Expected behavior
If included usage remains available to voice, the session should continue. If a separate voice restriction applies, show the actual exhausted allowance, its reset time, and explain why it differs from the reported Codex allowance.
The current pricing documentation says desktop voice and tasks share the plan's usage limits:
https://learn.chatgpt.com/docs/pricing#how-much-does-voice-cost
Related reports / distinction
Please investigate the voice quota/entitlement check and its consistency with account/rateLimits/read. The precise backend cause is unknown. No credentials, account identifiers, conversation contents, or full logs are included.