agy-p

agy-p

Use this skill when the task is not “how do I use the Antigravity TUI manually?”, but rather:

• “How do I call agy from code?”
• “Can another agent/script use my Google-backed Antigravity subscription?”
• “How do I run Antigravity headlessly?”
• “How do I resume an agy conversation programmatically?”
• “Why is agy -p hanging / asking for permissions / printing weird extra output?”

This skill is about the CLI subprocess integration path.

---

Mental model

agy has two distinct modes:

1. Interactive TUI mode — plain agy
2. Headless one-shot print mode — agy -p / agy --print

For programmatic integrations, prefer print mode unless you truly need the live TUI.

The key idea: agy authenticates using the same user’s local Antigravity credentials, so a script can usually reuse the existing Google-backed login without needing a separate API key.

---

Fast answer

For a one-shot scripted call, start here:

agy \
  --dangerously-skip-permissions \
  --print-timeout 10m \
  -p "Summarise the repo and suggest the next 3 actions"

Good defaults for integrations:

• set the working directory deliberately
• add --dangerously-skip-permissions if the task may use tools
• set --print-timeout explicitly
• optionally set --model
• capture stdout and stderr
• treat the command as a subprocess, not an API

---

Verified local facts

These were verified locally on this machine with agy 1.0.6:

• Binary path: <AGY_BIN>
• agy --help exposes: --print, --prompt, --dangerously-skip-permissions, --print-timeout, --model, --conversation, --continue, --sandbox, --add-dir, --log-file, --prompt-interactive
• agy --help also lists shell subcommands: changelog, help, install, models, plugin, plugins, update
• agy models works non-interactively and currently lists:
  • Gemini 3.5 Flash (Medium)
  • Gemini 3.5 Flash (High)
  • Gemini 3.5 Flash (Low)
  • Gemini 3.1 Pro (Low)
  • Gemini 3.1 Pro (High)
  • Claude Sonnet 4.6 (Thinking)
  • Claude Opus 4.6 (Thinking)
  • GPT-OSS 120B (Medium)
• A fresh print call like agy -p "Reply with exactly: AGY_OK" returned clean stdout
• Output redirection to a file worked locally on Linux in testing
• --conversation <id> and --continue both worked for follow-up turns
• Important integration caveat (local observation, not promised contract): in local testing, resumed print-mode calls emitted prior assistant replies on stdout before the newest reply. Do not assume resumed output is only the latest turn.