# Agent not executing commands in WSL2 **URL:** \ **Category:** Bug Reports\ **Created:** [June 7, 2025, 2:49pm UTC](https://forum.cursor.com/t/agent-not-executing-commands-in-wsl2/101445 "2025-06-07T14:49:21Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![abhishekraok](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/abhishekraok/32/61877_2.png) [@abhishekraok](https://forum.cursor.com/u/abhishekraok)\ **Post date:** [June 7, 2025, 2:49pm UTC](https://forum.cursor.com/t/agent-not-executing-commands-in-wsl2/101445/1 "2025-06-07T14:49:22Z")
### Describe the Bug Hi, I’m using Cursor (1.0.0) on Windows 11 and WSL2. When I run the agent, it can edit files and run other tools, but for executing commands in terminal (e.g. running tests) it gets stuck. If I send it to background then it is able to execute in the terminal, but the agent itself doesn’t see the output. I have to inform the agent every time if the command was successfully executed. ### Steps to Reproduce Download a python pytest repo on Windows 11 WSL2, ask agent to run tests. ### Expected Behavior Command actually executing in the agent’s windows. ### Operating System Windows 10/11 ### Current Cursor Version (Menu → About Cursor → Copy) Version: 1.0.0 (user setup) VSCode Version: 1.96.2 Commit: 53b99ce608cba35127ae3a050c1738a959750860 Date: 2025-06-04T19:44:25.253Z Electron: 34.5.1 Chromium: 132.0.6834.210 Node.js: 20.19.0 V8: 13.2.152.41-electron.0 OS: Windows\_NT x64 10.0.26100 ### Does this stop you from using Cursor No - Cursor works, but with this issue ---
**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\ **Post date:** [July 7, 2025, 2:49pm UTC](https://forum.cursor.com/t/agent-not-executing-commands-in-wsl2/101445/3 "2025-07-07T14:49:50Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.