What's happening (and it's honestly embarrassing)
If you attempt to log in with a wrong account, the entire authentication flow collapses. The app gets stuck in some cursed state where:
- It refuses to let you log in with a different account, no matter what you try
- Logging out does nothing useful
- Switching accounts is apparently not a use case anyone thought to test
And here's the truly baffling part: uninstalling and reinstalling the app barely helps. Some broken state is clearly being persisted somewhere outside the app bundle — probably in Keychain, ~/Library/Application Support, or some other location that survives a clean reinstall.
So when you finally log in with the correct account after all this mess, Claude integration is completely broken. It just doesn't work. At all.
Steps to reproduce
- Open Codexbar and attempt to log in with an incorrect account
- Notice the app enters a broken state — login with a different account is now impossible
- Uninstall and reinstall Codexbar
- Log in with the correct account
- Observe that Claude features are still non-functional
Expected behavior
Logging in with a wrong account should be a recoverable error. The user should be able to:
- Log out cleanly
- Log in with a different account without needing a workaround
- Have a fully functional session after a reinstall
This is table-stakes authentication UX. It should work.
Actual behavior
The app persists broken auth state across sessions and reinstalls, and even a successful login afterward results in Claude being completely unusable.
Environment
- macOS (Apple Silicon)
- Codexbar latest version
Fix suggestion
Please ensure that on logout — and especially on reinstall — all persisted auth state is wiped: Keychain entries, app support files, cached tokens, everything. Also worth adding a "Clear all data and log out" option for when things inevitably go sideways again.
What's happening (and it's honestly embarrassing)
If you attempt to log in with a wrong account, the entire authentication flow collapses. The app gets stuck in some cursed state where:
And here's the truly baffling part: uninstalling and reinstalling the app barely helps. Some broken state is clearly being persisted somewhere outside the app bundle — probably in Keychain,
~/Library/Application Support, or some other location that survives a clean reinstall.So when you finally log in with the correct account after all this mess, Claude integration is completely broken. It just doesn't work. At all.
Steps to reproduce
Expected behavior
Logging in with a wrong account should be a recoverable error. The user should be able to:
This is table-stakes authentication UX. It should work.
Actual behavior
The app persists broken auth state across sessions and reinstalls, and even a successful login afterward results in Claude being completely unusable.
Environment
Fix suggestion
Please ensure that on logout — and especially on reinstall — all persisted auth state is wiped: Keychain entries, app support files, cached tokens, everything. Also worth adding a "Clear all data and log out" option for when things inevitably go sideways again.