Terminal IntelliSense broken: vscode.terminal-suggest fails with "Module not found in bundle: ./completions/upstream/ls"

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Description

Terminal IntelliSense (command autocomplete in the integrated terminal) stopped working. When typing commands like git or cd , no suggestions appear.

The built-in extension vscode.terminal-suggest fails to activate. Extension Host logs show:

Steps to Reproduce

  1. Open Cursor on Windows
  2. Open the integrated terminal (PowerShell)
  3. Ensure terminal.integrated.suggest.enabled is true
  4. Type git or press Tab while typing a command
  5. Open Developer: Show LogsExtension Host
  6. Observe the activation failure for vscode.terminal-suggest

Expected Behavior

Terminal shows command/flag/path suggestions while typing.

Operating System

Windows 10/11

Version Information

Cursor version: 3.10.17
Extension: vscode.terminal-suggest v1.0.1 (built-in)

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, thanks for the detailed report. The logs and steps really helped.

Confirmed: this is a regression in 3.10 and I can reproduce it. The built-in extension vscode.terminal-suggest crashes on activation, so terminal suggestions disappear. This affects not only Windows and PowerShell, but all platforms on this build. I’ve filed an internal report, but I can’t share a fix timeline yet.

Until it’s fixed, the only workaround is to roll back to a build before 3.10 if terminal suggestions are critical for you. I’ll post an update in this thread as soon as I have one.

Hey there!

Thanks again for the report. This should be fixed in the next cut of 3.10 as well as 3.11.

Still appears broken in 3.11.19 on Mac.

@Brian_McNaboe On my side (Mac, 3.11.19) the extension activates and autocomplete works fine.

  • Have you made sure that terminal.integrated.suggest.enabled is set to true in your VSCode Settings?
  • Do you see any failures in the Extension Host logs (Cmd + Shift + P > Developer: Show Logs → Extension Host

Hi @Colin , thanks for the response.

Yes, I can confirm the VSCode setting.

Here’s the log output:

2026-07-13 13:39:39.047 [info] ExtensionService#_doActivateExtension vscode.terminal-suggest, startup: false, activationEvent: 'onTerminalCompletionsRequested'
2026-07-13 13:39:39.057 [info] Extension activation failure: vscode.terminal-suggest
2026-07-13 13:39:39.057 [error] Activating extension vscode.terminal-suggest failed due to an error:
2026-07-13 13:39:39.057 [error] Error: Module not found in bundle: ./completions/upstream/ls

Thanks @Brian_McNaboe

This fix seems to have made it into 3.10, and the upcoming 3.12, but not 3.11. :frowning: This should get fixed with our next release, apologies.

No worries. Thanks, Colin.

It has been fixed in version 3.12.0, thank you!