Tool Loop Control Directory
Type: kb/types/index.md
← Parent
- A framework-owned tool loop can simulate explicit orchestration by externalizing control state (note) - Shows how a framework-owned tool loop can recover branching, recursive decomposition, and state projection by moving the control stack into a singleton runtime/tool instead of application code
- Anatomy of an LLM application (note) - Starts from the standard prompted-agent tool loop, showing that the real control boundary appears when applications need to change the capability surface for later steps
- LLM frameworks should keep the tool loop optional (note) - Framework-owned tool loops package the common model/tool/retry pattern well, but strong frameworks keep the loop optional so applications can control state projection, branching, and re-entry