Antigravity Cmd+K Inline Edit Not Responding: 7 Things to Check

You select a few lines, hit ⌘K, and... nothing. The little inline prompt that usually slides in just isn't there. Or it shows up, you type your instruction, hit Enter, and the spinner runs until you give up. When Cmd+K stops working in Antigravity, half the value of the editor evaporates. I lost a solid thirty minutes hunting down the cause during a Next.js refactor before I learned to triage it systematically.

This article is the order I now follow. Each step takes one to two minutes, and if you go top-to-bottom, you'll usually find the culprit before you finish reading. The steps are arranged by how often they actually turn out to be the cause in my own experience, not by how much each one sounds like the right answer.

Suspect a keybinding override first

Surprisingly often, another extension or a stale user config has stolen ⌘K. In Antigravity, ⌘K triggers inline edit, but ⌘K is also the historical chord-prefix for VS Code's keychord system, which means dozens of commands sit on it by default. Any one of those can take precedence depending on context.

Open the command palette with ⌘⇧P and run Preferences: Open Keyboard Shortcuts. Type cmd+k in the search box. If antigravity.editInline (the exact ID may differ in your build) sits at the top, you're fine. If a third-party extension's command outranks it, you have a conflict. The "When" column tells you under which conditions each binding fires; an override that fires only when an editor is focused will silently win in exactly the situations where you most want Cmd+K.

// keybindings.json — pin Cmd+K to inline edit and disable the keychord starter
{
  "key": "cmd+k",
  "command": "antigravity.editInline",
  "when": "editorTextFocus && !inputFocus"
},
{
  "key": "cmd+k",
  "command": "-workbench.action.keychord.start"
}

The second entry is the trick: it explicitly removes the legacy keychord start binding. Without it, your override works most of the time but fails in odd contexts (especially right after the panel gains focus, or when the editor is in a split view). After saving, hit Cmd+K once in any source file to confirm the binding fires before you go any further.

The model is unset, or you've hit a quota wall

Look at the model name in the bottom-right of the status bar. If it shows Gemini 2.5 Pro or similar, you're good. If it says Select Model or is blank, inline edit will refuse to start, often without any visible error. The dropdown can lose its selection after an update or after switching workspaces, so it's worth a quick glance.

Quota throttling is sneakier. The status bar dims slightly but doesn't pop a clear error. Run Antigravity: Show Usage from the palette to confirm your daily credit balance. On the Free plan, Cmd+K responses can stall during peak hours; for heavy refactor sessions I usually switch to Pro to avoid the stutter, then drop back to Free when I'm reading or doing lighter work.

If usage limits keep biting, the Antigravity credits and quota troubleshooting guide walks through how to read your usage breakdown and what each plan actually buys you in terms of inline edit budget.

How selection and context can quietly break Cmd+K

Cmd+K uses your cursor position or selection as context, but there are subtle traps that don't surface as errors:

• A zero-character selection (just a cursor) works, but response quality drops sharply because the model has only a few surrounding lines to anchor on
• Selecting an entire multi-thousand-line file makes the request hang for a long time and often fails after the streaming timeout
• With multi-cursor selections, only the position you clicked last is sent as the primary anchor — the others are mostly ignored
• Folded code regions are still part of the selection from the editor's point of view, so a small visible selection can secretly carry hundreds of folded lines

In practice, selecting a single function or about fifty lines gives you the highest success rate. When you want to rewrite the whole file, switch to the Cmd+I chat or the Agent mode instead. The split between inline edit and chat is something the Antigravity Cmd+I inline chat mastery guide walks through clearly, including which kinds of refactors map to which surface.

The silent failure mode behind corporate proxies

If you connect through a corporate proxy or VPN, you may see chat work fine while inline edit alone goes silent. Chat tends to ride a WebSocket connection while inline edit uses a separate HTTP/2 streaming endpoint, and many proxy rules quietly block the latter while allowing the former. From the user's point of view it looks random — chat works, completion works, but inline edit just hangs.

Open Settings, search for proxy, and configure both http.proxy and http.proxyStrictSSL for your environment.

{
  "http.proxy": "http://proxy.example.com:8080",
  "http.proxyStrictSSL": true,
  "antigravity.network.preferStreamingHttp": false
}

The last setting flips Antigravity from streaming responses to chunked responses. You lose a bit of perceived speed, but tightly controlled proxies tend to let chunked traffic through. For the broader picture of network restrictions and SSL inspection, the corporate proxy and firewall fix article covers the certificate pitfalls that come with it, which are the second most common cause of this exact symptom.

Extensions and IMEs that swallow the keystroke

Vim emulators, Emacs keybinding extensions, and various input helpers love to hook ⌘K. If one of them captures the event first, Antigravity never sees it. The fastest way to confirm this is to disable all extensions for the workspace (Extensions: Disable All Installed Extensions in Workspace), restart, and test. If Cmd+K springs back to life, re-enable extensions one by one to find the culprit. It's worth doing this even if you don't think you have a conflicting extension installed — auto-installed recommended extensions sneak in surprisingly often.

For Japanese, Chinese, or Korean input, your IME can also intercept ⌘K mid-conversion. Once you commit the conversion, the binding works again — but it's easy to think the editor itself is broken. Readers who hit IME-related quirks may find the Antigravity Japanese IME input fix useful even outside Japanese-specific issues, since the diagnosis pattern (commit the conversion, then test the shortcut) generalizes well.

When nothing above works

If you've tried all six and Cmd+K is still dead, run through this short escalation:

1. Run Antigravity: Restart Extension Host from the palette (lighter than a full restart, and resolves a surprising number of cases)
2. If that fails, fully quit Antigravity and relaunch — make sure no background process is left hanging
3. Rename ~/.antigravity/settings.json to back it up, then start fresh — this resets the user config without touching your projects
4. As a last resort, reinstall the latest Antigravity build (your profile and projects are preserved)

In my experience, step three (the config reset) fixes far more cases than people expect. After months of use, deprecated settings accumulate and quietly conflict with newer Antigravity releases. The settings.json file you back up is also useful evidence — diffing it against a fresh one tells you which old key was the problem.

Once you've recovered, do this

The single best habit I've adopted after every Cmd+K outage is putting keybindings.json and settings.json under Git in my dotfiles repo. Next time something breaks, git diff tells you exactly what changed and when. It also makes it trivial to share a known-good config with teammates who hit the same issue. For broader project-level config hygiene, the Antigravity custom rules and project config mastery guide is a good companion read.

Make your editor config a snapshot you can roll back. The next outage will resolve in a tenth of the time. Today, copy your current settings into your dotfiles repo — that's the one action this article is asking for.