use-gcx

Essential Principles

Load the bundled skill before acting. gcx ships 24 task-specific Agent Skills inside the binary; they carry the query patterns, manifest shapes, and investigation workflows this file deliberately omits so it does not drift from the installed version. Pick one from the routing table below and read it with gcx agent skills get <name> -otext.
Discover, never guess commands. The surface is large and versioned. gcx help-tree --depth 1 -o text orients; gcx <group> <cmd> --help gives exact flags and ends with a Related skill(s) pointer.
Agent mode is auto-detected from CLAUDECODE, PI_CODING_AGENT, CURSOR_AGENT, and similar env vars: JSON output, skipped confirmation prompts, and large responses spilled to temp files.
gcx's own prompts are not a safety net. Named resources delete selectors never prompt, datasources delete auto-approves in agent mode, and other deletes skip the prompt with --force. Confirm every mutation (create, update, delete, push, ack/silence/resolve) with the user first - the confirmation gate is you, not the CLI.
Verify the context before mutating. Contexts are named environments (kubectl-style). gcx config current-context names the active one; gcx config check --context <name> confirms it can reach the server.
Prefer dedicated commands over gcx api. They handle pagination, datasource resolution, and token-efficient output. Reserve gcx api for endpoints with no dedicated command.

command -v gcx >/dev/null 2>&1

If not found: brew install gcx.