Terminal output truncated

Support Help
1

Hi, I use a script that dumps code diffs into the terminal such that an agent can review the diff

However, after updating cursor, I now see the following at the beginning of the terminal output

[Terminal output truncated: ~85KB dropped from beginning]

Is there any way to disable this new behavior such that the entire command output is readable by the model?

2

Hey, thanks for the report.

This is new behavior. The team added a terminal output size limit to avoid performance issues with large outputs.

Right now, there’s no setting to disable this limit. Here are a few workarounds:

  1. Use the Legacy Terminal (Cursor Settings → Agents → Use Legacy Terminal). It doesn’t have this limit.
  2. Redirect the output to a file: your-diff-script > /tmp/diff.txt, then use @Files to add the file to the agent context.
  3. Split the output into smaller chunks, or use tail/head to grab the sections you need.

Could you share more details about your use case? What script are you running, and roughly how big is the diff? This will help the team evaluate whether we should add a setting to control this limit.

3

I’m having this issue as well and just wanted to provide my use case: the output size limit is nowhere near large enough to handle the environment variables being passed into our applications. These environment variables are needed support Firebase, Postgres and Stripe - which are fairly common needs in an application. The environment variables come from a file, which is references in the build config for the key “envFile”. I’m surprised by this change, tbh… it’s very common to drive applications (esp. server side) through env variables in order to run them locally and remotely without code changes, and it’s very common to integrate to authentication, payment, data storage and other 3rd party services.

4

TS describes the problem that his git diff does not fit into 1000 lines of a sliding terminal window. Do you want to let LLM read your env files through the terminal? :eyes:

5

Hm, his issue doesn’t exactly match mine - there are a number of terminal output threads and this is the wrong one! That being said - the issue I am facing is that running a build configuration will not fully enter the command to run the build config; it stops at a certain number of characters and does not “enter” the command. It just leaves the terminal input buffer truncated at that point. And yes, I do want my IDE to set the environment variables for my local environment before running an application. Otherwise, the application won’t run - it won’t connect to the local test database. There are no secrets in these environment variables, those are managed in the infrastructure.

6

Ask Opus 4.5 Thinking or GPT-5.2 XHigh to route the configuration through some config.ini/config.toml and try to debug the system startup. See what happens.

7

Hm, that seems like a lot. I just pulled up the project in another IDE and that works so I’ll go with that approach.