Antigravity Tab Completion Not Working? Here's How to Fix It

There's a particular kind of frustration that hits when you switch to a new AI editor expecting magical completions, and then… nothing happens when you press Tab. Or worse, completions show up but suggest patterns that have nothing to do with your actual project—recommending Redux when you're using Zustand, or generating plain JavaScript when you're deep in a TypeScript codebase.

Tab completion is one of Antigravity's most visible day-to-day features, and when it misbehaves, the whole experience suffers. The good news is that most issues fall into a small set of categories, and once you know where to look, they're usually quick to resolve. Let's walk through them systematically.

Step One: Verify Completions Are Actually Enabled

This sounds obvious, but it's the most commonly overlooked cause. After a fresh install or after resetting settings, tab completion can end up disabled without any visible indication.

Open Antigravity's settings panel (⌘, on Mac, Ctrl+, on Windows/Linux) and look for the AI Completions section. Two things to verify:

• Enable Tab Completion is toggled on
• Model for Completions is set to an actual model (e.g., gemini-flash-lite), not None

If you have a project-level settings override, also check .antigravity/settings.json:

// .antigravity/settings.json
{
  "completions": {
    "enabled": true,
    "model": "gemini-flash-lite",
    "triggerDelay": 150
  }
}

If "enabled" is false, that's your culprit. Flip it to true, save the file, and restart Antigravity. That alone solves a surprising number of "completions are broken" reports.

Completions Don't Appear at All: Check Your Network and File Settings

If settings look correct but completions still never show up, the next areas to investigate are network connectivity and file-type exclusions.

Network connectivity

Antigravity's completion engine relies on cloud API calls. If you're on a corporate network with an outbound proxy, connected to a VPN, or in a restricted environment, those API calls may be silently blocked.

# Quick connectivity check from your terminal
curl -I https://generativelanguage.googleapis.com
 
# You should see something like: HTTP/2 200
# A timeout or 403 indicates a network-level block

If you're on a corporate network, ask your IT team to whitelist *.googleapis.com. This is typically a one-time setup that resolves the issue permanently.

File types being excluded

Antigravity lets you disable completions for specific file types. Check Settings → Completions → Excluded Languages to make sure your target language (TypeScript, Python, etc.) hasn't accidentally been added to that list.

Also worth knowing: very large files—think 5,000+ lines—can cause the completion engine to time out or give up silently. If completions work fine in smaller files but fail in one large file, that's likely the reason. Consider splitting the file, or switch to using the chat agent for that particular file.

Completions Appear but Feel Off: Fix the Context

When suggestions appear but feel generic or mismatched to your project, the issue is almost always insufficient context. The completion model generates suggestions based on what it knows about your codebase—and if that knowledge is thin, you'll get generic results.

Add a project rules file

Creating .antigravity/rules.md (or RULES.md in your project root) with a few lines about your project's conventions is surprisingly effective. You don't need paragraphs—even a short list makes a noticeable difference:

# .antigravity/rules.md
 
## Project conventions
- State management: Zustand only (no Redux, no Recoil)
- API calls: centralized in src/lib/api.ts
- Styling: Tailwind CSS (no styled-components)
- Async: always use async/await (no Promise chains)
- Components: functional only (no class components)

After adding this file, restart Antigravity to flush the completions cache. You should notice the suggestions aligning more closely with your actual patterns.

Make sure key files are in your Workspace

The completion model only sees files that are part of your active Workspace. If your type definitions (.d.ts files), package.json, or tsconfig.json are outside the Workspace boundary, the model won't have access to your library's API signatures.

Open the Workspace settings (⌘⇧P → "Antigravity: Configure Workspace") and verify that your key project files are included.

TypeScript Path Aliases and Type Completions Are Missing

If you're in a TypeScript project and completions don't suggest your path aliases (@/components, ~/lib, etc.), or type information feels incomplete, the most common cause is tsconfig.json not being properly recognized.

This problem is especially common in monorepos or projects where tsconfig.json lives in a non-standard location. Antigravity may not know which config file to use.

The fix is straightforward: go to Settings → TypeScript → Config File Path and point it explicitly to your project's tsconfig.json.

// Example tsconfig.json with path aliases
{
  "compilerOptions": {
    "baseUrl": ".",
    "paths": {
      "@/*": ["src/*"],
      "~/lib/*": ["lib/*"]
    }
  }
}

Once Antigravity correctly loads your tsconfig.json, typing @/ should immediately start showing files from your src/ directory as completion candidates.

When Nothing Works: Clear the Cache and Check the Logs

If you've gone through the above steps and completions are still misbehaving, a corrupted cache or a transient engine error may be the cause.

Clearing the completions cache

# macOS
rm -rf ~/Library/Caches/Antigravity/completions-cache
rm -rf ~/Library/Application\ Support/Antigravity/model-cache
 
# Windows (PowerShell)
# Remove-Item -Recurse -Force "$env:LOCALAPPDATA\Antigravity\completions-cache"

After deleting the cache, do a full quit and relaunch—don't just click "restart." The process needs to fully exit for the cache to clear properly.

If you're using the VS Code extension version of Antigravity, you can also run "Antigravity: Reset Completions Cache" from the Command Palette (⌘⇧P).

Reading the completions log

The output log is your best friend when diagnosing completion failures. Go to View → Output and select "Antigravity Completions" from the dropdown.

Here's what the common errors mean and how to respond:

• 401 Unauthorized — Your session has expired. Sign out and back in.
• 429 Too Many Requests — You've hit your plan's rate limit. Wait a few minutes or consider upgrading.
• 5xx errors — Server-side issue on Antigravity's end. Usually resolves itself within a few minutes; just wait and retry.

If the log shows no errors at all, the completion engine is working correctly. That points back to a context or configuration issue rather than a connectivity problem.

Where to Start

The majority of tab completion problems come down to either a disabled setting or thin project context. Start with the settings panel—confirm completions are turned on and a model is selected. If they're enabled but the suggestions feel off, spend five minutes writing a .antigravity/rules.md file. It's a small investment that tends to make a noticeable difference in how well the AI understands what you're building.