Command output is being prematurely truncated. It apparently now has a 20k limit (I believe it was much larger before?) which means it cannot accurately run git diffs on large sets of changes. Why is there this limit? should be able to handle up to the remaining context window size at least..
Steps to Reproduce
have the agent do a git diff on anything remotely interesting and the git will be truncated
Expected Behavior
do not truncate – 640k was a barrier long ago, 20k is silly low.
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
hi @charles thank you for the post. It is not a bug in that sense as it’s not broken. We do have to limit context size as long terminal output confuses agents and they perform worse but also consume much more tokens.
We have a fix for that with dynamic context discovery that will roll out soon.
Also doesn’t the Agent find relevant info from logs by itself? that works for me already.
No it tries to read the git diff as requested, sees its truncated and goes a bit wild trying to overcome it. Shouldnt be all these hard limits in Cursor, they’re sloppy. It should scale to infinity unless literally constrained by a hard resource like memory (or token context lengths). Causes problems when none would occur.