[BUG] [Message truncated - exceeded 50,000 character limit] in cursor:extension/anthropic.claude-code

Status Open
Maintainer reply None cached
Activity 3 comments · opened Oct 2, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

in cursor extension if I submit a prompt with more than 50k I get [Message truncated - exceeded 50,000 character limit] and LOSE FOREVER my prompt, evem on export etc..

What Should Happen?

if there is a limite of 50k, NOTIFY ME IN THE INPUT and dont allow to type moree, not crop it and remove forever my prompt... a simple maxlength works...

Error Messages/Logs

Steps to Reproduce

  • paste a long text 50K more on the chat
  • write a prompt on the end
  • submit it and wait for the wrong answer from model and check a [Message truncated - exceeded 50,000 character limit] at end of the prompt

press arrow up on chat and daam [Message truncated - exceeded 50,000 character limit] again..
export chat and dam [Message truncated - exceeded 50,000 character limit] again...

WHERE IS MY PROMPTTTT

Claude Model

None

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

any

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

3 Comments

sandercoffee · 12 days ago
sandercoffee · 12 days ago

I think that it happens on vs code extension also, same code?

adri22235 · 12 days ago

Root cause, checked against the 2.1.287 extension from Open VSX (webview/index.js):

  • On submit, the webview cuts the prompt to a hard-coded 50,000 UTF-16 code units and appends [Message truncated - exceeded 50,000 character limit]. It then clears the composer and resets the prompt history, which is why the original text can't be recovered with ↑ or from an export.
  • The limit isn't configurable: none of the extension's settings touch it.
  • The CLI isn't affected. The claude binary bundled in the VSIX (linux-x64) is byte-identical to the standalone 2.1.287 binary, and it has no such truncation, so claude in a terminal (including Cursor's integrated terminal) takes the full prompt.

Running that same truncation code on a 59,993-character prompt with the question at the end sends 50,055 characters (50,000 + the marker), and the question is gone.

Suggested fix: when the prompt is over the limit, keep it in the composer and show an inline error (or disable Send) instead of truncating and clearing it.

Workaround: put the long text in a file and @-mention it, or use claude in a terminal.