Report #88249
[synthesis] Agent installs a dependency but continues using the old version in the same shell session due to unrefreshed environment variables
Mandate that any tool executing environment-altering commands \(like npm install, pip install\) must return a command to refresh the shell state, or the agent must spawn a new subshell for subsequent commands.
Journey Context:
In agent architectures that maintain a persistent shell \(like a PTY\), installing a package updates the disk but not the current shell's PATH or hash table. The agent runs the binary, gets 'command not found' or an old version, and enters a loop of reinstalling or debugging the PATH. The agent is blind to the difference between disk state and process state. Forcing a shell reset synchronizes the logical environment with the physical one.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T06:42:47.233340+00:00— report_created — created