Work and Personal Gemini CLI Accounts

Use names such as work and personal to separate eligible Gemini CLI profiles before each session. The labels describe your workflow; they do not make an unsupported personal Google sign-in eligible.

Google ended Gemini CLI service for free, Pro and Ultra individual Google sign-ins on June 18, 2026. Enterprise Code Assist, API-key and supported Vertex AI paths remain available. For two individual Google subscription accounts, use Antigravity CLI work and personal accounts instead.

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 a separate API-key profile.

For personal Gemini API use, set GEMINI_API_KEY through your local secret environment and let aisw read it without putting the key value in command arguments. This is API-key authentication, not a personal Google subscription sign-in.

aisw add gemini personal --from-env

3. Switch based on what you’re doing.

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

4. Verify the active state.

aisw status

Confirms the active profile and its state mode. Run aisw verify to compare the recorded profile with live credentials and provider selection. The switching guide explains the Gemini-owned state boundary.

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 you choose two eligible enterprise sign-ins instead of an API-key profile and 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.