Agentic Data Plane

rpk ai run agy

Launch Antigravity CLI (agy) through Google or Vertex Gemini providers.

An isolated Gemini directory forces modelProvider=gemini without reading or changing your personal Antigravity CLI settings. The gateway key is passed only in GEMINI_API_KEY, never in command arguments or generated settings.

An ADP API key is required. The first launch asks to create one; existing managed keys are reused and renewed on launch. If a key is unavailable or declined, the command stops instead of falling back to your login token or Google account. An explicit --token may carry an ADP API key, but not a JWT.

The isolated custom model catalog registers the provider’s Gemini model IDs without renaming them. No model is selected automatically. Use /model before your first prompt, or pass --model. Explicit --model and --effort are passed to agy unchanged; the gateway still enforces its model allowlist.

Vertex uses the gateway’s Gemini API compatibility route. The gateway signs upstream Vertex requests; no Google credentials or ADC are needed on your machine. Claude-only Vertex providers are not supported by this command.

Configuration isolation and custom models require agy 1.3.5. Versions that do not recognize that flag fail rather than fall back to personal authentication. Pass Antigravity’s own arguments after a literal --.

Usage

rpk ai run agy [flags]

Flags

Value Type Description

--api-key

string

ADP API key creation: ask (prompt), yes (create without prompting), no (do not create; an explicit ADP --token is required).

-e, --effort

string

Antigravity reasoning effort (requires an explicit model).

-L, --llmprovider

string

enabled Google or Vertex Gemini provider name.

-m, --model

string

Antigravity model supported by the CLI and allowed by the provider (omit to choose with /model).

--print-config

bool

print isolated Antigravity settings and exit (no gateway call or credential).

Global flags

Value Type Description

--config

string

Redpanda or rpk config file; default search paths are ~/.config/rpk/rpk.yaml, $PWD/redpanda.yaml, and /etc/redpanda/redpanda.yaml.

-X, --config-opt

stringArray

Override rpk configuration settings; -X help for detail or -X list for terser detail.

--ignore-profile

bool

Ignore rpk.yaml and redpanda.yaml; use default settings.

--profile

string

rpk profile to use.

-v, --verbose

bool

Enable verbose logging.