# WSL Issue 1.18.3 - Commands Don't Work

**URL:** <https://discuss.ai.google.dev/t/wsl-issue-1-18-3-commands-dont-work/124692>\
**Category:** Google Antigravity\
**Tags:** wsl2, bug, help\_request\
**Created:** [February 20, 2026, 1:50pm UTC](https://discuss.ai.google.dev/t/wsl-issue-1-18-3-commands-dont-work/124692 "2026-02-20T13:50:56Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![JohnBCoding](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/johnbcoding/32/31578_2.png) [@JohnBCoding](https://discuss.ai.google.dev/u/JohnBCoding)\
**Post date:** [February 20, 2026, 1:50pm UTC](https://discuss.ai.google.dev/t/wsl-issue-1-18-3-commands-dont-work/124692/1 "2026-02-20T13:50:56Z")

</div>

Anyone have this issue occurring on the newest version? Any command it tries to run it tries to append sandbox commands that seem to be MacOS only which fails in WSL. If I downgrade to the previous version its works perfectly so seems to be some configuration on the Windows/WSL branch causing this?

 ![Capture](https://d3qe71uytubmmx.cloudfront.net/original/3X/d/a/dadff1a09df7adb308c49257df720e8a139a997d.png)

---

<div class="post-metadata">

**Author:** ![JohnBCoding](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/johnbcoding/32/31578_2.png) [@JohnBCoding](https://discuss.ai.google.dev/u/JohnBCoding)\
**Post date:** [February 22, 2026, 3:46am UTC](https://discuss.ai.google.dev/t/wsl-issue-1-18-3-commands-dont-work/124692/2 "2026-02-22T03:46:24Z")

</div>

Thankfully it looks like turning off shell integration seems to fix this issue for now.

---

<div class="post-metadata">

**Author:** ![Mrinal\_Ghosh](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/mrinal_ghosh/32/32599_2.png) [@Mrinal\_Ghosh](https://discuss.ai.google.dev/u/Mrinal_Ghosh)\
**Post date:** [February 23, 2026, 6:29am UTC](https://discuss.ai.google.dev/t/wsl-issue-1-18-3-commands-dont-work/124692/3 "2026-02-23T06:29:04Z")

</div>

Hi @JohnBCoding ,

We are pleased to hear that the issue has been resolved. Thank you for sharing this update with the community. Should you encounter any further difficulties, please do not hesitate to let us know.
