Skip to content

feat(antigravity): add GUI presentation mode - #649

Closed
playtix-brain wants to merge 1 commit into
SDSLeon:masterfrom
playtix-brain:feat/antigravity-gui
Closed

feat(antigravity): add GUI presentation mode#649
playtix-brain wants to merge 1 commit into
SDSLeon:masterfrom
playtix-brain:feat/antigravity-gui

Conversation

@playtix-brain

Copy link
Copy Markdown

Antigravity is currently terminal-only (presentationModes: ["terminal"]), so it cannot be used as a regular chat like the other providers.

This adds a print-mode session adapter over the agy CLI's stream-json protocol and enables gui alongside terminal. Scope is limited to src/supervisor/agents/antigravity/ — no shared runtime or UI code changes.

Verified end to end against agy 1.1.22: a GUI thread starts, streams and completes normally. Module tests: 62 passing.

🤖 Generated with Claude Code

Antigravity was terminal-only. This adds a print-mode session adapter over the
agy CLI's stream-json protocol so Antigravity threads can run as regular GUI
chats, matching the other providers.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@playtix-brain
playtix-brain requested a review from SDSLeon as a code owner August 29, 2026 02:14
@SDSLeon

SDSLeon commented Aug 29, 2026

Copy link
Copy Markdown
Owner

Thanks for the contribution and for validating that Antigravity can work in Poracode's Chat presentation.

Since this was opened, Google has published an official Antigravity ACP server—the same antigravity-acp distribution Zed installs from the ACP Registry. Poracode already consumes that registry and has shared ACP session infrastructure, so we are going to implement built-in Antigravity Chat through Google's official ACP route instead of maintaining a provider-specific agy -p one-shot session.

That route gives us the native streaming/session lifecycle, resume, cancellation, tool updates, authentication, and a supported install/update path. Once the built-in integration is complete, we will also hide the separate Antigravity ACP registry entry to avoid presenting it as a duplicate provider.

I'm closing this PR in favor of that implementation. Thanks again for taking the time to build and test this—it helped establish the Chat use case and prompted us to investigate the now-available official integration.

@SDSLeon SDSLeon closed this Aug 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants