# 20k command result limit is far too little **URL:** \ **Category:** Bug Reports\ **Created:** [January 6, 2026, 10:50pm UTC](https://forum.cursor.com/t/20k-command-result-limit-is-far-too-little/148152 "2026-01-06T22:50:11Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![charles](https://avatars.discourse-cdn.com/v4/letter/c/6f9a4e/32.png) [@charles](https://forum.cursor.com/u/charles)\ **Post date:** [January 6, 2026, 10:50pm UTC](https://forum.cursor.com/t/20k-command-result-limit-is-far-too-little/148152/1 "2026-01-06T22:50:11Z")
### Where does the bug appear (feature/product)? Cursor IDE ### Describe the Bug 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) Version: 2.3.21 VSCode Version: 1.105.1 Commit: 68e0a0385b87408d050869ea543e3778ad53f780 Date: 2026-01-02T23:46:13.381Z Electron: 37.7.0 Chromium: 138.0.7204.251 Node.js: 22.20.0 V8: 13.8.258.32-electron.0 OS: Darwin arm64 24.6.0 ### Does this stop you from using Cursor Sometimes - I can sometimes use Cursor ---
**Author:** ![Artemonim](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/artemonim/32/56113_2.png) [@Artemonim](https://forum.cursor.com/u/Artemonim)\ **Post date:** [January 6, 2026, 10:59pm UTC](https://forum.cursor.com/t/20k-command-result-limit-is-far-too-little/148152/2 "2026-01-06T22:59:07Z")
Most likely limited to 1000 lines. Tell Agent to export the git diff to a file if it needs to read it. I run this in PowerShell ```auto git diff > temporary/git_diff.txt && git add . && git status >> temporary/git_diff.txt ``` ---
**Author:** ![condor](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/condor/32/73148_2.png) [@condor](https://forum.cursor.com/u/condor)\ **Post date:** [January 7, 2026, 4:22am UTC](https://forum.cursor.com/t/20k-command-result-limit-is-far-too-little/148152/3 "2026-01-07T04:22:14Z")
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. > **[Dynamic context discovery](https://cursor.com/blog/dynamic-context-discovery)** > > Built to make you extraordinarily productive, Cursor is the best way to code with AI. ---
**Author:** ![charles](https://avatars.discourse-cdn.com/v4/letter/c/6f9a4e/32.png) [@charles](https://forum.cursor.com/u/charles)\ **Post date:** [January 9, 2026, 9:00am UTC](https://forum.cursor.com/t/20k-command-result-limit-is-far-too-little/148152/4 "2026-01-09T09:00:00Z")
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. ---
**Author:** ![lili](https://avatars.discourse-cdn.com/v4/letter/l/b38774/32.png) [@lili](https://forum.cursor.com/u/lili)\ **Post date:** [January 9, 2026, 10:04am UTC](https://forum.cursor.com/t/20k-command-result-limit-is-far-too-little/148152/5 "2026-01-09T10:04:30Z")
[Say Goodbye to AI’s “Goldfish Memory”! MCP Git Server Deep Integration Guide - Discussions - Cursor - Community Forum](https://forum.cursor.com/t/say-goodbye-to-ais-goldfish-memory-mcp-git-server-deep-integration-guide/148171) Try using this MCP tool. Have it save each modification to a change log, and then let it view the change list before pushing the final update. ---
**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\ **Post date:** [January 31, 2026, 10:05am UTC](https://forum.cursor.com/t/20k-command-result-limit-is-far-too-little/148152/6 "2026-01-31T10:05:29Z")
This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.