You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Login with 'Team' plan incorrectly detected as 'Free' plan and usage prohibited #1984
@natzgg If you want to change to use a different account that has a different plan, you just do /logout and then start again. But the problem discussed in this issue is not "changing the plan", but that Team plan being detected as Free plan.
Codex CLI logs in but still shows Free account, cannot use Team subscription
After installing @openai/codex and logging in, the CLI still shows my account as Free, so I cannot use features that require a subscription.
My situation:
• I have a ChatGPT Team subscription.
• The Team account was created later, while I also have an older personal ChatGPT (Free) account. Both use the same Gmail login method.
• When logging into Codex CLI, the browser may default to my older personal account (Free workspace), even though I have switched to the Team workspace in the ChatGPT web UI.
• I have tried logging out, clearing cache, switching workspaces in the web UI, and using incognito mode to reauthorize, but the CLI still doesn’t detect the Team subscription.
• There is no OPENAI_API_KEY set in my environment variables.
• The Team features work fine in the web UI.
Steps to reproduce:
1. Install Codex CLI:
npm install -g @openai/codex
codex --version # latest version
2. In the ChatGPT web UI, switch to the Team workspace (avatar → Workspaces → select Team)
3. Run codex login → choose Sign in with ChatGPT
4. After login, the CLI still shows Free account status
Expected result:
The CLI should recognize the Team subscription after login and unlock the corresponding features.
Possible cause:
• The login flow binds to the current browser session, but my browser defaults to the old account’s Free workspace.
• Codex CLI may not be handling multiple Google accounts correctly and is not picking the Team account.
Question:
Is there a way to force Codex CLI to select/target the Team workspace during login, or otherwise ensure that in multi-account scenarios it recognizes the Team subscription?
@MILKMILKKING almost exactly describes my problem, as well. The only difference is that I don't log in with GMail, but with user/password. The rest is the same: There's an old free account I used before starting our Team subscription.
anyone found a better workaround to this? latest Codex desktop application 260208.1016 (571) and I still can't login with our company Workspace, stuck on personal, even with edits to the ~/.codex/auth.json with the non-personal Account ID ..
I can switch to the Workspace at chatgpt.com but not from Codex desktop ..
@mikem-coalesce, this issue was resolved and closed many months ago. If you're experiencing a problem today, it's almost definitely a different issue even if the symptoms might appear similar. Please look for an active bug report, and if you can't find one, file a new one. Thanks!
Activity
HenriNext commentedon Aug 8, 2025
Version 0.19.0 has still the same problem
seop-archisketch commentedon Aug 8, 2025
Waited for the
0.19.0release, but still has the same problem. Team Plan is considered Free on/statusnatzgg commentedon Aug 8, 2025
I'm having the same issue. How to change the plan?
357749948 commentedon Aug 8, 2025
I'm having the same issue.plus.
HenriNext commentedon Aug 8, 2025
@natzgg If you want to change to use a different account that has a different plan, you just do /logout and then start again. But the problem discussed in this issue is not "changing the plan", but that
Teamplan being detected asFreeplan.hiddow commentedon Aug 8, 2025
Same issue here!
gpeal commentedon Aug 8, 2025
Duplicate of #1977
hongfeiyang commentedon Aug 8, 2025
Same issue
MILKMILKKING commentedon Aug 8, 2025
Same issue
MILKMILKKING commentedon Aug 8, 2025
Codex CLI logs in but still shows Free account, cannot use Team subscription
After installing @openai/codex and logging in, the CLI still shows my account as Free, so I cannot use features that require a subscription.
My situation:
• I have a ChatGPT Team subscription.
• The Team account was created later, while I also have an older personal ChatGPT (Free) account. Both use the same Gmail login method.
• When logging into Codex CLI, the browser may default to my older personal account (Free workspace), even though I have switched to the Team workspace in the ChatGPT web UI.
• I have tried logging out, clearing cache, switching workspaces in the web UI, and using incognito mode to reauthorize, but the CLI still doesn’t detect the Team subscription.
• There is no OPENAI_API_KEY set in my environment variables.
• The Team features work fine in the web UI.
Steps to reproduce:
1. Install Codex CLI:
npm install -g @openai/codex
codex --version # latest version
Expected result:
The CLI should recognize the Team subscription after login and unlock the corresponding features.
Possible cause:
• The login flow binds to the current browser session, but my browser defaults to the old account’s Free workspace.
• Codex CLI may not be handling multiple Google accounts correctly and is not picking the Team account.
Question:
Is there a way to force Codex CLI to select/target the Team workspace during login, or otherwise ensure that in multi-account scenarios it recognizes the Team subscription?
jimmyn commentedon Aug 8, 2025
I'm facing the same issue
LuigiPagani commentedon Aug 8, 2025
same issue
thejeed commentedon Aug 8, 2025
@MILKMILKKING almost exactly describes my problem, as well. The only difference is that I don't log in with GMail, but with user/password. The rest is the same: There's an old free account I used before starting our Team subscription.
So... +1
Granluke commentedon Aug 8, 2025
Same issue here
robin-liquidium commentedon Aug 8, 2025
facing the same issue
samuelbirocchi commentedon Aug 8, 2025
I can't even login. When I try I get the following error:
Route Error (400 ): {
"error": {
"message": "No eligible ChatGPT workspaces found.",
"type": "invalid_request_error",
"param": null,
"code": "chatgpt_account_missing"
}
}
murilocurti commentedon Aug 8, 2025
same here codex version 0.19.0
willenbug commentedon Aug 8, 2025
Some updated instructions from another thread (original credit to @mrairdon-midmark).
This works on Linux, Mac OS, and Windows if installed under WSL:
javascript:alert(document.cookie.match(/(?:^|;\s*)_account=([^;]*)/)?.[1] || 'Cookie not found');and press enter~/.codex/auth.jsonfile. Do not change anything elsemikem-coalesce commentedon Feb 9, 2026
anyone found a better workaround to this? latest Codex desktop application
260208.1016 (571)and I still can't login with our company Workspace, stuck on personal, even with edits to the~/.codex/auth.jsonwith the non-personal Account ID ..I can switch to the Workspace at chatgpt.com but not from Codex desktop ..
etraut-openai commentedon Feb 9, 2026
@mikem-coalesce, this issue was resolved and closed many months ago. If you're experiencing a problem today, it's almost definitely a different issue even if the symptoms might appear similar. Please look for an active bug report, and if you can't find one, file a new one. Thanks!