{"version":"2.1.227","anchor":"enable-tool-search-force-now-works-from-settings-composed-en","canonical_anchor":"enable-tool-search-force-now-works-from-settings-composed-en","heading":"ENABLE_TOOL_SEARCH=force now works from settings-composed environment","tier":"use","area":"Tool Search","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/enable-tool-search-force-now-works-from-settings-composed-en","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### `ENABLE_TOOL_SEARCH=force` now works from settings-composed environment\n\nENABLE_TOOL_SEARCH=force now works when set through your settings, not just the shell.\n\n**What**\n\nSetting `ENABLE_TOOL_SEARCH` to `force` pins tool search to its search-based mode and skips the \"standard\" fallback that would otherwise apply. The value is now read from the environment Claude Code composes from your settings, not just the raw process environment. The override is refused under HIPAA mode and for non-first-party model providers.\n\n**Details**\n\n- Resolved value `force` selects the `tst` tool search mode; any other value leaves the previous resolution in place.\n- If reading settings fails, the failure is logged and treated as \"not forced\", so the standard fallback still applies.\n\n**Usage**\n\n`ENABLE_TOOL_SEARCH=force claude` **Evidence** `isToolSearchForceOverride: settings read failed`\n\n- Area: Tool Search\n- Names: `ENABLE_TOOL_SEARCH`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 3\/5"}