Request ID: f5e1cc17-cf0f-4aea-955d-743879a43484
[internal] internal error
internal error
ConnectError: [internal] internal error
at e (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.glass.main.js:20399:638436)
at async Object.addAsyncFollowupBackgroundComposer (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.glass.main.js:7466:11739)
at async k$t._sendFollowupRequest (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.glass.main.js:8899:85827)
at async k$t._submitMessage (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.glass.main.js:8899:81641)
at async k$t._submitMessageForAgent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.glass.main.js:8895:348441)
at async gmm.submitMessage (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.glass.main.js:8895:6097)
at async vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.glass.main.js:19432:79740
Local project moved off cloud, agents in local are active.
Stack (abridged): addAsyncFollowup… → _sendFollowupRequest → optimistic queue in workbench.glass.main.js
Local This PC agents still work. This appears to be a Cloud/backend failure on the follow-up path.
Steps to Reproduce
Open Cursor IDE on Windows (Glass / Agents Window).
Open an existing Cloud Agent that is ready for follow-up.
Send a short follow-up message.
Observe ConnectError [internal] internal error from addAsyncFollowup….
Retrying the same follow-up still fails.
Expected Behavior
Follow-up messages should be accepted and processed. If the backend cannot handle the follow-up, show a clear actionable error instead of a generic [internal] internal error.
Operating System
Windows 10/11
Version Information
Cursor IDE 3.21.4 (Windows x64)
OS: Windows 10
Feature: Cloud Agent follow-up via Glass / Agents Window
For AI issues: add Request ID with privacy disabled
7b18afc4-08f1-4aa3-8693-976320b6b62c
Additional Information
Please check backend logs for this Request ID. Workaround: start a new Cloud Agent instead of following up, or try cursor.com/agents.
No local project paths or agent IDs included intentionally.
Noticed it first in Projects, I kept getting internal errors.
Here’s a sample:
Request ID: 47895c2a-3278-432f-93a2-1ef14dd1fc77
[internal] internal error
internal error
ConnectError: [internal] internal error
at e (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.glass.main.js:20566:545938)
at async Object.addAsyncFollowupBackgroundComposer (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.glass.main.js:7678:11739)
at async Lvi._sendFollowupRequest (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.glass.main.js:9057:82541)
at async Lvi._submitMessage (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.glass.main.js:9057:78499)
at async Lvi._submitMessageForAgent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.glass.main.js:9053:337548)
at async bcm.submitMessage (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.glass.main.js:9053:6097)
at async vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.glass.main.js:19596:79648
When I start a new cloud agent chat, it closes the chat after a few seconds and removes it from my history. Same on the web.
In the environments list of the Cloud Agent I’m getting the following error “Failed to load environments”.
For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)
For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…
Additional Information
Add any other context about the problem here.
Does this stop you from using Cursor?
Yes - Cursor is unusable
Sometimes - I can sometimes use Cursor
No - Cursor works, but with this issue
The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!
For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)
For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…
Additional Information
Add any other context about the problem here.
Does this stop you from using Cursor?
Yes - Cursor is unusable
Sometimes - I can sometimes use Cursor
No - Cursor works, but with this issue
The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!
For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)
For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…
Additional Information
Add any other context about the problem here.
Does this stop you from using Cursor?
Yes - Cursor is unusable
Sometimes - I can sometimes use Cursor
No - Cursor works, but with this issue
The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!
Created Cloud Project does not appear in the Projects left-nav sidebar. Creation seemed to succeed (coordinator/brief started), then the Project vanished from the list. After full quit/reopen I still only see 2 Projects; the third is missing. Renaming the visible Projects in the UI immediately reverts. Local Cursor state still shows the missing Project as active (with a background-composer workspace id), so it looks like an orphan: exists in local/cloud worker state but not listed in the Projects sidebar. This makes multi-Project setups unusable.
Steps to Reproduce
In Cursor, open Projects (left nav) → New Project.
Select a private GitHub repo and create the Project (paste a short project brief / seed).
Confirm creation appears to succeed (coordinator / brief starts).
Return to the Projects list / sidebar.
Observe the new Project is missing (or appears briefly then disappears).
Fully quit Cursor and reopen; check Projects again — still missing.
Optionally: rename one of the remaining visible Projects — the name reverts immediately.
Expected Behavior
Every successfully created Cloud Project appears and stays visible in the Projects left-nav sidebar.
Rename either persists, or the UI does not offer rename if titles are server-owned / immutable.
Creating a Project must not leave an orphan that exists in local/cloud worker state but is missing from the sidebar.
Operating System
Windows 10/11
Version Information
Version: 3.20.21
VSCode/Electron commit: f09fca384ceca23f7bf21f9c23655b162641d740
OS: Windows 11 Pro (10.0.26200)
Arch: x64
For AI issues: which model did you use?
N/A — this is a Projects sidebar / Cloud Projects listing bug, not a model-output issue.
For AI issues: add Request ID with privacy disabled
N/A for the sidebar listing itself.
Related Background Agent / Project worker ID from local state (missing Project):
bc-397431a7-931d-460f-bcc5-f6c7c1e65e93
In Cursor Early Access Projects, Create Project fails repeatedly with “Couldn’t create the project. Please try again.” The UI also reports Internal Server Error. This affects the Phoenix Collective account and the project “Collective Cockpit”.
Steps to Reproduce
Open Early Access Projects and choose Create Project.
Try project name “Collective Cockpit”.
Try selecting only the PhoenixClaw01/phoenix-collective-os repository (not multi-repo and not the local D: folder).
Also try multi-selecting collective-os + local-stack, and try the single-repo path again.
Submit with model “High Fast”.
Separately, Cloud Agents Environment setup also fails for this same account.
Expected Behavior
A project should be created successfully and the selected repository/environment should be configured. Instead, every attempt fails with “Couldn’t create the project. Please try again.” and Internal Server Error.
Operating System
Windows 10/11
Version Information
Cursor Early Access Projects (current build; exact version not captured). Project: Collective Cockpit. Repository/environment: PhoenixClaw01/phoenix-collective-os; local D: folder also tested.
For AI issues: which model did you use?
High Fast
For AI issues: add Request ID with privacy disabled
f11053a0-228f-4da5-857b-5b0986ed628a
Additional Information
Account: Phoenix Collective. Profile handle is already claimed as @falkor (cursor.com/@falkor), so the short-handle namespace workaround does not apply. The failure occurs with ONLY PhoenixClaw01/phoenix-collective-os selected; it is not specific to multi-repo or the local D: folder. Multi-select collective-os + local-stack also failed, and single-repo also failed. Cloud Agents Environment setup is failing for the same account. Please investigate the Projects create endpoint and environment setup for this account.
