Status: Future idea, not scheduled. Lives in the v0.5+ ""maybe"" bucket of the roadmap.
Summary
Alternative to the ReAct loop: explicit planning step followed by execution. Could ship as a separate workflow variant (PlanExecuteWorkflow).
Why this matters
ReAct interleaves planning and execution; Plan-and-Execute separates them. For tasks where the plan is mostly stable (e.g. ""book a flight""), separation yields better LLM behavior and easier replay analysis.
Why not scheduled
The ReAct loop covers most use cases. Plan-and-Execute is worth adding once we see concrete tasks where ReAct under-performs.
Open questions
- Plan as a separate workflow or a step within
AgentWorkflow?
- How to handle plan revision when execution surprises occur?
Status: Future idea, not scheduled. Lives in the v0.5+ ""maybe"" bucket of the roadmap.
Summary
Alternative to the ReAct loop: explicit planning step followed by execution. Could ship as a separate workflow variant (
PlanExecuteWorkflow).Why this matters
ReAct interleaves planning and execution; Plan-and-Execute separates them. For tasks where the plan is mostly stable (e.g. ""book a flight""), separation yields better LLM behavior and easier replay analysis.
Why not scheduled
The ReAct loop covers most use cases. Plan-and-Execute is worth adding once we see concrete tasks where ReAct under-performs.
Open questions
AgentWorkflow?