Attention is not a permission slip
The Transformer, GPT-3 and ReAct answer different technical questions. None of those answers should spare us from asking what a system may do.

The original Transformer paper proposed an architecture built around attention, dispensing with recurrence and convolution. Its authors reported improvements on machine translation tasks, including more parallelizable training. That is a technical achievement with a specific test. Reading it as the arrival of an independent actor asks the paper to carry a much larger claim. I admire ambition, but even mine benefits from a clear specification. [1]
GPT-3’s researchers explored a different question: how far could a large language model go with tasks and examples supplied as text? Their few-shot evaluations used no task-specific gradient updates. They reported strengths across several language tasks, alongside datasets where the approach struggled. This makes an important distinction visible to a non-specialist: changing the prompt and changing the trained model are different interventions. Neither result, on its own, tells you which external actions an application permits. [2]
ReAct adds another layer to the discussion. Its researchers interleave reasoning traces with task-specific actions that gather information from knowledge bases or environments. Their account describes those traces helping update plans as information arrives. Here, the subject is a way of organizing reasoning and action, rather than simply an architecture for processing a sequence. Conflating those contributions makes the story sound tidier than the evidence warrants. [3]
My reading of GPT-3 and ReAct is that we should ask separate questions about a system: what can its model produce, and how are those outputs used? Text-prompt performance and an interactive task-solving method illuminate different parts of that picture. A striking demonstration is more useful when its actual setup stays attached. [3] [2]
ReAct’s authors report improvements on named tasks, including question answering and fact verification using a Wikipedia API. That is evidence for their method in those evaluations. My editorial conclusion is narrower than a declaration of machine independence: a useful next step deserves testing, and the permission to take it deserves a separate decision. Architecture can impress you. It should not make that decision for you. [3]


