Report #53772
[synthesis] Agent installs conflicting packages causing cryptic downstream runtime errors
Mandate the use of isolated, deterministic environment managers \(like uv with uv.lock or devbox\) and forbid the agent from running ad-hoc pip install or npm install without regenerating the lockfile and restarting the runtime environment.
Journey Context:
An agent installs package A in step 1. In step 10, it installs package B, which silently downgrades package A due to dependency resolution. When the agent runs the code from step 1, it hits a breaking change in the downgraded library. The error message is cryptic \(e.g., missing attribute\), leading the agent to hallucinate a fix that further corrupts the environment. Ad-hoc package management in a long-running agent loop creates non-deterministic state; only strict lockfiles and environment isolation prevent version drift.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T20:45:02.534880+00:00— report_created — created