dynamic-tool-routing-reuse

Dynamic tool routing manages tool availability by combining always-on Tier1 tools with an LRU and keyword-based Tier2 unlock, plus a permanent fallback. This pattern progressively unlocks additional tools based on usage and user intent.

To enable dynamic tool routing, set the environment variable CLAUDE_CODE_DYNAMIC_TOOLS=1 and issue a sample prompt that includes an intent keyword to unlock a Tier2 tool. This activates the routing pattern in toolRouter.ts.

The LRU and keyword-based unlock mechanism works by keeping essential Tier1 tools always available while unlocking Tier2 tools when user intent keywords are detected, maintaining a least-recently-used cache for progressive availability.

Yes, you can debug tool availability in third-party API modes using the documented integration points in toolRouter.ts and related services. The system provides clear guidelines for extending tool sets and troubleshooting availability.

When the dynamic tool set is insufficient, a permanent fallback safety mechanism guarantees access to the full CORE_TOOL_NAMES set. This ensures critical tasks remain supported even if dynamic routing fails to unlock needed tools.

Yes, dynamic tool routing supports extending tool sets by providing clear guidelines for adding new tools, extending intent keyword detection, and maintaining modular architecture across code assistants and related services.