{"version":"2.1.61","anchor":"built-in-tools-no-longer-deferred-by-default","canonical_anchor":"built-in-tools-no-longer-deferred-by-default","heading":"Built-in tools no longer deferred by default","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.61\/e\/built-in-tools-no-longer-deferred-by-default","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.61","markdown":"### Built-in tools no longer deferred by default\n\n**What**\n\nBuilt-in tools marked as deferrable (e.g., Bash, Read, WebFetch, Task tools, etc.) are no longer automatically deferred based on usage frequency. Previously, if you hadn't used a tool recently (usage score below a threshold), it could be hidden and require discovery through the ToolSearch tool before use. Now all built-in tools are loaded and available immediately.\n\n**Details**\n\n- The `tengu_coral_whistle` feature flag default was changed from enabled (`!0`) to disabled (`!1`) in the tool deferral check\n- MCP (Model Context Protocol) tools remain always deferred \u2014 they still require ToolSearch to discover and load\n- Tool usage tracking remains active (the usage recording path is unchanged), suggesting data is still being collected for future improvements\n- The server can still enable usage-based deferral via the feature flag if needed\n\n**Evidence**\n\nTool deferral gate function `WG()` (search for `\"tengu_coral_whistle\"`) \u2014 default changed from `!0` to `!1` at line ~246691"}