agy-p

Execute Antigravity CLI tasks headlessly via subprocess calls.

1|1|Updated Jun 11, 2026
One-click install
npx skills add https://github.com/valtterimelkko/agent-workflow-skills --skill agy-p
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agy-p
Source: https://github.com/valtterimelkko/agent-workflow-skills/tree/main/skills/agy-p
Command: npx skills add https://github.com/valtterimelkko/agent-workflow-skills --skill agy-p

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the challenge of integrating the Antigravity CLI into automated pipelines, scripts, and agent harnesses by providing a reliable pattern for headless, non-interactive execution.

Core Features & Use Cases

  • Headless Automation: Enables running Antigravity tasks via subprocesses without requiring a TUI.
  • Subscription Reuse: Leverages existing local user authentication to avoid complex API key management.
  • Workflow Continuity: Supports resuming specific conversation threads and managing workspace contexts programmatically.

Quick Start

Use the agy-p skill to execute a headless prompt by calling the agy binary with the print flag and the dangerously skip permissions argument.

Frequently Asked Questions about agy-p

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run Antigravity CLI tasks in headless automation pipelines?

To run Antigravity CLI tasks in headless automation, execute the agy binary via subprocess calls using the print flag and the skip permissions argument, avoiding the need for a TUI.

Can I reuse my local Antigravity authentication for automated scripts?

Yes, you can reuse local authentication for automated scripts. The integration leverages existing local user authentication state to avoid complex API key management during headless execution.

What is the best way to resume specific conversation threads programmatically with Antigravity?

The best way to resume conversation threads programmatically is using this integration pattern, which supports workflow continuity by managing workspace contexts and resuming specific conversations via subprocess calls.

What are the limitations of integrating Antigravity CLI into automated agent harnesses?

Limitations of integrating Antigravity CLI into automated harnesses include the need for careful management of subprocess timeouts, reliable stdout parsing, and maintaining local authentication state to ensure stable execution.

Does this approach require an API key to process workspace-scoped tasks?

No, processing workspace-scoped tasks does not require an API key. The integration reuses your existing local user authentication state to facilitate automated task processing.

Why does my Antigravity subprocess call fail in non-interactive environments?

Antigravity subprocess calls fail in non-interactive environments if local authentication state is invalid, if stdout parsing is incomplete, or if subprocess timeouts are not carefully managed.