Reactive vs TPAOV
The runtime currently supports two distinct execution styles because not every task benefits from the same loop shape.
Reactive
Section titled “Reactive”Reactive mode is primarily for specialist tasks.
Characteristics:
- direct native tool-calling turns
- low loop overhead
- fast progress when the task is focused
- runtime-side completion checks still apply
Use this mental model: the agent is mostly doing the work directly.
Reactive mode is a good fit when the system already knows what kind of task exists and the main question is “can the specialist perform it efficiently?”
TPAOV stands for:
- Think
- Plan
- Act
- Observe
- Verify
This mode is primarily for orchestrator work where the system benefits from explicit planning and verification between phases.
Use this mental model: the agent is coordinating, reasoning about the workflow, and deciding what should happen next.
Why The Split Exists
Section titled “Why The Split Exists”Specialist execution usually wants speed and direct tool use. Orchestrator execution usually wants structure, explicit planning, and stronger verification.
That is why Agirunner does not force one loop style onto every task. The platform chooses the mode through the task contract. The runtime enforces it.