Switching Claude Code accounts, dont refresh cached cookie from browser, and dont show current account usage

Open
#3,663 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
64/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
swift

Research direction

Start by tracing the account-switching flow and the cached browser-cookie handling in the Swift app. Verify how usage data is refreshed after selecting “switching account...” and identify the settings path for manually refreshing or clearing the cached cookie; done means the displayed usage belongs to the selected account.

Written by the indexing model from the issue text.

Description

clawsweeper:needs-live-repro clawsweeper:needs-maintainer-review clawsweeper:needs-product-decision clawsweeper:no-new-fix-pr impact:auth-provider impact:ux-friction issue-rating: 🐚 platinum hermit P2

I use 2 CC accounts in my daily basis, but when I switch accounts, the app will still show me the usage of the account not being used currently because it is using a cached web cookie.

So, please:
1 - Allow me to refresh the cached cookie manually in settings, or at least delete/clean it.
2- When selecting "switching account..." from the options. That doesn't seem to do anything today, as it still keeps showing the previous account data.

Dominant language
Swift
Stars
21.6k
Forks
2k
Avg merge
1d 9h
Merged PRs (30d)
385

Contributor guide

No contributing guide indexed for this repository

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.

More from steipete/CodexBar

All issues in steipete/CodexBar

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.