Failed to share transcript. Try again later

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Failed to share transcript. Try again later.

Steps to Reproduce

(1) Click share scripts
------------------------------------network log-----------------------------------
Cursor Network Diagnostic Results

DNS: Success
Logs:
[2026-04-07T21:22:58.764Z] Host: api2.cursor.sh
[2026-04-07T21:22:58.764Z] Servers: 127.0.0.1
[2026-04-07T21:22:58.764Z] Resolved to 100.51.120.45 in 18ms
[2026-04-07T21:22:58.790Z] Resolved to 100.51.120.45 in 1ms
[2026-04-07T21:22:58.791Z] Resolved to 100.51.120.45 in 0ms
[2026-04-07T21:22:58.791Z] Resolved to 100.51.120.45 in 0ms
[2026-04-07T21:22:58.793Z] Host: api2.cursor.sh
[2026-04-07T21:22:58.793Z] Servers: system
[2026-04-07T21:22:58.793Z] Resolved to 100.51.120.45 in 1ms
[2026-04-07T21:22:58.793Z] Resolved to 100.51.120.45 in 0ms
[2026-04-07T21:22:58.794Z] Resolved to 100.51.120.45 in 0ms
[2026-04-07T21:22:58.794Z] Resolved to 100.51.120.45 in 0ms
[2026-04-07T21:22:58.794Z] Result: true

HTTP/2: Success
Logs:
[2026-04-07T21:22:58.739Z] Start
[2026-04-07T21:22:58.846Z] Host: api2.cursor.sh
[2026-04-07T21:22:58.846Z] Protocol: h2
[2026-04-07T21:22:58.846Z] Result: true in 107ms

SSL: Success
Logs:
[2026-04-07T21:22:58.739Z] Start
[2026-04-07T21:22:58.971Z] URL: https://api2.cursor.sh/
[2026-04-07T21:22:58.971Z] Status: 200
[2026-04-07T21:22:58.971Z] IP: 100.51.120.45
[2026-04-07T21:22:58.971Z] Issuer: C=US; O=Amazon; CN=Amazon RSA 2048 M01
[2026-04-07T21:22:58.971Z] Name: api2.cursor.sh
[2026-04-07T21:22:58.971Z] AltName: DNS:api2.cursor.sh, DNS:prod.authentication.cursor.sh, DNS:*.api2.cursor.sh
[2026-04-07T21:22:58.971Z] DNS Time: 6ms
[2026-04-07T21:22:58.971Z] Connect Time: 51ms
[2026-04-07T21:22:58.971Z] TLS Time: 128ms
[2026-04-07T21:22:58.971Z] Result: true in 232ms

API: Success
Logs:
[2026-04-07T21:22:58.739Z] Start
[2026-04-07T21:22:58.940Z] Result: true

Ping: Success
Logs:
[2026-04-07T21:22:58.740Z] Sending ping 1
[2026-04-07T21:22:58.980Z] Response: ‘ping’ in 240ms
[2026-04-07T21:22:58.980Z] Sending ping 2
[2026-04-07T21:22:59.052Z] Response: ‘ping’ in 71ms
[2026-04-07T21:22:59.052Z] Sending ping 3
[2026-04-07T21:22:59.105Z] Response: ‘ping’ in 53ms
[2026-04-07T21:22:59.105Z] Sending ping 4
[2026-04-07T21:22:59.162Z] Response: ‘ping’ in 57ms
[2026-04-07T21:22:59.162Z] Sending ping 5
[2026-04-07T21:22:59.220Z] Response: ‘ping’ in 58ms
[2026-04-07T21:22:59.220Z] Result: true

Chat: Success
Logs:
[2026-04-07T21:22:58.741Z] Starting stream
[2026-04-07T21:22:58.940Z] Response: ‘foo’ in 198ms
[2026-04-07T21:22:59.961Z] Response: ‘foo’ in 1021ms
[2026-04-07T21:23:01.577Z] Response: ‘foo’ in 1616ms
[2026-04-07T21:23:02.571Z] Response: ‘foo’ in 994ms
[2026-04-07T21:23:03.598Z] Response: ‘foo’ in 1027ms
[2026-04-07T21:23:04.574Z] Result: true

Agent: Success
Logs:
[2026-04-07T21:22:58.742Z] Starting stream
[2026-04-07T21:22:58.742Z] Pushing first message
[2026-04-07T21:22:58.947Z] Response: ‘foo’ in 205ms
[2026-04-07T21:22:59.448Z] Pushing next message
[2026-04-07T21:22:59.495Z] Response: ‘foo’ in 548ms
[2026-04-07T21:23:00.003Z] Pushing next message
[2026-04-07T21:23:00.087Z] Response: ‘foo’ in 591ms
[2026-04-07T21:23:00.596Z] Pushing next message
[2026-04-07T21:23:00.643Z] Response: ‘foo’ in 556ms
[2026-04-07T21:23:01.151Z] Pushing next message
[2026-04-07T21:23:01.203Z] Response: ‘foo’ in 560ms
[2026-04-07T21:23:01.203Z] Result: true

Marketplace: Success
Logs:
[2026-04-07T21:22:58.734Z] Host: marketplace.cursorapi.com
[2026-04-07T21:22:58.827Z] Response in 93ms
[2026-04-07T21:22:58.827Z] Response: 200
[2026-04-07T21:22:58.827Z] Response Type: cors
[2026-04-07T21:22:58.827Z] Server: null
[2026-04-07T21:22:58.827Z] Result: OK in 93ms

Authentication: Success
Logs:
[2026-04-07T21:22:58.736Z] Host: prod.authentication.cursor.sh
[2026-04-07T21:22:59.470Z] Response: 200 in 734ms

Authentication UI: Success
Logs:
[2026-04-07T21:22:58.739Z] DNS lookup: authenticator.cursor.sh
[2026-04-07T21:22:58.766Z] Resolved authenticator.cursor.sh to 172.64.152.23 in 11ms

Cursor Tab: Success
Logs:
[2026-04-07T21:22:58.739Z] DNS lookup: api3.cursor.sh
[2026-04-07T21:22:58.765Z] Resolved api3.cursor.sh to 104.18.19.125 in 10ms

Agent Endpoint: Success
Logs:
[2026-04-07T21:22:58.739Z] DNS lookup: agent.api5.cursor.sh
[2026-04-07T21:22:59.341Z] Resolved agent.api5.cursor.sh to 100.30.166.181 in 593ms

Codebase Indexing: Success
Logs:
[2026-04-07T21:22:58.739Z] DNS lookup: repo42.cursor.sh
[2026-04-07T21:22:58.767Z] Resolved repo42.cursor.sh to 32.193.75.77 in 10ms

Downloads: Success
Logs:
[2026-04-07T21:22:58.738Z] Host: downloads.cursor.com
[2026-04-07T21:22:58.880Z] Response: 403 in 142ms

CDN: Success
Logs:
[2026-04-07T21:22:58.738Z] Host: cursor-cdn.com
[2026-04-07T21:22:59.053Z] Response: 404 in 315ms

Expected Behavior

allow sharing.

Operating System

Windows 10/11

Version Information

Version: 3.0.12 (user setup)
VSCode Version: 1.105.1
Commit: a80ff7dfcaa45d7750f6e30be457261379c29b00
Date: 2026-04-04T00:13:18.452Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26200

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, thanks for the report. The Share Transcript feature is only available on paid plans Pro, Business, and Enterprise. It shouldn’t work on the Free plan, but you’re right that the error message is confusing. Instead of something clear like feature is only available for Pro users, it shows the generic Failed to share transcript.

For now, if you need to share the chat content, you can use the chat context menu three dots and select Copy.