Thanks for reporting a bug you have found in Cursor!
Please add the following info to help us diagnose your issue:
Check the forum to ensure the issue hasn’t been reported already
Provide a clear description of the bug
After the latest cursor update, I have been unable to use the latex workshop extension. Please see the issue that I filed on the latex workshop GitHub for details. The developer of latex workshop; took a look at this in
opened 12:31AM - 02 Apr 25 UTC
closed 01:48AM - 02 Apr 25 UTC
> _Please fill the following fields with a star (*) and provide as much related … information as possible._
## Pre-checks*
> _Please change the following `[ ]` to `[x]` for confirmation._
- [x] The issue has not been reported in this repository.
- [x] The issue remains after disabling all other extensions and restarting Visual Studio Code.
- [x] The [FAQ](https://github.com/James-Yu/LaTeX-Workshop/wiki/FAQ) cannot address the issue.
- [x] The issue is not related to compiling a document, or the document can be successfully compiled in the OS terminal but not in Visual Studio Code with this extension.
## Environment*
> _Please write exact version numbers instead of descriptors such as `latest`._
- Operating System: MacOS 15.3.1
- Visual Studio Code Version:
Version: 0.48.6
VSCode Version: 1.96.2
Commit: 1649e229afdef8fd1d18ea173f063563f1e722e0
Date: 2025-03-31T04:59:09.581Z
Electron: 34.3.4
Chromium: 132.0.6834.210
Node.js: 20.18.3
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.3.0
- LaTeX Workshop Version: 10.9.0
- TeX Distribution Version: TeX Live 2024)
> _Please list the environment and version number if you are using VSCodium, Snap or Flatpack versions of Visual Studio Code, and/or Visual Studio Code Remote Containers/SSH/WSL._
- I am using Cursor, which is just a fork of VSCode, whose version is given above.
## The Issue*
> _Please briefly describe the issue you come across._
- When I have the latex workshop extension enabled, I am not able to use other extensions such as Talon or Cursorless. Everything was working just fine until today, when I updated my IDE. In particular, the TeX sidebar is blank, simply reading, There is no data provider registered that can provide view data. When I try to build with a recipe by pressing the Green play button on top of my .tex file, i get command 'latex-workshop.build' not found. See sc.

-
### Reproduction Steps
> _Please list out the steps to reproduce your bug. Include relevant environmental variables or any other configuration._
1. Using the Talon and Cursorless extensions with Latex Workshop.
2.
3.
### Expected Behavior
> _What were you expecting to see? Include any relevant examples or documentation links._
-
-
## Logs
### LaTeX Workshop Output*
> _Please paste the whole log messages below, not parts of ones. The log should start with `New log placeholder %WS1% registered`._
Does not show up now, so nothing to include.
### Developer Tools Console
> _Please paste the whole log messages below, not parts of ones. This console logs can sometimes be very important in many cases. To access the log, click `Help` -> `Toggle Developer Tools` -> `Console`._
```
workbench.desktop.main.js:2961 Overwriting grammar scope name to file mapping for scope source.cmake.
Old grammar file: file:///Users/patrykkozlowski/.cursor/extensions/ms-vscode.cmake-tools-1.20.53/syntaxes/CMake.tmLanguage.
New grammar file: file:///Users/patrykkozlowski/.cursor/extensions/twxs.cmake-0.0.17/syntaxes/CMake.tmLanguage
register @ workbench.desktop.main.js:2961
workbench.desktop.main.js:2961 Overwriting grammar scope name to file mapping for scope source.cmakecache.
Old grammar file: file:///Users/patrykkozlowski/.cursor/extensions/ms-vscode.cmake-tools-1.20.53/syntaxes/CMakeCache.tmLanguage.
New grammar file: file:///Users/patrykkozlowski/.cursor/extensions/twxs.cmake-0.0.17/syntaxes/CMakeCache.tmLanguage
register @ workbench.desktop.main.js:2961
workbench.desktop.main.js:2370 [Extension Host] (node:50245) ExperimentalWarning: Use `importAttributes` instead of `importAssertions`
(Use `Cursor Helper (Plugin) --trace-warnings ...` to show where the warning was created)
xkr @ workbench.desktop.main.js:2370
textMateTokenizationWorker.workerMain.js:31 Overwriting grammar scope name to file mapping for scope source.cmake.
Old grammar file: file:///Users/patrykkozlowski/.cursor/extensions/ms-vscode.cmake-tools-1.20.53/syntaxes/CMake.tmLanguage.
New grammar file: file:///Users/patrykkozlowski/.cursor/extensions/twxs.cmake-0.0.17/syntaxes/CMake.tmLanguage
register @ textMateTokenizationWorker.workerMain.js:31
textMateTokenizationWorker.workerMain.js:31 Overwriting grammar scope name to file mapping for scope source.cmakecache.
Old grammar file: file:///Users/patrykkozlowski/.cursor/extensions/ms-vscode.cmake-tools-1.20.53/syntaxes/CMakeCache.tmLanguage.
New grammar file: file:///Users/patrykkozlowski/.cursor/extensions/twxs.cmake-0.0.17/syntaxes/CMakeCache.tmLanguage
register @ textMateTokenizationWorker.workerMain.js:31
workbench.desktop.main.js:4921 Extension Host
workbench.desktop.main.js:931 Error checking file existence: Error: Unable to resolve filesystem provider with relative file path 'cursor.aisettings:cursor/aisettings'
(anonymous) @ workbench.desktop.main.js:931
workbench.desktop.main.js:931 Error checking file existence: Error: Unable to resolve filesystem provider with relative file path 'cursor.aisettings:cursor/aisettings'
(anonymous) @ workbench.desktop.main.js:931
workbench.desktop.main.js:931 Error checking file existence: Error: Unable to resolve filesystem provider with relative file path 'cursor.aisettings:cursor/aisettings'
(anonymous) @ workbench.desktop.main.js:931
workbench.desktop.main.js:4921 Extension Host
workbench.desktop.main.js:4917 Extension host (LocalProcess pid: 50245) terminated unexpectedly. Code: 5, Signal: unknown
Bb @ workbench.desktop.main.js:4917
vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/services/extensions/worker/webWorkerExtensionHostIframe.html?&vscodeWebWorkerExtHostId=5c668b8a-e004-4049-b920-10071a579cc8:1 An iframe which has both allow-scripts and allow-same-origin for its sandbox attribute can escape its sandboxing.
www.vscode-unpkg.net/_gallery/anysphere/pyright/latest:1
Failed to load resource: the server responded with a status of 404 ()
workbench.desktop.main.js:2370 [Extension Host] (node:50295) ExperimentalWarning: Use `importAttributes` instead of `importAssertions`
(Use `Cursor Helper (Plugin) --trace-warnings ...` to show where the warning was created)
xkr @ workbench.desktop.main.js:2370
workbench.desktop.main.js:4921 Extension Host
workbench.desktop.main.js:4921 Extension Host
workbench.desktop.main.js:4917 Extension host (LocalProcess pid: 50295) terminated unexpectedly. Code: 5, Signal: unknown
Bb @ workbench.desktop.main.js:4917
vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/services/extensions/worker/webWorkerExtensionHostIframe.html?&vscodeWebWorkerExtHostId=75b60e02-1c5c-4cf0-bd8e-555f86ecdf9b:1 An iframe which has both allow-scripts and allow-same-origin for its sandbox attribute can escape its sandboxing.
workbench.desktop.main.js:2370 [Extension Host] (node:50386) ExperimentalWarning: Use `importAttributes` instead of `importAssertions`
(Use `Cursor Helper (Plugin) --trace-warnings ...` to show where the warning was created)
xkr @ workbench.desktop.main.js:2370
workbench.desktop.main.js:4921 Extension Host
workbench.desktop.main.js:4921 Extension Host
workbench.desktop.main.js:4917 Extension host (LocalProcess pid: 50386) terminated unexpectedly. Code: 5, Signal: unknown
Bb @ workbench.desktop.main.js:4917
workbench.desktop.main.js:4847 Extension host terminated unexpectedly 3 times within the last 5 minutes.
c @ workbench.desktop.main.js:4847
workbench.desktop.main.js:5242 An iframe which has both allow-scripts and allow-same-origin for its sandbox attribute can escape its sandboxing.
mountTo @ workbench.desktop.main.js:5242
workbench.desktop.main.js:635 Error: No Connect transport provider registered.
at sss.transport (workbench.desktop.main.js:98:117518)
at async sf.createSingleServer (workbench.desktop.main.js:98:118220)
c @ workbench.desktop.main.js:635
workbench.desktop.main.js:635 Error: No Connect transport provider registered.
at sss.transport (workbench.desktop.main.js:98:117518)
at async sf.createSingleServer (workbench.desktop.main.js:98:118220)
c @ workbench.desktop.main.js:635
workbench.desktop.main.js:635 Error: No Connect transport provider registered.
at sss.transport (workbench.desktop.main.js:98:117518)
at async sf.createSingleServer (workbench.desktop.main.js:98:118220)
c @ workbench.desktop.main.js:635
workbench.desktop.main.js:635 Error: No Connect transport provider registered.
at sss.transport (workbench.desktop.main.js:98:117518)
at async sf.createSingleServer (workbench.desktop.main.js:98:118220)
maybeRefreshConfig @ workbench.desktop.main.js:635
workbench.desktop.main.js:593 Error refreshing default models: Error: No Connect transport provider registered.
at sss.transport (workbench.desktop.main.js:98:117518)
at async sf.createSingleServer (workbench.desktop.main.js:98:118220)
refreshDefaultModels @ workbench.desktop.main.js:593
workbench.desktop.main.js:4939 Error refreshing background composers Error: No Connect transport provider registered.
at sss.transport (workbench.desktop.main.js:98:117518)
at async sf.createSingleServer (workbench.desktop.main.js:98:118220)
at async sf.get (workbench.desktop.main.js:98:118034)
at async Oki.refreshBackgroundComposers (workbench.desktop.main.js:4939:7845)
(anonymous) @ workbench.desktop.main.js:4939
Error: No Connect transport provider registered.
at sss.transport (workbench.desktop.main.js:98:117518)
at async sf.createSingleServer (workbench.desktop.main.js:98:118220)
at async sf.get (workbench.desktop.main.js:98:118034)
at async l3t.forceRefreshServerConfig (workbench.desktop.main.js:593:32209)
workbench.desktop.main.js:593 Error refreshing default models: Error: No Connect transport provider registered.
at sss.transport (workbench.desktop.main.js:98:117518)
at async sf.createSingleServer (workbench.desktop.main.js:98:118220)
refreshDefaultModels @ workbench.desktop.main.js:593
Error: No Connect transport provider registered.
at sss.transport (workbench.desktop.main.js:98:117518)
at async sf.createSingleServer (workbench.desktop.main.js:98:118220)
at async sf.get (workbench.desktop.main.js:98:118034)
at async l3t.forceRefreshServerConfig (workbench.desktop.main.js:593:32209)
workbench.desktop.main.js:635 Error: No Connect transport provider registered.
at sss.transport (workbench.desktop.main.js:98:117518)
at async sf.createSingleServer (workbench.desktop.main.js:98:118220)
c @ workbench.desktop.main.js:635
workbench.desktop.main.js:593 Error refreshing default models: Error: No Connect transport provider registered.
at sss.transport (workbench.desktop.main.js:98:117518)
at async sf.createSingleServer (workbench.desktop.main.js:98:118220)
refreshDefaultModels @ workbench.desktop.main.js:593
await in refreshDefaultModels
(anonymous) @ workbench.desktop.main.js:4931
withSemaphore @ workbench.desktop.main.js:892
await in withSemaphore
(anonymous) @ workbench.desktop.main.js:4931
Error: No Connect transport provider registered.
at sss.transport (workbench.desktop.main.js:98:117518)
at async sf.createSingleServer (workbench.desktop.main.js:98:118220)
at async sf.get (workbench.desktop.main.js:98:118034)
at async l3t.forceRefreshServerConfig (workbench.desktop.main.js:593:32209)
Promise.catch
(anonymous) @ workbench.desktop.main.js:593
setTimeout
e.setTimeout @ workbench.desktop.main.js:2418
r @ workbench.desktop.main.js:593
(anonymous) @ workbench.desktop.main.js:593
setTimeout
e.setTimeout @ workbench.desktop.main.js:2418
r @ workbench.desktop.main.js:593
(anonymous) @ workbench.desktop.main.js:593
setTimeout
e.setTimeout @ workbench.desktop.main.js:2418
r @ workbench.desktop.main.js:593
(anonymous) @ workbench.desktop.main.js:593
setTimeout
e.setTimeout @ workbench.desktop.main.js:2418
r @ workbench.desktop.main.js:593
(anonymous) @ workbench.desktop.main.js:593
setTimeout
e.setTimeout @ workbench.desktop.main.js:2418
r @ workbench.desktop.main.js:593
(anonymous) @ workbench.desktop.main.js:593
setTimeout
e.setTimeout @ workbench.desktop.main.js:2418
r @ workbench.desktop.main.js:593
(anonymous) @ workbench.desktop.main.js:593
setTimeout
e.setTimeout @ workbench.desktop.main.js:2418
r @ workbench.desktop.main.js:593
(anonymous) @ workbench.desktop.main.js:593
setTimeout
e.setTimeout @ workbench.desktop.main.js:2418
r @ workbench.desktop.main.js:593
(anonymous) @ workbench.desktop.main.js:593
setTimeout
e.setTimeout @ workbench.desktop.main.js:2418
r @ workbench.desktop.main.js:593
(anonymous) @ workbench.desktop.main.js:593
[exthost.log](https://github.com/user-attachments/files/19559441/exthost.log)
[exthost.log](https://github.com/user-attachments/files/19559454/exthost.log)
```
## Anything Else?
> _Add any other context about the problem below._
-
, and he concluded that “Please report to cursor. Their update breaks something internal.”, so that is why I am asking here. Could somebody please take a look?
Explain how to reproduce the bug (if known)
I get this bug in VSCode as well now that I updated Cursor.
Attach screenshots or recordings (e.g., .jpg
, .png
, .mp4
).
The relevant developer tools console log as well as a sc is included in my filed issue.
Tell us your operating system and your Cursor version (e.g., Windows, 0.x.x
).
Operating System: MacOS 15.3.1
Visual Studio Code Version:
Version: 0.48.6
VSCode Version: 1.96.2
Commit: 1649e229afdef8fd1d18ea173f063563f1e722e0
Date: 2025-03-31T04:59:09.581Z
Electron: 34.3.4
Chromium: 132.0.6834.210
Node.js: 20.18.3
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.3.0
LaTeX Workshop Version: 10.9.0
TeX Distribution Version: TeX Live 2024)
Tell us if the issue stops you from using Cursor.
+1 on this. I am having the same issues after the last update. Problem is that, while fully functioning, I can’t see the latex-workshop extension in the extension bar anymore ( )