{"version":"2.1.239","anchor":"the-same-shell-preamble-machinery-would-install-a-bq-shim-an","canonical_anchor":"the-same-shell-preamble-machinery-would-install-a-bq-shim-an","heading":"The same shell-preamble machinery would install a bq shim, and cannot currently be enabled","tier":"soon","area":"Bash Tool","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/the-same-shell-preamble-machinery-would-install-a-bq-shim-an","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### The same shell-preamble machinery would install a `bq` shim, and cannot currently be enabled\n\nThe same shell preamble would install a bq shim on PATH, and cannot be turned on here.\n\n**What**\n\nThe 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.\n\n**Details**\n\n- Remote config key `tengu_sl_gate_config`, in-source fallback all false with python_leg \"on\".\n- Telemetry `bash_sl_gate` includes a materialise_failed reason for a directory that could not be written.\n- The key does not appear in v2.1.238.\n\n**Evidence**\n\n`sl-gate: could not write the carrier, off this process:`\n\n- Area: Bash Tool\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}