Bug report, connection error

Support Bug Reports
1

Connection error.

Request ID: 2fa0adde-ee92-4c41-adb7-86c7806f4d00
[internal] Blob not found: {“role”:“user”,“content”:[{“text”:“<additional_data>\nBelow are some potentially helpful/relevant pieces of information for figuring out how to respond:\n<open_and_recently_viewed_files>\nRecently viewed files (recent at the top, oldest at the bottom):\n- /Users/junchaoxu/code/ttraa-app/libs/backend/central-app/data-access/prisma/prisma/schema.prisma (total lines: 2935)\n- /Users/junchaoxu/code/ttraa-app/docs/templates/linear-issue-template.md (total lines: 179)\n\nFiles that are currently open and visible in the user’s IDE:\n- /Users/junchaoxu/code/ttraa-app/docs/templates/linear-issue-template.md (currently focused file, cursor is on line 16, total lines: 179)\n\nNote: these files may or may not be relevant to the current conversation. Use the read file tool if you need to get the contents of some of them.\n</open_and_recently_viewed_files>\n</additional_data><user_query>\n@docs/templates/linear-issue-template.md:1-179 帮我生成一个需求。背景是，selfadvertiser链路中创建完brief不知道联系谁，或者创建完lineitem后，等待influencer自己联系他们。我们需要增加一个帮助他们联系influencer的功能。 这里有3个节点：\n1. 创建完brief。2. 在brief详情页. 3. 在创建完lineitem后。都有对应的帮他们联系的入口。\n点击入口后有两个选择：1 留下留资信息，包括他们的联系方式和邮箱，可以默认从workspace的信息中读取。 2. 直接和销售约google meeting。\n信息输出：将留资信息对接zoho的表单。输出给销售团队。 同时google meeting也同步创建，支持在google内查看。\n</user_query>\n”,“type”:“text”}]}
gie: [internal] Blob not found: {“role”:“user”,“content”:[{“text”:“<additional_data>\nBelow are some potentially helpful/relevant pieces of information for figuring out how to respond:\n<open_and_recently_viewed_files>\nRecently viewed files (recent at the top, oldest at the bottom):\n- /Users/junchaoxu/code/ttraa-app/libs/backend/central-app/data-access/prisma/prisma/schema.prisma (total lines: 2935)\n- /Users/junchaoxu/code/ttraa-app/docs/templates/linear-issue-template.md (total lines: 179)\n\nFiles that are currently open and visible in the user’s IDE:\n- /Users/junchaoxu/code/ttraa-app/docs/templates/linear-issue-template.md (currently focused file, cursor is on line 16, total lines: 179)\n\nNote: these files may or may not be relevant to the current conversation. Use the read file tool if you need to get the contents of some of them.\n</open_and_recently_viewed_files>\n</additional_data><user_query>\n@docs/templates/linear-issue-template.md:1-179 帮我生成一个需求。背景是，selfadvertiser链路中创建完brief不知道联系谁，或者创建完lineitem后，等待influencer自己联系他们。我们需要增加一个帮助他们联系influencer的功能。 这里有3个节点：\n1. 创建完brief。2. 在brief详情页. 3. 在创建完lineitem后。都有对应的帮他们联系的入口。\n点击入口后有两个选择：1 留下留资信息，包括他们的联系方式和邮箱，可以默认从workspace的信息中读取。 2. 直接和销售约google meeting。\n信息输出：将留资信息对接zoho的表单。输出给销售团队。 同时google meeting也同步创建，支持在google内查看。\n</user_query>\n”,“type”:“text”}]}
at r9A (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34267:23755)
at n9A (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34267:22658)
at d9A (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34268:6285)
at rau.run (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34268:10400)
at async GOa.runAgentLoop (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:46834:10206)
at async v5u.streamFromAgentBackend (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:46888:9277)
at async v5u.getAgentStreamResponse (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:46888:13663)
at async bMe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34329:17597)
at async Object.Ea [as onSubmit] (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:45813:4826)
at async vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:45787:57069

image
image3024×1718 403 KB

2

Hi there!

We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.

To help us investigate and fix this faster, could you edit your original post to include the details from the template below?

Bug Report Template - Click to expand

Where does the bug appear (feature/product)?

  • Cursor IDE
  • Cursor CLI
  • Background Agent (GitHub, Slack, Web, Linear)
  • BugBot
  • Somewhere else…

Describe the Bug
A clear and concise description of what the bug is.

Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!

  1. …
  2. …
  3. …

Expected Behavior
What is meant to happen here that isn’t working correctly?

Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)

Operating System

  • Windows 10/11
  • MacOS
  • Linux

Version Information

  • For Cursor IDE: Menu → About Cursor → Copy
  • For Cursor CLI: Run agent about in your terminal
IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......

CLI:
CLI Version 2026.01.17-d239e66

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!

6

Hi @Sophie_XU,

This is a known server-side issue on our end. The error is not related to your setup or network.

As a workaround, please try starting a new chat (don’t continue the conversation where the error occurred). This typically resolves the issue since the error is tied to a specific conversation state.

If the error persists even in a brand new chat, please reply here with the new request ID (three dots menu at top right of chat > Copy Request ID) and I’ll investigate further.