{"version":"2.1.280","anchor":"inline-tools-gate-consolidated-with-env-var-overrides","canonical_anchor":"inline-tools-gate-consolidated-with-env-var-overrides","heading":"Inline tools gate consolidated with env-var overrides","tier":"soon","area":"Inline Tools","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/inline-tools-gate-consolidated-with-env-var-overrides","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Inline tools gate consolidated with env-var overrides\n\nWhether 'inline tools' are enabled is now decided by a consolidated check with environment-variable overrides\n\n**What**\n\nA new helper function determines whether \"inline tools\" are enabled, checking in this order:\n\n- `CCR_SESSION_PROFILE` \u2014 if set, inline tools are disabled\n\n- `CLAUDE_CODE_INLINE_TOOLS` \u2014 if set, it directly overrides the setting\n\n- Otherwise, it falls back to a remote gate called `tengu_brisk_meadow`\n\n**Why**\n\nThis consolidates what was presumably scattered logic into one place and gives environment variables a way to force inline tools on or off regardless of the remote rollout gate.\n\n- Flag `tengu_brisk_meadow`: Off in both readings (read for one account on one subscription tier against v2.1.280; this account: off, anonymous baseline: off, compiled default: not a boolean we can read) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Inline Tools\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}