Wierd output "echo 'ok enough'", "echo 'no more shell'"

[AbdelRahman_Hamed]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

GPT-5 plan execution started failing after a grep step

Steps to Reproduce

started to fail after an rg --files -g '.env*' command failing
–: line 1: rg: command not found

Expected Behavior

it should’ve reverted to a different command if “rg” fails (grep with flags/pipe with sed?)

Screenshots / Screen Recordings

Operating System

Linux

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.3.34 (user setup)
VSCode Version: 1.105.1
Commit: 643ba67cd252e2888e296dd0cf34a0c5d7625b90
Date: 2026-01-10T21:17:10.428Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

GPT-5.2 Codex

For AI issues: add Request ID with privacy disabled

58eec760-ed22-4063-acf5-2b91c367f366

Additional Information

using WLS (Debian)

Does this stop you from using Cursor

No - Cursor works, but with this issue

[deanrie]

Hey, thanks for the screenshot, it makes things clearer now.

This isn’t normal behavior. The agent got stuck in a loop running meaningless echo commands.

For now, please try:

• Start a new chat with CTRL + N
• Stop the current generation
• If you’re using GPT-5.2 Codex, try switching to Claude for now and see if the issue still happens

Also, install ripgrep in WSL with sudo apt install ripgrep. This should fix the original rg: command not found error.