Support Antigravity as a peer of Claude Code and Codex

[dkmj]

using bram with Claude previously, but inspired by you latest column @judell wanted to try googles agy as well, in order to faclitate conversations among my team. but agi terminal is unreadable and can't find settings to control this. remember choosing settings when using bram for the first time maybe two weeks ago, now cant find how to control it (nothing in the bram Settings=

[dkmj]

realise now that agy is not supported. sorry.

[judell]

Hi Peter, yeah it took me a few minutes to understand what's going on here because I've never looked at Antigravity, I was thinking of it as another kind of terminal but no, it's an agent like Claude Code or Codex. So you could run Antigravity in Bram's xterm, and we could fix the colors, but to support Antigravity, Bram's provider architecture - which handles PTY parsing, session-file parsing, turn-end detection, etc, in a neutral way for Claude Code and Codex - would need to handle Antigravity in the same way. Given that support for just those two is still a work in progress, I'm inclined to rename this issue as "Add Antigravity as a Bram provider", does that sound right?

Thanks,

Jon

[dkmj]

Yes, "rename this issue as "Add Antigravity as a Bram provider?"" is perfect by me. I'll hack the situation for now, am very early low on the coding skills ladder. Run out of Claude tokens and sometimes need to fall back to agy (also pay for, as part of Google bundle incl photos).

Thanks.

[judell]

What V2.15's hook-first menu work does — and does not — give a future Antigravity peer.

The permission-menu cutover established the provider-adapter shape a third peer would plug into:

• a dispatch branch in permission_request_to_menu (src-tauri/src/lib.rs:2394, which keys off a provider field),
• a per-provider menu parser alongside codex_permission_request_to_menu (:2285),
• per-provider hook registration (Claude via settings.json, Codex via ~/.codex/config.toml).

So if Antigravity exposes a hook surface (a permission/PreToolUse-style event we can register and POST from), adding its menus is the same three-part adapter Codex got — not a rebuild.

Two honest caveats:

• Conditional on Antigravity having hooks. If it has no hook mechanism, menus fall back to the fragile xterm grid scraper rather than the hook path. Unknown until we know Antigravity's hook story.
• Does not address this issue's actual report. The unreadable Antigravity terminal and the missing settings control are launcher/rendering concerns, separate from menu surfacing. The menu substrate is one building block toward peer support; it doesn't fix the readability/settings problems reported here.