A PATH-prepending prologue for every Bash call is wired into the command builder but its providers return nothing.
What
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.
Details
- 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.
Evidence
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.
One source agreesOne thing we can check says the same as this entry.
The name it cites is new in this build
New in this build: tengu_sl_gate_config