You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
bug(critical): silent truncation causes data loss — LLM takes decisions on incomplete diffs #827
I did a diff between 2 large files (+1000 lines of data/yaml) and asked Claude for a summary.
RTK truncated the diff, Claude didn't tell me or didn't notice.
I made important decisions based on this diff that I can't undo (very frustrating).
Claude confirmed the next day that RTK had truncated the data.
I lost trust, I don't have time for this, I'm uninstalling.
Root cause
rtk diff silently truncates output at 3 levels:
Max 50 changes shown (.take(50)) — no warning to LLM
Lines truncated at 70-80 chars — content silently cut
No machine-readable truncation marker — LLM cannot detect data loss
Same pattern exists in rtk git diff, rtk read, and potentially other commands.
Impact
P0 severity: Users make irreversible decisions on incomplete data
Trust killer: Once bitten, users uninstall RTK
LLM blind spot: Claude/Copilot cannot tell the user that data was truncated
Proposed fix
Short term (must-fix)
Add a clear, machine-readable truncation warning at the end of any truncated output:
[warn] Output truncated: showing 50/847 changes. Run `diff file1 file2` for full output.
This lets the LLM:
Tell the user the diff is incomplete
Suggest running the raw command for full output
Avoid making decisions on partial data
Long term
Add --full flag to disable truncation for critical commands (diff, read)
Consider making rtk diff of large files pass through to raw diff with a warning
Tee integration: save full output to disk, print hint
Silent output truncation across rtk commands (diff, git diff, read) causes LLMs to make decisions on incomplete data without any machine-readable warning; needs truncation markers added to all affected commands.
Triaged automatically by wshm · This is an automated analysis, not a human review.
Activity
fix(diff): never truncate diff content — show all changes in full
pszymkowiak commentedon Mar 26, 2026
🔍 Automated Triage
bugcriticalSummary
Silent output truncation across rtk commands (diff, git diff, read) causes LLMs to make decisions on incomplete data without any machine-readable warning; needs truncation markers added to all affected commands.
Triaged automatically by wshm · This is an automated analysis, not a human review.
fix(sync): never truncate diff content (upstream rtk-ai#827)
fix(diff): never truncate diff content — show all changes in full
fix(diff): never truncate diff content — show all changes in full
ROADMAP: v1.1 plan with P0/P1/P2 priorities, motivated by community
add: versioned rtk config, installed by copy not symlink