# \[Bug / Question\] WSL UNC paths fail with %5C encoding error in Antigravity 2.3.1 — Any workaround?

**URL:** <https://discuss.ai.google.dev/t/bug-question-wsl-unc-paths-fail-with-5c-encoding-error-in-antigravity-2-3-1-any-workaround/175960>\
**Category:** Google Antigravity\
**Tags:** wsl, wsl2, bug\
**Created:** [July 24, 2026, 3:03am UTC](https://discuss.ai.google.dev/t/bug-question-wsl-unc-paths-fail-with-5c-encoding-error-in-antigravity-2-3-1-any-workaround/175960 "2026-07-24T03:03:59Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![imalexgo](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/imalexgo/32/138582_2.png) [@imalexgo](https://discuss.ai.google.dev/u/imalexgo)\
**Post date:** [July 24, 2026, 3:03am UTC](https://discuss.ai.google.dev/t/bug-question-wsl-unc-paths-fail-with-5c-encoding-error-in-antigravity-2-3-1-any-workaround/175960/1 "2026-07-24T03:03:59Z")

</div>

### **Issue:**

Opening project folders directly via standard WSL UNC paths (e.g., `\\wsl.localhost\Ubuntu-26.04\home\...`) fails with a `Missing Folder` error.

Antigravity URL-encodes the backslashes `\` into `%5C` (resulting in `%5C%5Cwsl.localhost%5CUbuntu...`), which prevents the app from locating the folder.

### **Question:**

Has anyone found a working workaround to open and work on WSL projects in version 2.3.1 without triggering this URL-encoding issue?

 ![Снимок экрана 2026-07-23 162544](https://d3qe71uytubmmx.cloudfront.net/original/3X/6/2/6285ad70f9ef3ae934b5a3861958e959d15b73df.png)

---

<div class="post-metadata">

**Author:** ![Joe\_Cole](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/joe_cole/32/139205_2.png) [@Joe\_Cole](https://discuss.ai.google.dev/u/Joe_Cole)\
**Post date:** [July 27, 2026, 12:29pm UTC](https://discuss.ai.google.dev/t/bug-question-wsl-unc-paths-fail-with-5c-encoding-error-in-antigravity-2-3-1-any-workaround/175960/2 "2026-07-27T12:29:58Z")

</div>

I have the same issue.

I was able to at least use WSL as a working directory by first adding a Windows directory as the only project folder, then adding the WSL directory, and finally removing the Windows directory.

However, while AG can work on the files normally, it cannot show them in the app. So Implementation Plans, linked files, etc all do not display in the app. Quite annoying and, frankly unusable and unacceptable, particularly when both Claude Code and Codex FLAWLESSLY set up projects on the first attempt, with ZERO user interaction.

---

<div class="post-metadata">

**Author:** ![Rebbanpalli\_Naveen](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/rebbanpalli_naveen/32/120945_2.png) [@Rebbanpalli\_Naveen](https://discuss.ai.google.dev/u/Rebbanpalli_Naveen)\
**Post date:** [September 23, 2026, 8:29pm UTC](https://discuss.ai.google.dev/t/bug-question-wsl-unc-paths-fail-with-5c-encoding-error-in-antigravity-2-3-1-any-workaround/175960/3 "2026-09-23T20:29:59Z")

</div>

Hi @imalexgo and @Joe_Cole ,

To work on WSL2 projects without triggering `%5C` path encoding errors (and with full support for Implementation Plans and file previews), please follow the below steps:

1. **\*\*Update to the Latest Release (`v2.15.1`)\*\***:

\* Update your desktop application from `v2.3.1` to the latest **\*\*Antigravity (`v2.15.1`)\*\*** release from [[https://antigravity.google/download\](https://antigravity.google/download%5C)]([Google Antigravity - Download](https://antigravity.google/download)).  
2. **Use the Antigravity 2.0 UI with WSL2 via [Remote Control](https://antigravity.google/docs/remote-control/) (Recommended for the 2.0 UI)**:

- Install the Linux **Antigravity CLI (`agy`)** directly inside your Ubuntu WSL2 distribution ([CLI Installation Guide](https://antigravity.google/docs/cli/install/)) and start a session with Remote Control enabled:

```bash
agy --remote-control

```

_(Or run `agy remote-control start` inside WSL2 to run a persistent headless background daemon)._
- Open the printed session URL—or navigate to the [Antigravity Remote Control Dashboard](https://antigravity.google.com) signed into the same Google Account—to interact with your WSL2 instance using the **Antigravity 2.0 desktop UI** in your browser. Because the agent runs natively inside Linux (`/home/...`), you have full access to view active conversations, start new agent tasks, review Implementation Plans, and inspect artifacts with zero `\\wsl.localhost` `%5C` encoding issues.

1. **Antigravity for IDEs ([IDE Extensions](https://antigravity.google/docs/ide/extensions/)) or [Antigravity IDE](https://antigravity.google/docs/ide/overview/)**:
  - If you prefer working inside an editor connected to your WSL2 environment, you can use the official [Antigravity IDE Extensions](https://antigravity.google/docs/ide/extensions/) (such as for VS Code with Remote - WSL) or the dedicated [Antigravity IDE](https://antigravity.google/download).

Please let us know if the issue still persists.