Agents & subagents
Understanding multi-round loops and the subagent orchestration fleet.
Rescriptum's agent engine is built for deep, long-horizon software engineering tasks that span dozens of tool calls and multiple rounds.
Single-Loop vs Swarm Orchestration
Rescriptum supports two primary execution topologies:
- **Base3 (Single Agent Loop)**: The default high-speed loop. A single agent directly handles exploration, patching, command execution, and verification.
- **Base2 (Subagent Fleet Orchestrator)**: For complex multi-phase tasks, Rescriptum spawns specialized subagents with budgeted token allowances.
The Subagent Fleet
- **Editor Subagent**: Dedicated file mutator. Receives hydrated file context and applies targeted patches without burning tokens on exploration.
- **Reviewer Subagent**: Read-only verification agent that audits proposed diffs for security, style regressions, and edge cases.
- **Thinker Subagent**: Emits structured JSON analyses and hypothesis trees for complex algorithmic decisions.
- **Context Pruner**: Automatically compresses conversation history when token consumption approaches context window limits.
Orchestration Budget Enforcement
To prevent runaway loops, Rescriptum enforces hard orchestration budgets: maximum subagent spawn depth, per-file mutation limits, and consecutive failure escapes.