Bug Report: Overleaf Workshop Plugin Stuck on “Generating”
Description
When using the Overleaf Workshop plugin (Login with Cookie) in Cursor version 0.47.5, the Cursor tab gets stuck on “Generating” indefinitely and becomes unresponsive for all edit, ask, and agent modes. Doing inline Edit (CMD+K) is fine, but Edit in the separate Cursor tab got stuck on “Generating” indefinitely.
This issue was not present in version 0.45, where the plugin worked fine.
Not help
Open a new Chat
Restart Cursor
Reboot computer
Reinstall Cursor (0.47.5)
Load historical chats
Open a new window and remove/add the workspace again
Steps to Reproduce
Install Cursor version 0.47.5.
Install the Overleaf Workshop plugin.
Try to use the plugin—it will get stuck on “Generating” and never complete.
Expected Behavior
The Overleaf Workshop plugin should generate results normally without getting stuck, as it did in version 0.45.
2025-03-17 10:13:43.025 [info] Not indexing because user does not want to index this workspace.
2025-03-17 10:13:47.407 [info] Creating Indexing Repo client: https://repo42.cursor.sh
2025-03-17 10:13:47.407 [info] Creating repo client with backend url: https://repo42.cursor.sh
2025-03-17 10:13:47.407 [error] Git command failed: git config --get remote.origin.url A system error occurred (spawn /bin/sh ENOENT)
2025-03-17 10:13:47.407 [error] Error getting repo info: A system error occurred (spawn /bin/sh ENOENT)
2025-03-17 10:13:47.407 [error] Error: spawn /bin/sh ENOENT
at ChildProcess._handle.onexit (node:internal/child_process:285:19)
at onErrorNT (node:internal/child_process:483:16)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
2025-03-17 10:13:47.642 [info] InternalRepoInfo constructor with preferredEmbeddingModel 0
2025-03-17 10:13:49.438 [info] Creating Indexing Repo client: https://repo42.cursor.sh
2025-03-17 10:13:49.438 [info] Creating repo client with backend url: https://repo42.cursor.sh
2025-03-17 10:13:49.438 [info] InternalRepoInfo constructor with preferredEmbeddingModel 0
System Information
Cursor Version: 0.47.5
VSCode Version: 1.96.2
Commit: 53d6da1322f934a1058e7569ee0847b24879d180
Date: 2025-03-14T21:41:01.221Z
Electron: 32.2.6
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: macOS (Darwin arm64 24.3.0)
Impact
This issue prevents effective usage of Cursor for writing reports and research papers, making it a critical problem for scientists and researchers who rely on Overleaf integration.
Please investigate this issue and provide a fix. Thank you!
Same problem here, stuck on “Generating” since 0.47.5!!
But no “Overleaf” plugin installed
I have the “Remote - SSH” and “Remote Explorer” plugins though
OK, now I perceived that this problem of not generating only happens on windows that use SSH. Generating on windows with local codebases work.
Yours seems related to my issue. I can also generate using the local codebase, but when switching to a remote service whether via SSH or login with a cookie (Overleaf Workshop uses login with a cookie), it just gets stuck. This worked fine in 0.45.17, so it’s pretty clear the issue is with the new Cursor version, not the plugins. It makes no sense to say both SSH and Overleaf plugins need fixes when Cursor should be the one ensuring compatibility.
Same issue. I am using Cursor + Overleaf workflow extension but in the chat it is stuck in “Generating” and also I do not get text completion in the .tex file as well.
I am encountering the same issue. I am on Cursor version 0.47.8
However, for me cursor tab and agent works fine on other ssh hosts but not in Overleaf Workshop document.
I tried both 0.46, 0.47 with overleaf plug in, and both of them cannot generate the text.
0.45 has no issue. So, I guess the temporal solution would be downgrading it as for now.
Hi @danperks or any official developers or community members,
We truly value Cursor and rely on it heavily, especially as AI researchers working across platforms like Overleaf. However, it is extremely disappointing to see obvious, long-standing bugs that have been widely reported remain unresolved, with no acknowledgement or updates from the team.
This silence is frustrating. If these issues are being worked on, please let us know. If not, please be transparent. We are not here to criticize. We want Cursor to thrive, but ignoring key issues faced by core users is not acceptable.
Please take this seriously and let the community know where things stand.