Desktop app: selected local project/repo doesn't reset when switching accounts in the same window
Status Open
Maintainer reply None cached
Activity 1 comment · opened Aug 4, 2026
Claude Desktop app. When a local project/repo is manually selected in the project picker (bottom bar), that selection persists across account logout/login within the same app window — even when switching to a completely different Claude.ai account.
Repro:
- Log into Account A, manually select local repo X in the project picker.
- Log out, log into Account B (different Claude.ai account, different org).
- Repo X is still shown as the active/selected project — expected: picker should reset or prompt for a project scoped to Account B.
- Confirmed not a stale in-memory/session issue: fully quitting and relaunching the app does not clear it — the stuck selection survives a full process restart, so it must be persisted to disk (Local Storage/IndexedDB or config.json), not held in renderer memory.
What I found while investigating (may help triage):
~/Library/Application Support/Claude/claude-code-sessions/<accountUuid>/<orgUuid>/local_*.jsoncorrectly scopes individual session records per account — each has its own correctcwd.~/Library/Application Support/Claude/config.jsonholds a single sharedoauth:tokenCache/tokenCacheV2and onelastKnownAccountUuidfor the whole app instance, suggesting the picker's "currently selected project" is tracked as app-wide UI state rather than per-account — likely in Local Storage/IndexedDB, not a plain config file.
Impact:
Confusing/risky when working across a work org account and a personal account in the same window — easy to end up committing or running actions against the wrong repo while believing you're scoped to the other account.
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗