Still facing the problem.
Version: 1.7.17
VSCode Version: 1.99.3
Commit: 34881053400013f38e2354f1479c88c9067039a0
Date: 2025-09-29T03:10:26.099Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.6.0
Using the following zshrc resolved the issue for me without changing the Cursor settings (v1.7.17 Cursor, 1.99.3 VSCode)
bindkey '^[[1;3C' forward-word
bindkey '^[[1;3D' backward-word
Thanks Adams! This totally works, at least until Cursor developers try to fix the bug
Dear developers, I’m still facing the issue. Since I updated to broken version 4 more updates released, still no fix.
```
Version: 1.7.25 (Universal)
VSCode Version: 1.99.3
Commit: 429604585b94ab2b96a4dabff4660f41d5b7fb80
Date: 2025-09-30T15:26:29.622Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.6.0
```
Looking at this threat it seems like issue was introduced and fixed multiple times.
Do you mind fixing it once and for all and doing some testing (automated tests, manual testing), so it’s not introduced again?
This is really annoying, I’ve never seen similar issue appearing in VS Code.
With all the respect, I don’t want to search for workarounds to fix basic functionality which works in every other app.