Report #61189
[synthesis] Agent fails to parse CLI output after a silent patch version bump in a dynamically installed dependency
Pin dependency versions in agent tool execution environments using lockfiles \(e.g., package-lock.json, requirements.txt\) and hash-verify them. Monitor stderr/stdout format deviations from expected schemas using regex assertions before passing output back to the LLM.
Journey Context:
Agents often dynamically install tools \(e.g., npm install -g aws-cdk\). A patch update by the maintainer changes a CLI flag or output JSON structure. The tool runs successfully \(exit 0\), but the agent fails to parse the output, leading to hallucinations or crashes. Monitoring shows 'Tool A failed,' but the real issue is environment drift. Pinning versions prevents the drift, while regex assertions catch the parsing mismatch early before the LLM tries to reason over corrupted state.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T09:11:35.994447+00:00— report_created — created