openai / openai/codex

Linux app: Chat-mode Voice is blocked by Codex usage limit

Open
#40,792 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app bug rate-limits
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

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

26.820.60940

What subscription do you have?

ChatGPT Plus

What platform is your computer?

Linux Mint 22.3 Cinnamon (X11), 64-bit

What issue are you seeing?

I am using the official Linux ChatGPT desktop app.

I started a conversation in Chat mode (not Work/Codex). From the Chat screen, I clicked the Voice button. Voice failed to start and showed this message:

"Voice chat couldn't start"

"You've hit your usage limit. Upgrade to Pro (https://chatgpt.com/explore/pro), visit https://chatgpt.com/codex/settings/usage to purchase more credits or try again at 3:56 AM."

This appears to gate regular Chat Voice behind the Codex / Work usage limit, even though I am in Chat mode, not Work.

Expected behavior:
Voice in Chat mode should use regular Chat/Voice limits and should not depend on Codex usage / credits.

Actual behavior:
Voice in Chat mode is blocked and directs me to the Codex usage/credits page.

I also submitted in-app feedback.

Feedback ID:
no-active-thread-01a03c51-cd67-7700-be12-cb097ee2fc45

Environment:

  • Official ChatGPT Linux desktop app
  • Linux Mint 22.3 Cinnamon
  • X11 session
  • 64-bit

I can attach screenshots showing:

  1. Chat mode with the Voice button visible
  2. The Voice error mentioning the Codex usage limit
  3. The feedback-submitted confirmation
What steps can reproduce the bug?

Feedback ID: no-active-thread-01a03c55-e618-7b80-8725-e0ff7157cbb7

What is the expected behavior?

Steps to reproduce:

  1. Open the official ChatGPT Linux desktop app.
  2. Select Chat mode, not Work.
  3. Have the Codex/Work usage allowance exhausted.
  4. Start a regular Chat conversation.
  5. Click the Voice button.
  6. Voice fails to start and says the usage limit has been reached.
  7. The error directs me to the Codex usage/credits page even though Chat mode is selected.

Expected behavior:

Voice started from regular Chat mode should use the normal Chat/Voice entitlement and should not be blocked by the Codex/Work usage allowance.

If Chat Voice and Codex/Work Voice intentionally share the same usage allowance in the Linux app, the UI should clearly indicate that before Voice is started rather than presenting it as ordinary Chat Voice.

Additional information

The Chat/Work selector clearly shows Chat selected when this occurs.

The error specifically directs me to the Codex usage/credits page even though I am not using Work mode.

I have attached a combined screenshot showing:

  1. Chat mode selected with the Voice button available.
  2. The Voice failure referencing the Codex usage limit.
  3. Confirmation that in-app feedback was submitted.

This is particularly confusing because the Chat and Work modes are presented as separate modes in the application.

Image

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the failure in the official Linux desktop app with Chat selected and the Codex allowance exhausted. Inspect the Chat/Work selector, Voice button, and usage-limit error routing; done means Chat Voice no longer depends on the Codex allowance, or the UI clearly identifies a shared allowance.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux
Domain
desktop
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.