Issue Description
Is your feature request related to a problem? Please describe.
Buzz currently supports integrations with select coding agents, but lacks native support for Antigravity CLI (agy / google-antigravity). Developers and automated workflows using Google's Antigravity CLI as their primary terminal-based agent harness cannot currently spawn or manage agy agents within Buzz workspace channels.
Describe the solution you'd like
Add Antigravity CLI as a first-class supported agent runner/harness within Buzz:
- Agent Detection & Spawn Engine: Support detecting local/remote
agy installations and spawning agent instances bound to Buzz channels via BUZZ_PRIVATE_KEY identity scoping.
- Event & Patch Mapping: Map Antigravity CLI agent actions (multi-file edits, terminal execution, NIP-34 patch proposals) directly into Buzz's Nostr event log.
- Session & Auth Handling: Integrate session export/import and credential management so Antigravity CLI agents can collaborate seamlessly alongside human teammates in project channels.
Describe alternatives you've considered
Running Antigravity CLI externally in a separate terminal session and manually copying patches and outputs into Buzz channels, which loses the unified audit trail, real-time review integration, and event history.
Additional context
Issue Description
Is your feature request related to a problem? Please describe.
Buzz currently supports integrations with select coding agents, but lacks native support for Antigravity CLI (
agy/google-antigravity). Developers and automated workflows using Google's Antigravity CLI as their primary terminal-based agent harness cannot currently spawn or manageagyagents within Buzz workspace channels.Describe the solution you'd like
Add Antigravity CLI as a first-class supported agent runner/harness within Buzz:
agyinstallations and spawning agent instances bound to Buzz channels viaBUZZ_PRIVATE_KEYidentity scoping.Describe alternatives you've considered
Running Antigravity CLI externally in a separate terminal session and manually copying patches and outputs into Buzz channels, which loses the unified audit trail, real-time review integration, and event history.
Additional context