Progressive AX and SubAgent Delegation
Loading dozens of tools into an Agent's context window upfront degrades system performance. It induces cognitive load, causes choice paralysis, increases parameter hallucinations, and wastes tokens.
Progressive AX and SubAgent Delegation are the two primary structural patterns for managing complex toolsets without overloading context.
Progressive AX vs. SubAgents: Choosing Your Work Boundary
| Pattern | Operational Metaphor | Best Used When... | Context Window Impact | Risks |
|---|---|---|---|---|
| Progressive AX | Page Navigation<br/>(Single Agent) | You need multi-step page or form navigation within a single continuous thread. | Tool schemas swap dynamically; chat history is preserved. | Context window growth over time; potential token bloat on long conversations. |
| SubAgents | Task Delegation<br/>(Supervisor-Worker) | Trial and error is common or the task is unrelated to our Agent's expertise. | Intermediate tool outputs and scratchpad iterations are fully isolated. | Context loss or degradation during the initial supervisor handoff. |
Lifecycle: Progressive AX (Single Agent Page Router)
In Progressive AX, a single agent transitions across UI states within one thread.
The agent starts in a Gatekeeper State with a single SKILL lookup tool. Upon retrieving the product_management SKILL, the harness unmounts the gatekeeper tool and dynamically mounts search_products and edit_product.
Lifecycle: SubAgents (Isolated Context Boundary)
SubAgents enforce a structural context boundary. The primary agent delegates execution to a new agent instance, keeping worker scratchpads and intermediate steps completely out of the main thread.
Engineering Gains: Progressive AX vs. SubAgent Delegation
Depending on your architecture's core bottleneck, both patterns offer distinct gains:
1. Progressive AX Gains (In-Thread Continuity)
- Reasoning Precision: Only giving the agent a handful of context-relevant tools reduces choice paralysis and parameter cross-contamination.
- Deterministic Control: Relying on verbal system instructions like "Don't call Tool B until Tool A is complete" fails at scale. Progressive AX enforces sequences in application code—Tool B literally does not exist in the schema until Tool A succeeds.
- Shared Conversational Memory: Preserves full thread visibility so the agent can reference prior user inputs without complex context re-hydration.
2. SubAgent Delegation Gains (Context Isolation)
- Absolute Scratchpad Cleanliness: Loops, trial-and-error attempts, and multi-turn debug steps remain in the worker thread, preventing main-context pollution.
- Context Preservation: Protects the supervisor agent's context window from blowing past token limits during noisy, repetitive sub-routines.
- Parallelization Potential: Enables the supervisor to spin up multiple specialized subagents simultaneously to handle independent sub-tasks in parallel.