Keep Work and Personal Antigravity Accounts

Using Antigravity CLI for both work and personal projects is safer when the account boundary is explicit. aisw keeps the two logins named and makes the active choice visible before you start coding.

1. Capture the work account

Sign in to the work account through Antigravity CLI’s native flow, then save the live account:

aisw add antigravity work --from-live

2. Capture the personal account

Sign in to the personal account through the provider’s own flow and save it separately:

aisw add antigravity personal --from-live
aisw list antigravity

Both profiles are local. AI Switcher does not proxy prompts, sync credentials, or create a second Antigravity CLI authentication service.

3. Switch before you code

aisw use antigravity work
aisw verify

When you move to a personal repository:

aisw use antigravity personal
aisw verify

Prevent the wrong account in a repository

For stronger protection, group the intended account in a context and bind that context to the repository:

aisw context create personal --antigravity personal
aisw workspace bind . --context personal
aisw workspace guard --mode strict

The shell guard checks the binding before a coding-agent launch and tells you which context is expected when the active state is wrong.

Desktop workflow

AI Switcher Desktop exposes the same named profiles and context bindings in a visual interface. Select the Antigravity CLI profile you need, activate it, and confirm the live-match indicator before opening the repository.

Important state-mode detail

Antigravity CLI is currently supported through shared-state switching. That means aisw separates saved account profiles, but it does not claim to isolate every piece of Antigravity CLI’s local runtime configuration per account. Use repository guardrails when account correctness matters most.