A bug in ubuntu terminal

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Hello everyone, my agent can’t execute command in terminal properly. I have been developing a GoLang project in wsl-ubuntu-24.04. However, after Cursor pushed a new update the day before yesterday, my project suddenly stopped being able to automatically execute commands in the terminal properly.

As shown in the image , cd → <d , the command my GPT-5 wants to execute:

cd /root/project/quittr_backend_gin && go build ./cmd/api

is automatically changed to:

<d /root/project/quittr_backend_gin && go build ./cmd/api

Then the agent gets permanently stuck. Switching the model to Claude didn’t change anything. It’s very strange—this bug only appeared this week. Does anyone know what the issue might be?

Steps to Reproduce

Run cursor IDE in wsl-ubuntu-24.04’s terminal. Ask model to execute terminal command.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.5.11 (user setup)
VSCode Version: 1.99.3
Commit: 2f2737de9aa376933d975ae30290447c910fdf40
Date: 2025-09-05T03:48:32.332Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.26100

For AI issues: which model did you use?

GPT-5 , Claude

Does this stop you from using Cursor

Yes - Cursor is unusable

Hey, thanks for the report. Could you try creating a new chat? Also, could you share the request ID? First, you’ll need to disable privacy mode.

Hi, sorry to report this bug. I tried multiple new chats, rebooted my machine, and reinstalled Cursor. Eventually, I resolved the issue by reinstalling WSL2. Although it still maps curl -s to <url -s, the agent no longer gets stuck constantly, and I can now use my agent functionality normally. Since I am using a Chinese input method, this seems more like a display issue caused by the input method. If anyone else encounters the same problem as me, please contact me—I can try to help reproduce it. For now, this issue no longer affects my use of the agent.

Finally , even it still shows curl → <url , but it’s not stuck anymore . Best wishes to your team.