Why 'Next-Token Predictor' Is the Wrong Mental Model for LLMs
Calling an LLM a “next-token predictor” isn’t wrong—it’s incomplete. That framing describes the mechanism (autoregressive token generation) but ignores what post-training encodes: simulation of a helpful assistant and knowledge discovered through exploration.
The Training Loops
Pre-training is indeed next-token prediction:
for tokens in training_data:
for position in range(1, len(tokens)):
prior_tokens = tokens[:position]
actual_next_token = tokens[position]
model.make_more_likely(actual_next_token, after=prior_tokens)
But modern LLMs undergo RLVR (reinforcement learning with verifiable rewards), which looks different:
for task in training_tasks:
for explored_tokens in model.explore(task):
reward = evaluate_outcome(task, explored_tokens)
for position in range(len(explored_tokens)):
prior_tokens = task + explored_tokens[:position]
explored_next_token = explored_tokens[position]
model.make_more_likely(explored_next_token, after=prior_tokens, according_to=reward)
During RLVR, the model generates new sequences and learns from outcomes—never seen in training data. That’s fundamentally different from just imitating existing text.
Chess Analogy
Think of two chess systems. One trained only on grandmaster games predicts the most likely next move—a next-move predictor. Another exhaustively explores all possible games, knows win probability from every position, and picks the move that maximizes winning. Calling the second a “next-move predictor” would be strange—it’s trying to win, not to imitate.
Why It Matters
RLHF also shifts models away from imitation toward helpful-assistant simulation. RLVR goes further, enabling exploration beyond training data. So “next-token predictor” describes the shape but ignores what the loop encodes. A simulation of a helpful assistant and discovered knowledge both fit in the same autoregressive loop—but that’s not all they are.
📖 Read the full source: HN AI Agents
👀 See Also

NVIDIA announces NemoClaw with OpenShell security features
NVIDIA announced NemoClaw at GTC, building on OpenClaw to add enterprise-grade security through OpenShell, which enforces policy-based privacy and security guardrails for AI agents.

OpenClaw 2026.3.22-beta.1: Key workflow changes for plugin authors and browser automation
OpenClaw 2026.3.22-beta.1 changes plugin installation to prefer ClawHub over npm, removes the Chrome extension relay, consolidates image generation, and introduces breaking changes to the Plugin SDK.

Block's 4,000 Job Cuts Raise AI-Washing Concerns
Block announced 4,000 job cuts that have sparked suspicions of AI-washing, with the story generating 10 points and 3 comments on Hacker News.

Manifest adds GitHub Copilot as fourth AI provider for OpenClaw routing
Manifest now supports routing OpenClaw requests through GitHub Copilot subscriptions, joining Anthropic, OpenAI, and Minimax as available providers. This allows developers to use their existing Copilot plans for code tasks through models built for development.