my-pi/pi-tool-search/docs/dynamic-tool-loading.md

Current dynamic tool-group loading

pi-tool-search keeps full low-frequency schemas hidden behind a compact, validated group catalog.

1. session_start activates tool_search, the six cross-platform Pi core tools, and configured alwaysEnabled names. The my-pi defaults also pin CodeGraph exploration, LSP diagnostics, and the three high-frequency Context Mode execution tools. On Windows, powershell is pinned beside bash; on non-Windows hosts it is excluded. Pinned tools do not consume the dynamic-group or dynamic-tool budget.
2. Hidden definitions are hashed with grouping constraints and matched against extensions/bundle-groups.ts. Available standard tools receive checked-in groups; unavailable optional tools are omitted.
3. If every hidden tool is recognized, the bundle catalog is used directly. No model call or per-user cache is required.
4. Additional tools receive immediate deterministic prefix/source groups. A matching model-enriched cache is reused only if it preserves all checked-in bundle assignments.
5. Only a hybrid catalog with unrecognized tools can call ModelRegistry.complete(), and an exact existing group skips that enrichment so activation cannot wait on an unrelated unknown tool. Unknown-group and query lookups may still enrich the catalog. The prompt marks bundle assignments as fixed; validation rejects any response that moves them.
6. Code validation still requires every exact tool name exactly once and rejects unknown names, duplicates, oversized generated groups, omissions, and tool-card/group mismatches. Generated text never changes executable schemas.
7. Loading one exact group or an atomic groups batch calls setActiveTools() once with the original full tool definitions. A batch is rejected without changing active state if its requested groups alone exceed either capacity limit. Pi supplies newly added schemas on the next model request.
8. Group load and member execution update an in-session LRU counter. Loading past the five-group or 28-tool defaults removes least-recently-used non-requested dynamic groups. /tool-search-status reports current capacity, LRU order, and the latest eviction reason.
9. Natural-language lookup gives exact tool names and workflow aliases more weight than descriptive overlap. Weak or closely tied matches return candidates without activation.
10. turn_start notices tool or grouping-configuration changes by hash, resets stale dynamic groups, and reconstructs the checked-in/hybrid catalog.

The standard bundle assigns the official Hippo Pi extension's five hippo_* tools to recall and management groups, and assigns Agent, get_subagent_result, and steer_subagent to the subagents orchestration group. context_tree_query remains in memory-recall because it recovers condensed tool output; retired Hermes names and third-party tff-memory_* names are not seeded. The maintained pi-ssh tools are also split by workflow: sequential reviewed agent-controlled connection lives in ssh-connection, structured ssh_read/ssh_write/ssh_edit file operations live in ssh-remote-files, bounded ssh_find/ssh_grep discovery lives in ssh-remote-search, and sequential reviewed workspace changes plus reviewed command execution live in ssh-remote-shell. The workflows tell the model to call ssh_connect or ssh_cd separately and wait for success before issuing remote calls that depend on the new connection or cwd. The maintained ask_user_question tool has its own user-interaction group so the model can load the complete interactive schema only when a missing decision or preference must come from the user. The pinned pi-chrome bridge registers its 21 chrome_* tools only after explicit per-session authorization. Once registered, catalog refresh assigns them to chrome-navigation, chrome-interaction, and chrome-debugging; the 28-tool default allows all three groups to coexist. Revocation remains enforced inside every upstream tool execution even if a schema is later reactivated by Tool Search.

A purely additive first load receives Pi's native dynamic-tool result propagation. A replacement that evicts one group while adding another is intentionally non-additive; current Pi detects the removal and uses its safe next-request fallback instead of attaching an invalid additive-only hint.

A model cannot call a schema it had not received in an already-generated assistant response. tool_search therefore returns normally, and the next model request sees the activated group's complete schemas. No provider payload rewriting, proxy dispatch, hidden steer message, old package alias, or duplicate Pi runtime is used.