Flashcard: in the agent loop, what counts as an 'action' and how is it different from a thought?

**An action** in an agent loop is a step that actually does something in the world: calling a tool, querying a database, running code, sending an email, clicking a button. **A thought** is the model's internal reasoning, the text it writes to plan or explain its next move. Both come out of the same LLM call, but only actions cause real effects. The distinction comes from the ReAct pattern, which made the difference explicit. In ReAct, the model alternates between two kinds of output. First it writes a thought, like "I need to find out the user's recent orders before answering." Then it emits an action, like a tool call to the order database. The runtime intercepts the action, executes it, and feeds the result back as an observation. The cycle repeats: thought, action, observation, thought, action, observation. Why the split matters. The model's reasoning text is useful for debugging and for guiding its own next decision, but it does not affect the outside world. The action is the part that does. By making the structure explicit, the runtime knows which parts to actually execute and which parts to just log. In modern function-calling APIs, the action is the structured tool-use block in the response. Everything else (reasoning, partial answers, planning) counts as a thought.

**An action** is a step that affects the world or fetches new information. Calling a tool, querying a database, running code, sending a message, executing a shell command. **A thought** is internal reasoning the model writes for itself before deciding what action to take. The distinction comes from the ReAct (Reason + Act) pattern, introduced in 2022. Earlier agent designs interleaved reasoning and tool use implicitly; ReAct made the structure explicit. The model alternates: thought, action, observation, thought, action, observation. The thought is plain text. The action is a structured tool call the runtime can parse and execute. The observation is whatever the tool returned. This explicit interleaving made trajectories debuggable and gave the runtime a clean place to intercept and execute actions. In modern function-calling APIs, the structural distinction is encoded directly. Anthropic returns content blocks of type `text` (thoughts) and `tool_use` (actions). OpenAI returns assistant messages with optional `tool_calls`. Both providers treat the tool-call block as the action; the surrounding prose is reasoning the runtime forwards to the conversation but does not execute. The model itself decides what to emit on each turn: an action means "runtime, please do this"; no action means "I am done" or "I am still thinking." Why the split matters practically. Actions have side effects, latency, and cost; thoughts are free in comparison. Actions need permission checks, idempotency keys, and audit logging; thoughts only need to be logged for trace inspection. Conflating them is the root of most beginner mistakes in agent design.