[Bug]: Subscription Sharing usage limit. #36857

Before submitting

• I searched existing issues and did not find a duplicate.
• I included enough detail to reproduce or investigate the problem.

Area

apps/web

Steps to reproduce

Hello T3 Code Support,

I'm experiencing a persistent Subscription Sharing usage limit error when using the Codex provider with my ChatGPT Plus account.

The issue has continued for more than 36 hours.

Details:

• T3 Code Codex provider: v0.166.0
• Authentication: Authenticated via ChatGPT
• Model: GPT-6.1 Sol (Medium)
• ChatGPT 5-hour usage remaining: 100%
• ChatGPT weekly usage remaining: 76%
• Both existing and newly created threads show "Limited"
• Error: "ChatGPT usage limit reached. Reset time unavailable; retry manually."

I have reauthenticated my ChatGPT account, but the issue persists.

Could you investigate whether there is a Subscription Sharing quota synchronization or authorization problem affecting my account?

Please advise how I can restore access without switching to paid API billing.

Thank you.

Expected behavior

When authenticated through my ChatGPT Plus account, T3 Code should allow me to use the Codex provider as long as my applicable usage limits have not been reached.

New and existing threads should accept requests and return responses without incorrectly displaying a "Subscription Sharing usage limit" error.

Actual behavior

The Codex provider consistently fails with a Subscription Sharing usage limit error, even though my ChatGPT Plus usage dashboard shows 100% remaining for the 5-hour limit and 76% remaining for the weekly limit.

Both existing and newly created T3 Code threads are marked as "Limited" and cannot process requests.

The application displays:

"ChatGPT usage limit reached. Reset time unavailable; retry manually."

Reauthenticating my ChatGPT account did not resolve the issue. The problem has persisted for more than 36 hours and completely blocks my work in T3 Code.
Impact
Blocks work completely
Version or commit
T3 Code Codex provider v0.166.0
Environment
No response
Logs or stack traces