Desktop app: per-account local state (project list, history, trust) instead of one shared profile across sign-ins

Feature request

Account-scoped local state in the Claude Code desktop app: when I sign out and sign in with a different Claude account, the app should show that account's own project list, session history, and directory trust records - not the shared machine-wide state.

Current behavior

The desktop app stores all local state (~/.claude, ~/.claude.json) per OS user, keyed to nothing account-specific. Signing out of a personal account and into a work account swaps only the credential: the work account still sees the personal account's recent projects, trusted directories, session transcripts, and memory (and vice versa).

Why it matters

Work/personal separation on one machine is a common setup. Today the only options are:

• Separate Windows user profiles (heavy)
• CLAUDE_CONFIG_DIR with the CLI (works well - config dir isolates settings, project list, history, and credentials together), but the desktop app does not honor or expose it, and since it launches from the Start menu there is no practical per-launch way to set it

Requested

Either of:

1. A profile/account switcher in the desktop app that keys local state to the signed-in account (each account gets its own config dir under the hood), or
2. Desktop app support for CLAUDE_CONFIG_DIR / a profile picker at launch, so the existing CLI isolation mechanism is reachable from the desktop app

Environment

• Windows 11 Home (10.0.26200)
• Claude Code desktop app (Microsoft Store / MSIX), package Claude_1.20186.1.0_x64