A single-prompt LLM call has no planning โ it generates an answer in one shot. An agent, by contrast, needs to decompose tasks, decide on a sequence of actions, adapt when things go wrong, and know when it's done. These planning architectures are the core of what separates a useful agent from an expensive LLM wrapper.
The three planning architectures
โก ReAct (Reason + Act)
The agent alternates between reasoning ("what should I do next?") and acting (calling a tool or producing output). After each action, it receives an observation and reason-acts again. Simple, effective, and the default for most agent frameworks.
๐ณ Tree of Thought (ToT)
Instead of committing to one reasoning path, the agent explores multiple branches simultaneously, evaluates them, and selects the most promising. Much better on tasks requiring search or creativity. More expensive โ typically 3โ10ร the tokens of ReAct.
๐ Plan-and-Execute
A planner LLM call first decomposes the task into an ordered list of steps. An executor agent then works through the steps sequentially, with optional re-planning if steps fail. Better structure than ReAct for long-horizon tasks; easier to debug.
Plan-and-Execute implementation
Choosing the right architecture
- Start with ReAct โ it's the simplest and works well for the majority of tool-using tasks. Only upgrade when you hit its limitations.
- Use Plan-and-Execute when tasks have 5+ steps, involve multiple tools, or need to be auditable (the plan is inspectable before execution).
- Use Tree of Thought sparingly โ reserve for tasks where exploring multiple options genuinely improves quality and cost is not the primary constraint.
- Hybrid approaches work well: Use ReAct within each step of a Plan-and-Execute architecture for the best of both worlds.
All three planning architectures on MoltBot
ReAct, Plan-and-Execute, and Tree of Thought โ configurable per agent. 14-day free trial.
Start Free Trial โ