The Orchestrator is how MeghaOS handles requests that require doing multiple things: “search for AI news, summarize it, and email me the result.” It uses AI to decompose the request into a graph (a DAG) of steps, then hands that graph to the Workflow Engine to execute.

​
The flow

1

Decompose

AI breaks the request into a list of steps.
2

Fill gaps

For any capability that doesn’t exist yet, a creation step is scheduled first (see auto-creation).
3

Execute

Run the graph (independent steps in parallel).
4

Report

Return a task-tracker widget summarizing each step’s status.

​
Decomposition

The planner doesn’t consider every capability at once. It first finds the most relevant tools for your request, then asks the AI to produce a plan. Each step describes:
Steps with no depends_on run in parallel. Use $key in an argument to consume an output from an earlier step, which is how data flows through the graph.

​
Personas (role-based steps)

MeghaOS supports personas. The planner assigns a role per step: At execution time the role’s expertise is injected into the prompt for that step, producing more domain-specialized output. A step can also delegate work to another role mid-flight. See Personas.

​
Auto-creating missing capabilities

If the plan references a capability that doesn’t exist, the orchestrator doesn’t fail; it creates it. A creation step is scheduled before the step that needs it (planning-time), and a runtime safety net covers anything still missing at execution time. See Self-Extension.

​
Two execution paths

MeghaOS prefers the Orchestrator (parallel graph). If that path errors, it falls back to a simpler sequential executor that runs the steps one after another.