Can no longer connect to devcontainer after updating to v1.16.5

Alexander_Roiatchki · February 5, 2026, 2:05pm

After updating to the new v.1.16.5 on Linux Antigravity can no longer connect to devcontainers and shows ‘Could not fetch remote environment. Failed to connect to the remote extension host server (Error: WebSocket close with status code 1006)’.

Here’s the tail of the output logs:

# Finish server setup



print_install_results_and_exit 0




[Info   - 14:02:55.467] Install options: {

  "id": "90553e2afa56b5f21a3a7409",

  "vscodeVersion": "1.107.0",

  "ideVersion": "1.16.5",

  "commit": "1504c8cc4b34dbfbb4a97ebe954b3da2b5634516",

  "quality": "stable",

  "extensionIds": [],

  "envVariables": [],

  "useSocketPath": false,

  "serverApplicationName": "antigravity-server",

  "serverDataFolderName": ".antigravity-server",

  "distroId": "1504c8cc4b34dbfbb4a97ebe954b3da2b5634516"

}

[Info   - 14:02:55.580] SSH Agent Forwarding: true

[Info   - 14:02:55.647] Server install output:

Waiting for lock...

Lock acquired, proceeding with installation.

Server script already installed in /home/vscode/.antigravity-server/bin/1.16.5-1504c8cc4b34dbfbb4a97ebe954b3da2b5634516/bin/antigravity-server

Server script is already running /home/vscode/.antigravity-server/bin/1.16.5-1504c8cc4b34dbfbb4a97ebe954b3da2b5634516/bin/antigravity-server

90553e2afa56b5f21a3a7409: start

exitCode==0==

listeningOn==37417==

connectionToken==507312017257==

logFile==/home/vscode/.antigravity-server/.1504c8cc4b34dbfbb4a97ebe954b3da2b5634516.log==

osReleaseId==debian==

arch==x86_64==

platform==linux==

tmpDir==/tmp==

90553e2afa56b5f21a3a7409: end




[Info   - 14:02:55.694] Finished installing remote server in container. Output: Waiting for lock...

Lock acquired, proceeding with installation.

Server script already installed in /home/vscode/.antigravity-server/bin/1.16.5-1504c8cc4b34dbfbb4a97ebe954b3da2b5634516/bin/antigravity-server

Server script is already running /home/vscode/.antigravity-server/bin/1.16.5-1504c8cc4b34dbfbb4a97ebe954b3da2b5634516/bin/antigravity-server

90553e2afa56b5f21a3a7409: start

exitCode==0==

listeningOn==37417==

connectionToken==507312017257==

logFile==/home/vscode/.antigravity-server/.1504c8cc4b34dbfbb4a97ebe954b3da2b5634516.log==

osReleaseId==debian==

arch==x86_64==

platform==linux==

tmpDir==/tmp==

90553e2afa56b5f21a3a7409: end




[Info   - 14:02:55.799] forwardSocket stdout: forwarder: ====socketForward=success====




[Info   - 14:02:55.800] Forwarding port 37417 for container 65e370dba477c5a9e46677d30c5b1ec833696f9200e22a3971fca14c99868062

[Info   - 14:02:55.899] forwardPort stdout: forwarder: ====forwarderPort=33761====




[Info   - 14:02:55.899] Found forwarder port: 33761

[Error  - 14:02:56.299] forwardSocket stderr: forwarder error: handleClient Error: subprocess terminated immediately with return code 127




[Error  - 14:02:56.433] forwardPort stderr: forwarder error: handleClient Error: subprocess terminated immediately with return code 127




[Error  - 14:02:56.946] forwardPort stderr: forwarder error: handleClient Error: subprocess terminated immediately with return code 127

Matthew_Fisch · February 5, 2026, 3:01pm

… still going strong with SSH remotes

Imraj_Singh · February 5, 2026, 5:54pm

Updated today and I have the exact same errors with my devcontainers

Alexander_Roiatchki · February 5, 2026, 5:56pm

I managed to downgrade back to 1.15 on Fedora and now I can use them again, but this isn’t ideal cause some extensions start notifying about updating Antigravity + there’s no way to know if Google might decide to drop support for this version and then I won’t be able to log in and use it.

Imraj_Singh · February 5, 2026, 6:14pm

Thanks, I think this may trigger my migration back to vscode… Also, I imagine developers of the extensions will prioritise ensuring it works on vscode rather than antigravity.

KipK · February 5, 2026, 9:54pm

Same problem here since latest update. Can’t even roll back to previous version as you’ve blocked it.
So can’t even work with antigravity anymore.

Don’t you test builds before release at google ?

Abhijit_Pramanik · February 6, 2026, 12:09am

Thank you for the report. This has been escalated to our engineering team for investigation.

To provide our developers with the necessary diagnostic data, we encourage you to use the in-app feedback tool (found via the Feedback icon in the top-right corner > Report Issue). This is the most efficient way to ensure a prompt resolution.

Ashwin_Krishnan · February 6, 2026, 4:14pm

I was really frustrated with this issue, too. I spent the better part of the last 2 days trying to find the problem

Had Gemini to summarise the bug, cause and a potential hack until Google fixes this properly
Have still not managed to get Docker in Docker working, though

Hope it helps some of you.

Summary

Antigravity version 1.16.5 fails to connect to dev containers with

forwardSocket/forwardPortsubprocess exit code 127 (“command not found”). The root cause is a path mismatch in thegetRemoteServerNodePathfunction.

Environment

Antigravity Version: 1.16.5 (commit 1504c8cc4b34dbfbb4a97ebe954b3da2b5634516)
OS: macOS (also likely affects Linux)
Container: Debian-based devcontainer (aarch64)

Symptoms

forwarder error: handleClient Error: subprocess terminated immediately with return code 127

WebSocket close with status code 1006

Root Cause

The getRemoteServerNodePath function in antigravity-dev-containers extension constructs an incorrect path to the remote node binary.

The Bug

Location:

antigravity-dev-containers/dist/extension.js→getRemoteServerNodePath()


// Buggy code (deobfuscated):

getRemoteServerNodePath(output) {

const parsed = this.getRemoteServerHomeAndCommitHash(output);

return `${parsed.serverHome}/bin/${parsed.commitHash}/node`;

//                                ^^^^^^^^^^^^^^^^^^

//                                Missing ideVersion prefix!

}

Expected path: /home/user/.antigravity-server/bin/1.16.5-{commitHash}/node
Actual path constructed: /home/user/.antigravity-server/bin/{commitHash}/node

The server installation script (generateBashInstallScript) installs to:

SERVER_DIR="$SERVER_DATA_DIR/bin/$DISTRO_IDE_VERSION-$DISTRO_ID"

# e.g., .antigravity-server/bin/1.16.5-1504c8cc4b34.../

But getRemoteServerNodePath omits the $DISTRO_IDE_VERSION- prefix when reconstructing the path.

Verification

 #Path WITHOUT version prefix - DOES NOT EXIST

docker exec <container> test -f ~/.antigravity-server/bin/1504c8cc4b34.../node

# Result: NOT FOUND

# Path WITH version prefix - EXISTS

docker exec <container> test -f ~/.antigravity-server/bin/1.16.5-1504c8cc4b34.../node

# Result: EXISTS

Suggested Fix

Update getRemoteServerNodePath to include the IDE version in the path:

getRemoteServerNodePath(output) {

const parsed = this.getRemoteServerHomeAndCommitHash(output);

if (!parsed) return null;

// Fix: Include ideVersion prefix in path

return `${parsed.serverHome}/bin/${parsed.ideVersion}-${parsed.commitHash}/node`;

}

getRemoteServerHomeAndCommitHash(output) {

// Update regex to capture ideVersion as well

const match = output.match(/logFile==(.+?\/\.[^\/]+)\/\.([a-f0-9]{40}(?:-dev)?)\.log==/);

if (!match) return null;

// Also parse ideVersion from the output

const ideVersionMatch = output.match(/ideVersion==([^=]+)==/);

return {

        serverHome: match[1],

        commitHash: match[2],

        ideVersion: ideVersionMatch ? ideVersionMatch[1] : this.getIdeVersion()

    };

}

Workaround

Add this to your devcontainer’s

postCreate command to create symlinks:

# Antigravity server symlink workaround

# Bug: Antigravity looks for node at .../bin/{commit}/node

# but server installs to .../bin/{version}-{commit}/node

(

	SERVER_DIR="$HOME/.antigravity-server/bin"

	mkdir -p "$SERVER_DIR"

while true; do

for dir in "$SERVER_DIR"/*-*; do

if [ -d "$dir" ]; then

				dirname=$(basename "$dir")

				commit="${dirname#*-}"

				symlink="$SERVER_DIR/$commit"

if [ ! -e "$symlink" ]; then

					ln -s "$dir" "$symlink" 2>/dev/null &&

						echo "Antigravity workaround: Created symlink $commit -> $dirname"

fi

fi

done

		sleep 5

done

) >/dev/null 2>&1 &

For an existing container, run manually:

docker exec -u <user> <container> ln -s \

~/.antigravity-server/bin/1.16.5-<commit> \

~/.antigravity-server/bin/<commit>

Discovered on 2026-02-06. Affects Antigravity 1.16.5. Previous versions may not be affected if they used a different path structure.

Muhammad_Nisar · February 6, 2026, 10:49pm

xNeo · February 7, 2026, 2:55am

I can confirm this worked for me, thanks!

against_vegetables · February 8, 2026, 6:57pm

Is there any update? This is a critical bug.

Regarding the reports from the IDE: there’s no feedback at all - it looks like the report just disappears into the void. That’s why I have to write here.

lgonzalez · February 8, 2026, 10:33pm

it works for me also! -10% cortisol.

Thanks @Ashwin_Krishnan !

Alexander_Roiatchki · February 10, 2026, 6:44am

Thanks for sharing this! The manual fix worked for me but couldn’t quite make it work with the postCreate command. Still, this finally let me use the newest version of agy. I hope Google will start implementing some type of hotfixes for serious issues like this that seem to have relatively easy resolutions.

Topic		Replies	Views
Failed to connect to the remote extension host server (Error: WebSocket close with status code 1006). Google Antigravity bug	0	82	February 8, 2026
Antigravity and Docker compatibility issue in v1.16.5? Google Antigravity bug	1	247	February 5, 2026
Is There Problem with Dev container? Google Antigravity bug	2	189	February 6, 2026
Unable to attach running container after upgrade (now 1.16.5) Google Antigravity bug	0	166	February 5, 2026
Bug with open Docker Container in Antigravity Google Antigravity bug	0	27	February 6, 2026