Overview
The Meta-Agent is TaurusX's strategic layer — a persistent coordinator that breaks complex goals into plans, delegates steps to the appropriate agents and engines, monitors progress, and adapts when conditions change.
Think of the Meta-Agent as the part of TaurusX that knows how to achieve a goal, not just how to answer a question. While the chat screen handles one exchange at a time, the Meta-Agent handles multi-step, multi-session objectives.
Planning
When the Routing Engine detects a multi-step goal, it activates the Meta-Agent automatically. You can also activate it explicitly with a natural language cue:
The Meta-Agent produces a structured plan — a numbered sequence of steps, each with:
- A clear action description
- The agent, engine, or tool that will execute it
- Dependencies on prior steps
- An estimated Cycle cost
Plans are shown in the Meta-Agent Console and can be approved, modified, or cancelled before execution begins.
Delegation
Once a plan is approved, the Meta-Agent delegates each step to the appropriate executor:
| Step Type | Delegated To |
|---|---|
| AI reasoning / generation | TX Engine (via the EAL) |
| Agent task | Agent Engine — dispatches to a named agent |
| Workflow trigger | Workflow Engine — runs a configured workflow |
| External tool call | Tool connector (e.g. web search, API call) |
| User decision required | Pauses and surfaces a confirmation request in the chat screen |
During execution, the Meta-Agent tracks the status of each delegated step. Completed steps are checked off the plan. Blocked steps surface a notification in the Continuum interface for the user to resolve.
Adaptive Strategy
Plans are not static. The Meta-Agent monitors execution and adapts when something changes:
- Step fails — Meta-Agent evaluates whether to retry, find an alternative approach, or escalate to the user
- New information arrives — plan steps can be revised to reflect updated context
- User changes goal — the plan is updated to reflect the new direction; completed steps are preserved
- Guardian blocks a step — Meta-Agent surfaces the block, explains the reason, and suggests a safe alternative
The Meta-Agent Console
The Meta-Agent Console is accessible from the Continuum sidebar under ENGINES → Meta-Agent, or directly at /os/continuum/meta-agent.
The console has three tabs:
| Tab | Description |
|---|---|
| Console | Live view of the Meta-Agent — current goal, active plan, step-by-step execution status, and Cycle usage |
| Plans | All active and paused plans with their current status and progress percentage |
| History | Completed, cancelled, and failed plans with full execution traces |
Within the Console tab, you can:
- Submit a new goal by typing in the goal input and pressing Enter
- Pause or resume an active plan
- Approve or reject a step that requires user confirmation
- View the full reasoning trace for any completed step
Plan History
Every plan the Meta-Agent creates is saved to the plan history, including:
- The original goal as submitted
- The full plan with all steps
- Execution timestamps for each step
- Outcomes: completed, skipped, blocked, or failed
- Total Cycles consumed
Plan history is retained for 90 days. Administrators can extend retention in account settings.
Limits & Guardrails
| Limit | Default | Notes |
|---|---|---|
| Max plan steps | 24 steps | Plans exceeding this are split into sub-plans |
| Max concurrent plans | 3 | Additional plans queue until a slot is free |
| Max autonomy duration | Plan-tier based | Free: 1h, Pro: 8h, Enterprise: unlimited |
| Guardian-blocked steps | Cannot proceed | User must authorise or the step is skipped |
| Cycle limit per plan | Account cycle balance | Plan halts if cycles are exhausted |