Skip to content

[Feature]: Offer "Allow full access for this session" / session-level approval option on Antigravity (agy) approval cards #40933

Closed as not planned

Description

@shihasbacker

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:

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 (or Allow for this thread), handled on the T3 side by answering the pending request with allow_once and 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)

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

  1. juliusmarminge commented on Nov 22, 2026

    @juliusmarminge
    Member

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions