The same shell preamble would install a bq shim on PATH, and cannot be turned on here.
The bq shim preamble builder always yields null because both accessors that would activate it return nothing.
What's wrong with this entry?
The preamble this subsystem would add puts a bq shim on PATH from a per-version directory under Claude Code's temp root and can extend PYTHONPATH. No setting reaches it in this build: the two accessors that would activate it return nothing, so the preamble builder always yields null and the directory is never written.
- Remote config key
tengu_sl_gate_config, in-source fallback all false with python_leg "on". - Telemetry
bash_sl_gateincludes a materialise_failed reason for a directory that could not be written. - The key does not appear in v2.1.238.
sl-gate: could not write the carrier, off this process:
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