Repository navigation
Description
Before submitting
- I searched existing issues and did not find an open duplicate.
- I included enough detail to reproduce or investigate the problem.
Summary
When an Antigravity (agy) model (e.g., Gemini 4 Neon) triggers an approval prompt in T3 Code, the approval card only offers Allow once, Deny, and More → Cancel — there is no Allow for this thread or Allow full access for this session option whenever agy omits allow_always from its ACP session/request_permission payload.
As a result, multi-step turns (file edits outside the workspace, repeated commands, or delegated subagent rounds) force the user to click Allow once repeatedly on every single call.
Why this happens
In AntigravityAcpSupport.ts, antigravityApprovalOptions(request) only adds the session-scoped option when agy explicitly advertises kind === "allow_always":
const always = optionWithKind("allow_always");
if (always) {
options.push({
decision: "acceptForSession",
label: "Allow for this thread",
...
});
}In practice, agy frequently sends only allow_once and reject_once in session/request_permission (for example on file edits outside the workspace or escalated shell commands). When allow_always is absent:
- The approval card shows only
Allow once,Deny, andMore→Cancel. - There is no one-click way on the approval card to grant session-wide / full-access approval for the current thread (and switching the composer to Full access mid-turn also does not apply to the running turn yet — see Runtime mode changed mid-turn doesn't apply to the running turn, so Antigravity keeps asking for approval under Full access #39866).
Proposed solution
Offer a T3-handled session-level approval option on Antigravity (agy) approval cards even when agy does not include allow_always in the ACP request — for example:
Allow full access for this session(orAllow for this thread), handled on the T3 side by answering the pending request withallow_onceand upgrading the active session/thread's live permission policy (or recording a session-scoped grant in T3's ACP client policy) so subsequent prompts in the same thread/session are auto-approved without restarting the turn.
Related issues (distinct, not duplicates)
- [Bug]: Antigravity Auto asks before reads that every other runtime mode allows #40127 (PR fix(antigravity): Auto no longer asks before reads that Supervised allows #40303) — Antigravity
Autoasks before reads that other modes allow. - [Bug]: Antigravity thread set to Auto stays in agy's default mode, so every shell command asks for approval #40896 (PR fix(server): an Antigravity thread in Auto asks agy for Auto instead of silently running Supervised #40906) — Antigravity thread in
Autostaying inagy'sdefaultmode. - Runtime mode changed mid-turn doesn't apply to the running turn, so Antigravity keeps asking for approval under Full access #39866 (PR fix(server): a runtime mode switched mid-turn applies to the running ACP turn #39892) — Switching runtime mode to
Full accessmid-turn not applying to the running turn. - Antigravity ACP in Auto mode prompts "Allow once" on every built-in t3-code MCP call (no "Always allow"; "More" only shows "Cancel") #40293 (closed as duplicate of [Bug]: Antigravity asks for approval on T3's own MCP tools in Auto-accept edits #38806) — Mentioned this same missing "Always allow" / session option as an orthogonal gap in its closing comment.
Even after #40127, #40896, and #39866 land, any legitimately escalated prompt from agy without allow_always still leaves the user with only Allow once / Deny / Cancel.
Environment
- T3 Code
0.1.12-nightly.20261122.5098 - macOS (darwin arm64)
- Provider: Antigravity (
agy), model:gemini-4-neon
Activity
juliusmarminge commentedon Nov 22, 2026
Thanks for writing this up. It asks for new behaviour rather than reporting a defect, so it does not belong in the bug tracker and I'm closing it as not planned here. Feature ideas are discussed in Discussions: please post it there.