Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
Cursor Grok causes major issues in production. It creates stubs and workarounds, complicating everything.
Essentially, it behaves deceptively, and its code cannot be trusted.
Composer 2.5 doesn’t do this, and neither does Opus 5.
I’ve built over 30 projects of varying complexity using Cursor. Problems started arising with more complex tasks after the introduction of Cursor Grok.
Please keep developing Composer… it’s the best workhorse, proven across a multitude of tasks.
I use Opus 5 for major debugging and final verification.
Steps to Reproduce
Try to build complex project with UI and Python with Composer and Grok.
Operating System
Windows 10/11
Version Information
Version: 3.21.16 (user setup)
VS Code Extension API: 1.128.0
Commit: 8ae78e8eee1e63479c7e0504b664bc0a80c68000
Date: 2026-09-19T06:43:22.276Z
Layout: IDE
Build Type: Stable
Release Track: Default
Electron: 42.10.0
Chromium: 148.0.7778.280
Node.js: 24.18.1
V8: 14.8.178.38-electron.0
xterm.js: 6.1.0-beta.291
OS: Windows_NT x64 10.0.26200
Does this stop you from using Cursor
No - Cursor works, but with this issue