⌥ + arrow no longer works

Support Bug Reports
21

is that version released?

There are currently no updates available. ← when i click check for updates

and there is no change log in Changelog | Cursor - The AI Code Editor

22

I think you need to enable early access on the beta tab in the Cursor settings.

23

I just updated to 1.5.7, but still have the same issue. Version: 1.5.7 VSCode Version: 1.99.3

1 Like
24

Which OS do you use?

25

Here are the full info:

Version: 1.5.7
VSCode Version: 1.99.3
Commit: 6aa7b3af0d578b9a3aa3ab443571e1a51ebb4e80
Date: 2025-08-27T22:43:32.248Z
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
1 Like
26

thanks for fixing this so quick!!!

27

The issue still persist for me.
I’ll mention that I experience the issue both in cursor and vscode.

It looks related to this PR in vscode: Restore alt+left/right keybinding to switch terminal pane by Tyriar · Pull Request #259332 · microsoft/vscode · GitHub

Also reported issue: `option+arrow key` inserts a letter instead of moving cursor by word · Issue #251715 · microsoft/vscode · GitHub

And in xterm.js: Jump word (option+arrow) navigation broken on mac · Issue #5389 · xtermjs/xterm.js · GitHub

Version: 1.5.7
VSCode Version: 1.99.3
Commit: 6aa7b3af0d578b9a3aa3ab443571e1a51ebb4e80
Date: 2025-08-27T22:43:32.248Z (1 day ago)
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
28

After deep dive what solve the issue for me was commenting out this line from my settings:

//  "terminal.integrated.sendKeybindingsToShell": true,
1 Like
29

Great!

For me I had to disable an additional setting relating to the terminal, reload the window before it works:

# 25/01/2023. To enable delete the last 'word' back in VSCode terminal (instead of the entire path "/abc/def")
"terminal.integrated.sendKeybindingsToShell": false,
"terminal.integrated.commandsToSkipShell": [
    "-workbench.action.terminal.sendSequence"
],
30

Hey all - noting we fixed this one in 1.5.7. Was only broken in ~1.5.5/1.5.6

31

Hey @andrewh, this bug had been fixed indeed. I definitely noticed it’s working again after upgrading Cursor when I saw you message. Unfortunately, it seems it’s broken again :frowning: I’m on Version: 1.6.23

2 Likes
32

Same - it had been working fine again but I just updated today to 1.6.23 and the bug has returned :worried:

2 Likes
33

Updated today to 1.6.26 and the bug is now re-fixed :+1:

2 Likes
34

I’m at 1.6.42 (Mac OS) and this bug is back again.

5 Likes
35

bug is still occurred at 1.6.45 (mac os/m3)

36

Still not working for me too :cry: My environment:

Version: 1.6.45
VSCode Version: 1.99.3
Commit: 3ccce8f55d8cca49f6d28b491a844c699b8719a0
Date: 2025-09-22T18:22:38.013Z
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.5.0
37

Same problem here,

Version: 1.7.12 (Universal)
VSCode Version: 1.99.3
Commit: b3f1951240d5016648330fab51192dc03e8d7050
Date: 2025-09-28T00:58:08.696Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 25.0.0
1 Like
38

Hey, thanks for the info, the team is already looking into this.

3 Likes
39

Also having the problem, although different version than davide

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
1 Like
40

Seeing the same.

Version: 1.7.22
VSCode Version: 1.99.3
Commit: 31b1fbfcec1bf758f7140645f005fc78b5df3550
Date: 2025-09-29T21:47:28.451Z
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

1 Like