ENABLE_TOOL_SEARCH=force now works when set through your settings, not just the shell.
What's wrong with this entry?
Setting 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.
- Resolved value
forceselects thetsttool search mode; any other value leaves the previous resolution in place. - If reading settings fails, the failure is logged and treated as "not forced", so the standard fallback still applies.
ENABLE_TOOL_SEARCH=force claudeisToolSearchForceOverride: settings read failed
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.224
Tool-search telemetry records the real mode and a finer skip reason
Both mention enable tool search
-
v2.1.221
Tool search no longer disabled on Vertex AI
Both mention enable tool search
-
v2.1.232
Tool search says once why it turned itself off
Both mention enable tool search