Cursor IDE
doing anything in the standard Vs code terminal causes cursor to stop responding.
This bug has been around for many months
Open terminal.ls
The entire app shouldnt crash
Linux
Version: 2.0.77
N/A
N/a
you have to then kill cursor and restart
Yes - Cursor is unusable
deanrie
November 19, 2025, 10:06am
2
Hey, thanks for the report. This is a known issue, so let’s investigate it together.
Quick diagnostic steps:
Check with extensions disabled:cursor --disable-extensions
Then try using the terminal. Does it still crash?
Check with GPU acceleration disabled:cursor --disable-gpu
Clear the cache (temporary workaround):rm -rf ~/.config/Cursor/Code\ Cache ~/.config/Cursor/CachedData
Then restart Cursor.
Also, please share:
Your Linux distribution and desktop environment (Wayland or X11?)
Your default shell (bash/zsh/fish?)
The output from the Developer Tools Console (Help > Toggle Developer Tools) right before it freezes
Whether the freeze happens with a fresh Cursor profile or workspace
If none of these steps help, I’ll escalate this to the team. The --disable-gpu flag has already helped other Linux users with crash issues.
Let me know what you find.
seems to be ok without extensions
same bug
same bug
``Distributor ID: UbuntuDescription: Ubuntu 25.10Release: 25.10Codename: questing``
Its not even possible to see the developer tools console log because that crashes also
deanrie
November 21, 2025, 7:55am
4
Thanks for testing. Since the terminal works with --disable-extensions, that confirms one of your extensions is causing the issue.
To find the specific extension:
Open the Extension Manager
Disable half of your extensions, restart Cursor, and test the terminal
Repeat:
If the terminal works, the problematic extension is in the disabled half
If it still crashes, the problematic extension is in the enabled half
Keep halving the list until you find the exact extension
Good places to start:
Any Java-related extensions (Java, Debugger for Java, etc.)
Extensions that change or enhance the terminal
Shell/bash extensions
Once you find the culprit, please share the extension name so we can escalate it as a potential compatibility issue with Cursor.
Bisecting was not easily possible as it would crash before the bisect could complete.
```aleksandardev.vscode-sequence-diagrams-0.4.7aleleba.fira-code-material-icon-theme-1.0.3ambooth.git-rename-1.3.0antfu.vite-0.2.5anysphere.cursorpyright-1.0.10apollographql.vscode-apollo-2.6.3-universalarchsense.architecture-view-nestjs-0.7.0atlassian.atlascode-4.0.9-universalbierner.markdown-mermaid-1.29.0-universalbpruitt-goddard.mermaid-markdown-syntax-highlighting-1.7.4bradlc.vscode-tailwindcss-0.14.28-universalchrmarti.regex-0.5.1ckolkman.vscode-postgres-1.4.3codeandstuff.package-json-upgrade-3.2.1cweijan.dbclient-jdbc-1.4.6cweijan.vscode-redis-client-8.3.6dbaeumer.vscode-eslint-3.0.16-universaldonjayamanne.githistory-0.6.20eamodio.gitlens-17.7.1-universalesbenp.prettier-vscode-11.0.0extensions.jsongithub.vscode-github-actions-0.28.0-universalgithub.vscode-pull-request-github-0.108.0-universalgitlab.gitlab-workflow-6.57.4-universalgraphql.vscode-graphql-0.13.2graphql.vscode-graphql-execution-0.3.2graphql.vscode-graphql-syntax-1.3.8kiranshah.chatgpt-helper-4.1.0mermaidchart.vscode-mermaid-chart-2.3.0-universalmhutchie.git-graph-1.30.0mquandalle.graphql-0.1.2ms-azuretools.vscode-azurefunctions-1.19.0-universalms-azuretools.vscode-azureresourcegroups-0.11.2-universalms-azuretools.vscode-azurestorage-0.16.5ms-azuretools.vscode-cosmosdb-0.24.1ms-azuretools.vscode-cosmosdb-0.26.0ms-azuretools.vscode-docker-2.0.0ms-dotnettools.csdevkit-1.16.6-linux-x64ms-dotnettools.csharp-2.63.32-linux-x64ms-dotnettools.vscode-dotnet-runtime-2.3.6-universalms-dotnettools.vscodeintellicode-csharp-2.2.3-linux-x64ms-mssql.mssql-1.31.1ms-mssql.sql-bindings-vscode-0.4.1ms-playwright.playwright-1.1.15ms-python.debugpy-2025.14.1-linux-x64ms-python.python-2025.6.1-linux-x64ms-python.vscode-pylance-2024.8.1ms-vscode-remote.remote-containers-0.394.0ms-vscode-remote.remote-ssh-0.113.1ms-vscode-remote.remote-ssh-edit-0.87.0ms-vscode-remote.remote-wsl-0.81.8ms-vscode.azure-account-0.13.0ms-vscode.remote-explorer-0.5.0ms-vscode.remote-server-1.5.2ms-vsliveshare.vsliveshare-1.0.5948mylesmurphy.prettify-ts-0.3.9naumovs.color-highlight-2.8.0nicoespeon.abracadabra-9.7.0-universalplanbcoding.vscode-react-refactor-1.1.3pmneo.tsimporter-2.0.1postman.postman-for-vscode-1.18.0-universalredhat.vscode-yaml-1.19.1-universalritwickdey.liveserver-5.7.9rvest.vs-code-prettier-eslint-6.0.0sburg.vscode-javascript-booster-14.0.1seatonjiang.gitmoji-vscode-2025.11.13-universalshd101wyy.markdown-preview-enhanced-0.8.20-universalsleistner.vscode-fileutils-3.10.3streetsidesoftware.code-spell-checker-4.2.6-universalstreetsidesoftware.code-spell-checker-cspell-bundled-dictionaries-2.0.12-universalstringham.move-ts-1.12.0vitest.explorer-1.32.1-universalvue.volar-3.1.5-universalwaderyan.gitblame-11.2.0-universalyoavbls.pretty-ts-errors-0.6.3-universalzainchen.json-2.0.2zhuangtongfa.material-theme-3.19.0```
deanrie
November 30, 2025, 9:46am
7
Thanks for the detailed report and the list of extensions. The problem is definitely caused by one of the extensions since the terminal works without them.
Quick check:
Try disabling extensions related to terminal/shell: Remote-SSH, Remote-Containers, Remote-WSL, GitBash, etc.
Or disable them one by one from your list and test the terminal
Suspicious candidates from your list:
ms-vscode-remote.* (Remote extensions)
Any extensions for shell/bash
When you find the problematic extension, please share its name, and I’ll pass it to the engineers to check compatibility with Cursor.
