Skip to content

COMMANDS.md

Latest commit

 

History

History
57 lines (42 loc) · 4.63 KB

COMMANDS.md

File metadata and controls

57 lines (42 loc) · 4.63 KB
Raw

Commands

/antigravity menu

Open /antigravity in the configured OpenCode or Pi host. It opens a shared menu rather than accepting the old per-feature slash commands or their arguments. Sections and actions depend on the host and active credential source.

Section Use
Accounts / Sign in Inspect, enable/disable, remove, or reauthorize local accounts; start Google OAuth when local authority permits
Quota Inspect readings or check quota now
Routing Inspect the effective account selection strategy and configuration key
Limits Configure OpenCode's killswitch and account floors
Diagnostics Adjust OpenCode logging and wire-dump capture; treat dumps as sensitive
Vault Request enrollment, choose approved accounts, or disconnect to use local credentials again

Both OpenCode generations expose the shared account menu through their own terminal UI; account and credential operations run on the server. See OpenCode 2's menu and sidebar for its host integration.

Standalone CLI

The antigravity-auth bin ships inside @cortexkit/opencode-antigravity-auth; no separate CLI package is needed:

npx -y @cortexkit/opencode-antigravity-auth --help
npx -y @cortexkit/opencode-antigravity-auth login --no-browser
npx -y @cortexkit/opencode-antigravity-auth list --json
npx -y @cortexkit/opencode-antigravity-auth quota --refresh --json

Use the intended build's CLI, especially for initialization, migration, or rollback; an older npm CLI may not implement those operations. The parser accepts:

antigravity-auth setup
antigravity-auth login [--project <id>] [--no-browser]
antigravity-auth list [--json]
antigravity-auth quota [--json] [--refresh]
antigravity-auth init
antigravity-auth migrate --offline [--yes]
antigravity-auth rollback --offline [--yes]
  • setup: guided host detection/registration and optional vault enrollment. See setup --help for its options.
  • login: PKCE and a local callback at http://localhost:51121/oauth-callback. --project <id> pins the project before login. --no-browser prints the URL; headless detection (SSH_*, OPENCODE_HEADLESS=1) also avoids browser launch. It does not free an occupied callback port. See remote callback troubleshooting.
  • list: INDEX, EMAIL, and STATUS (active, disabled, ineligible, or verification-required); --json emits the same data as JSON.
  • quota: ACCOUNT, STATUS, GROUP, REMAINING, and RESET; --refresh forces a live reading and --json emits the same array as JSON.
  • init, migrate, rollback: change the active local store. Follow offline migration and rollback first; --yes skips the prompt, not the stopped-process requirement.

Exit codes are 0 for success, 1 for a thrown error, and 2 for parse failure, including unsupported commands/options. list and quota do not initialize or migrate account storage.

Pool replacement, not account addition: standalone antigravity-auth login starts or replaces the local account pool; it does not append an account to an existing pool. When setup performs local OpenCode OAuth, it adds accounts; the host's account menu also adds accounts. Use /antigravity → Sign in to add an account without replacing the existing pool. Initialize a fresh store or complete offline migration first; do not recreate the legacy file or delete store files to bypass those requirements.

Host login routes

  • OpenCode 1: initialize/migrate the pool, then select Antigravity (Google OAuth) from Google provider login, or use /antigravity → Sign in.
  • OpenCode 2: use Google (antigravity-auth pool, browser), then select the saved Antigravity connection. For approved vault mode, choose Use approved Antigravity vault instead. The OpenCode 2 guide explains why ordinary native Google credentials do not activate plugin requests.
  • Pi: pi install npm:@cortexkit/pi-antigravity-auth, start pi, then /login google. Models use google/antigravity-…. The extension is discovered via pi.extensions; local credentials stay in Pi's native Google slot, not the OpenCode pool. See Pi's guide and vault custody.

If project lookup fails, local login can use fallback project rising-fact-p41fc. For a project permission refusal, enable the Gemini for Google Cloud API on your own project and use login --project <id>; do not hand-edit retired pool JSON. Vault accounts require the vault operator's help.