Existing issues
What happened?
Win-CodexBar does not retain two independently authenticated Codex users when both belong to the same ChatGPT Team workspace. After adding the first user and then the second, only one saved account remains visible even though the users have separate identities and independent usage quotas.
Both users should remain available as distinct saved accounts in Settings and the tray account list.
Affected area
Steps to reproduce
- Use two different OpenAI users that belong to the same ChatGPT Team workspace.
- Add or authenticate the first user through the Codex account controls.
- Add or authenticate the second user.
- Open the saved account list in Settings or the tray panel.
- Observe that only one user is retained.
Logs, screenshots, or recordings
No credential or account files are attached because they contain private authentication data. The behavior was reproduced manually with two separate users in the same Team workspace.
App version
v0.60.3. Equivalent identity-matching behavior was also present on main at commit 8cdd2cad before the fix.
Windows version
Not provided.
Additional context
The users share the Team workspace/account identifier but have different authenticated user subjects and email identities. A shared workspace identifier should not override conflicting user evidence, and removing one user must not remove or reuse the other user's managed home.
This issue concerns desktop saved-account discovery and reconciliation. CLI --all-accounts enumeration is outside this issue.
Existing issues
What happened?
Win-CodexBar does not retain two independently authenticated Codex users when both belong to the same ChatGPT Team workspace. After adding the first user and then the second, only one saved account remains visible even though the users have separate identities and independent usage quotas.
Both users should remain available as distinct saved accounts in Settings and the tray account list.
Affected area
Steps to reproduce
Logs, screenshots, or recordings
No credential or account files are attached because they contain private authentication data. The behavior was reproduced manually with two separate users in the same Team workspace.
App version
v0.60.3. Equivalent identity-matching behavior was also present on main at commit
8cdd2cadbefore the fix.Windows version
Not provided.
Additional context
The users share the Team workspace/account identifier but have different authenticated user subjects and email identities. A shared workspace identifier should not override conflicting user evidence, and removing one user must not remove or reuse the other user's managed home.
This issue concerns desktop saved-account discovery and reconciliation. CLI
--all-accountsenumeration is outside this issue.