Resolving WSL Friction with Google Antigravity: the Agy 2.0 and Agy IDE Edition

DEV Community

unset PROMPT_COMMAND # exit early, without running the rest of .bashrc, e.g. bypassing oh-my-bash return fi # The REST of your .bashrc # E.g. export OSH='/home/dazbo/.oh-my-bash'

Okay, let’s restart Agy and see if it has worked...

Prompted to allow — good start!

It created a script, executed it, injected interactive responses to the script, and completed!

Interactive scripts now work

Woop!

Browser Agent is Broken

The browser agent is the thing that allows you to launch a browser from your chat, and then navigate. It can also take screenshots or even record a video of the session.

But... It doesn’t work in WSL out-of-the-box, of course.

I test it with a prompt like this: "Use the browser agent to navigate dazbo.co.uk"

Agy fails, and gives me a response like this.

Chrome DevTools Protocol errors

The Fix

This is super-easy to fix!

We just need to enable mirroring mode in our WSL config!

In Windows, we just need to edit our \.wslconfig file (or create it, if it doesn’t yet exist):

notepad %userprofile%\.wslconfig

Just make sure the file has this block:

[wsl2]
networkingMode=mirrored

Then shutdown and restart WSL, from your Windows Command Prompt or Powershell:

wsl--shutdown# Wait a few secondswsl

Now we restart Agy, and let’s see what happens...

[フレーム]

How Does It Work?

By default, WSL2 uses a Network Address Translation (NAT) architecture, which essentially places your Linux environment behind a virtual router on a separate network isolated from Windows. When Agy triggers its browser agent, it spins up a browser instance on Windows and attempts to talk to it via the Chrome DevTools Protocol (CDP). In NAT mode, that connection slams straight into a networking wall because your Linux-based Agy harness can’t seamlessly see or route traffic to Windows localhost ports (like Chrome’s default debug port 9222).

Switching your networking mode to mirrored solves this. Instead of treating Linux as a detached VM on a virtual router, Windows literally mirrors its exact network interfaces directly into WSL2. This completely removes the network isolation barrier. Now, localhost means the exact same thing to both Windows and Linux, allowing Agy in WSL to hook straight into Chrome's remote debugging interface on Windows with zero port-forwarding friction, and no firewall headaches.

That’s It

Hope this has saved you some bother.

Until next time!

You Know What To Do!

Please share this with anyone who you think will be interested. It might help them, and it really helps me!
Please interact or leave a comment 💬.