Under the hood
Useful2 Signal2
The agent proxy's CLI lookup now gives up on a slow PATH scan instead of stalling startup.
What's wrong with this entry?
Anonymous. No account, no email.
What
The placeholder environment variables the agent proxy injects for GitHub, AWS and Google now come from one data table instead of three hand-written blocks, and the scan of your PATH for an already-installed CLI runs under a deadline. On timeout it records an event and carries on with only the CLIs it resolved so far.
Details
- The timeout event is
agent_proxy_path_probe_timeout. - Unconditional during agent-proxy startup.
Evidence
agent_proxy_path_probe_timeout
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.248
Agent proxy adds flow control with caps and stall aborts
Both mention agent proxy
-
v2.1.248
Proxy status JSON exposes backpressure counters
Both mention agent proxy
-
v2.1.248
Agent-proxy failures go through one helper
Both mention agent proxy