Report #15433
[agent\_craft] Pasting entire command line outputs into context window fills it with low-value tokens
Truncate or filter tool outputs aggressively on the tool side before returning to the LLM. For build commands, only return the last N lines or lines containing 'Error'. For file reads, return specific line ranges.
Journey Context:
Developers often pipe raw stdout back to the LLM. This fills the context with low-value tokens \(like progress bars or success logs\) and pushes the actual system prompt or user request out of the high-attention zone. Pre-processing tool outputs \(e.g., using tail, grep, or custom parsers\) on the execution side is a critical context engineering step that saves tokens and preserves focus.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T00:11:17.784941+00:00— report_created — created