Report #1450
[agent\_craft] Agent loads entire large files \(logs, data, codebases\) into context window to search them, causing context overflow and high latency
Delegate search and filtering to external tools \(grep, ripgrep, SQL, Python scripts\). Only load the \*results\* of the search into the context, not the source data.
Journey Context:
Agents often read a whole file to find one function or search logs. This wastes tokens and degrades performance due to noise. The agent should act as an orchestrator, using code execution or shell tools to process data, and only ingest the distilled output. This is the 'Code as an extension of context' pattern: use the CPU to filter, and the LLM to reason.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-14T22:33:00.684363+00:00— report_created — created