Bash commands could get a private directory prepended to PATH, but nothing ever supplies one.
A PATH-prepending prologue for every Bash call is wired into the command builder but its providers return nothing.
What's wrong with this entry?
New machinery creates a private directory under Claude Code's temp root and prepends it to PATH, and optionally PYTHONPATH, for every Bash tool call via a prologue spliced into the command string. The bash command builder already calls it. It is inert: the function the runtime consults returns nothing unconditionally, as does the provider of the directory's contents, so no prologue is ever added.
- The remote config key is
tengu_sl_gate_config, whose in-source fallback is enabled false, enforce false, everywhere false, python_leg "on". - That config reader has no caller anywhere in the bundle, so the fallback is not what decides the behaviour; the stubbed runtime check is.
- The prologue is wrapped as
'eval' '...' 2>/dev/null || 'true'so a failure cannot break the command. - Telemetry names
bash_sl_gatesuccess and materialise_failed are already registered. - None of this exists in 2.1.238.
tengu_sl_gate_config, carrier dir resolves outside the claude temp root
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.234
Every session now gets the
cdpermission warning in the Bash toolBoth mention bash tool
-
v2.1.234
Command lessons are recorded with the command that produced them
Both mention bash tool
-
v2.1.238
Directory tracking for backgrounded commands no longer breaks early
Both mention bash tool