What is ReAct prompting?
ReAct stands for **Rea**soning + **Act**ing. The model is prompted to alternate between two modes: generating reasoning (a Thought) and taking an action in the world (an Action), then reading what the action returns (an Observation). It repeats this cycle until it can produce a final answer. The pattern was named and formalized by Yao et al. 2022.
The reason it works is grounding. Pure chain-of-thought reasons in a vacuum — if the model misremembers a fact, the whole chain is built on sand. ReAct lets the reasoning trigger a real lookup (a web search, a database query, a calculator), so the next Thought is conditioned on a true Observation rather than on the model's guess. Reasoning steers which actions to take; observations correct the reasoning.
In modern stacks, ReAct is implemented through function calling or tool use rather than freeform text. The model emits a structured tool call, the runtime executes it and returns the result, and the model continues. The Model Context Protocol (MCP) is one common way to expose tools — see tool use and MCP for production LLM systems. Conceptually it is still Thought, Action, Observation.