Work and Personal Gemini CLI Accounts

Mixing a personal Google account with a work Gemini CLI setup risks conversation history, cached files, and configuration bleeding between the two. Because Gemini CLI keeps everything together under ~/.gemini, isolating them fully is actually simpler than with tools that split credentials from config.

CLI method

1. Add your work account.

If you haven’t run aisw init on this machine yet, start there, it bootstraps ~/.aisw/ and, if Gemini CLI is already signed in, offers to import the account right in the prompt:

aisw init

Otherwise, or to add a second account after init, capture it explicitly:

aisw add gemini work --from-live

2. Add your personal account.

aisw add gemini personal

3. Switch based on what you’re doing.

aisw use gemini work
# ... work session ...
aisw use gemini personal

4. Verify isolation.

aisw status

Confirms the active profile and that its state mode is Isolated, the only mode Gemini CLI supports.

Desktop method

The current public AI Switcher Desktop release covers macOS, Windows x64, and Linux x64. Download the matching build from /download/, then use the same work/personal profile flow below.

1. Open AI Switcher Desktop and go to Overview.
2. Add both profiles under the Gemini CLI column if you haven’t already.
3. Click Activate on whichever one matches your current session.

Common problems

If Gemini CLI still shows your personal history after switching to a work profile, confirm you actually ran aisw use gemini work rather than just adding the profile, adding a profile saves credentials but doesn’t activate them.

If adding the second account fails with an error naming your work profile, that usually means you’re still signed into the work Google account when aisw add gemini personal runs, aisw checks the underlying identity and won’t save the same account twice under different names. Sign out of Gemini CLI (or sign into the personal account first) before adding it.