LLM reasoning / chain-of-thought

ReAct

ReAct: Synergizing Reasoning and Acting in Language Models

Superseded baseline#7 of 772 most-superseded · first seen Oct 6, 2022

Superseded — cited as a baseline and beaten by newer methods

5 papers critique it · 3 beat it on benchmarks

What papers say

Verbatim critique sentences, each from a paper that cites ReAct as a baseline.

In our initial experiments with ReAct for planning, we found that the system is overly dependent on the syntactic similarity of the example prompt and the query and is extremely brittle to minor perturbations to the input prompt.
On the Brittle Foundations of ReAct Prompting for Agentic Large Language Models
agent behavior is typically static at inference time: the model follows a fixed prompt-guided policy, while feedback gathered during deployment is not used to systematically improve future decisions
OLIVIA: Online Learning via Inference-time Action Adaptation for Decision Making in LLM ReAct Agents
However, the REACT approach does not tackle efficiency in the second stage, relation modeling.
REACT++: Efficient Cross-Attention for Real-Time Scene Graph Generation
we demonstrate that CoT and its reasoning variants (e.g., ToT, ReAct) consistently underperform direct answering by a significant margin
The Curse of CoT: On the Limitations of Chain-of-Thought in In-Context Learning
The dominant approach for orchestrating tool usage relies on reactive, step-by-step reasoning frameworks like ReAct, often augmented by self-reflection techniques. However, this paradigm suffers from inherent local optimization traps due to its incremental decision-making process. While potentially effective for simple queries, its reactive nature often falters on complex tasks.
Beyond ReAct: A Planner-Centric Framework for Complex Tool-Augmented LLM Reasoning

Beaten on benchmarks

Head-to-head results where a newer method reports beating ReAct. Values are copied from the source paper's tables — verify against the cited paper.

What to use instead

Recent methods in the same sub-problem, not yet superseded in the knowledge base — arXiv benchmark leaders, not vetted production recommendations.