Skip to content
| Marketplace
Sign in
Visual Studio Code>Other>Antigravity VS Code Auto AcceptNew to Visual Studio Code? Get it now.
Antigravity VS Code Auto Accept

Antigravity VS Code Auto Accept

Pawnkoolong

|
2 installs
| (0) | Free
Auto accept command approvals in the latest tested official Antigravity extension for VS Code.
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

Antigravity VS Code Auto Accept

Auto-accept command approvals in the official Antigravity extension for VS Code.

Built for the latest tested official Antigravity extension for VS Code.

MIT Antigravity macOS Linux Windows

English · 简体中文

Quick Start · Features · How It Works · Configuration · Troubleshooting · Development


Keep your Antigravity agent moving while you work. This extension handles command permission cards in the official Antigravity extension for VS Code, submits Allow Once, and checks that the backend recorded the approval.

Use it alongside Antigravity in VS Code. No remote debugging port, desktop clicker, or global Turbo setting is required.

Quick Start

  1. Open your project in VS Code.

  2. Install and open Google's official Antigravity extension.

  3. Install Antigravity VS Code Auto Accept in the same extension host as Antigravity. For a VSIX, run Extensions: Install from VSIX... and select the package.

  4. In your trusted workspace, enable Antigravity VS Code Auto Accept in Settings, or add:

    {
      "antigravityVscodeAutoAccept.enabled": true
    }
    
  5. Look for AG Auto Accept: ON (0). The count increases after an approval is verified. Click the status item to pause or resume.

After an update, run Developer: Reload Window when your current task has finished. Download a VSIX from GitHub Releases, or build from source. Marketplace publication is described in the publishing guide.

Moving from the previous extension

This release uses the new extension ID Pawnkoolong.antigravity-vscode-autoaccept. Disable or uninstall Pawnkoolong.antigravity-sidebar-autoaccept before enabling the new extension, so only one instance handles approvals. Existing antigravitySidebarAutoAccept.* settings and command bindings remain compatible; explicit antigravityVscodeAutoAccept.* settings take priority. The new listing is a separate installation rather than an automatic update of the old listing.

Features

  • Official Antigravity extension support — handles command permission cards behind Allow and Submit.
  • Workspace scope — handles running conversations whose folders match this window.
  • One-time approvals — sends Allow Once without saving permanent grants.
  • Visible results — distinguishes submitted requests from verified approvals.
  • Long-conversation support — requests compact responses and skips completed history.
  • A simple switch — no extra panel and no runtime package dependencies.
  • Automatic platform support — the same installation, settings, commands, and status on Windows, macOS and Linux; no platform mode to select.

How It Works

This VS Code window
        ↓
Its official Antigravity backend
        ↓
Current-workspace command permission card
        ↓
Recheck request → Allow Once → Verify backend approval record

Some auto-accept extensions repeatedly call older Antigravity command IDs absent from the tested official VS Code extension. This adapter uses the structured approval request used by the official extension.

SUBMITTED means the backend accepted the request. VERIFIED means the matching one-time approval appeared in the step's completion record. The counter measures verified approvals, not command success.

What stays manual

This release handles command requests triggered by the default fallback policy. It leaves these to you:

  • Explicit Ask rules, hook approvals, and blocked or unknown request types.
  • Ordinary questions, plan review, MCP permissions, and browser permission cards.
  • Conversations outside the current workspace.

Eligible commands run without your click, including commands that can access files outside the project. Enable this behavior only in workspaces where you want it.

Compatibility

Component Support
Official extension google.google-antigravity 1.10.0; verified 2026-11-01
VS Code 1.90 or later
Extension host Windows, macOS and Linux; detected automatically, including local workspaces
Standalone Antigravity IDE Not the target of this adapter

The adapter uses an internal endpoint. New Antigravity versions may require an update; this table records the tested version rather than promising compatibility with future releases.

Windows uses built-in Windows PowerShell and Get-CimInstance; macOS uses ps; Linux uses /proc. All three automatically locate the backend owned by this window. No additional runtime, OS-specific configuration, or mode switch is needed.

Configuration

Setting Default Purpose
antigravityVscodeAutoAccept.enabled false Enable in this workspace.
antigravityVscodeAutoAccept.intervalMs 1000 Scan interval; minimum 500 ms.

Commands

Open the Command Palette and search for:

  • Antigravity VS Code Auto Accept: Toggle ON/OFF
  • Antigravity VS Code Auto Accept: Show Logs
  • Antigravity VS Code Auto Accept: Check Connection

Status

Status Meaning
OFF No new approvals will be submitted.
CONNECTING / WAITING Open Antigravity or wait for its backend.
ON (N) Scanning; N approvals verified since this instance started.
ERROR A connection or protocol problem needs attention; open the log.

Privacy

Requests go to the existing Antigravity backend on 127.0.0.1. The adapter starts no network listener and has no telemetry. It does not log command text, full conversations, or backend tokens, and does not change global permissions.

When Ezra Auto Accept is present, this adapter attempts to stop its old command poller in the same window. Disable the original extension's startup setting when replacing it.

Troubleshooting

Symptom What to check
WAITING Open Antigravity in this window; install both extensions in the same extension host.
ON, but a card remains Questions, non-command permissions, explicit Ask, and hook approvals stay manual.
ERROR Run Show Logs and inspect the last error.
Could not inspect Windows processes Check that Windows PowerShell and Get-CimInstance are permitted for VS Code.
Old response too large Upgrade to 0.1.1 or later and reload the window.
An update behaves like the old version Finish the task, then run Developer: Reload Window.
SUBMITTED without VERIFIED Inspect the card manually. Ambiguous submissions are not blindly retried.

For a bug report, include both extension versions, the host OS, and relevant log lines. Leave out tokens, private command text, and full conversations.

Development

Use Node.js 22 or later:

npm ci
npm run check
npm test
npm run package

The VSIX is written to dist/antigravity-vscode-autoaccept.vsix. vsce is a development dependency; the installed extension has no runtime dependencies.

For a local build without npm, use python3 package.py. To check a connection without accepting anything:

node probe.js <extension-host-pid> /path/to/workspace

On Windows, use python package.py for the Python build and quote the workspace path when probing:

node probe.js <extension-host-pid> 'C:\path\to\workspace'
.
├── core.js                 # Backend discovery and approval flow
├── extension.js            # VS Code lifecycle, commands, status
├── settings.js             # Settings and legacy-name compatibility
├── test/                   # Protocol and regression tests
├── docs/                   # Publishing and validation notes
├── .github/workflows/      # CI and release workflows
├── README.md
└── README.zh-CN.md

See Testing for validation scope and Publishing for releases.

License and Credits

MIT. Status-bar interaction was adapted from Ezra Auto Accept 1.2.0, retaining its copyright. This project adds the Antigravity protocol adapter and tests.

Independent community extension; not affiliated with or endorsed by Google or Microsoft.

  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
  • Your Privacy Choices
  • Consumer Health Privacy
© 2026 Microsoft