- Source
- arXiv
- Published
- Runtime
- 0:00
- Snippets
- 4
A conversation between
Agent Lightning v1.0: Towards Harnessed Agentic RL
§02
Snippets
-
Harnessed agentic RL lets the deploy-time harness own the environment interaction loop while the trainer observes only LLM request-response pairs, flipping control from the training engine to the harness.
This paradigm shift enables training agents within their real operational constraints, but introduces new technical challenges in retokenization and loss calculation.
-
RL improved Qwen3.5-9B on SWE-bench Verified from 41.8% to 56.4% (14.6-point gain) using only 6K training examples and modest compute.
Demonstrates that harnessed agentic RL can achieve significant real-world gains with minimal resources, making agent training more accessible.
-
Agent Lightning v1.0 uses an LLM endpoint proxy to disaggregate the harness from the trainer, enabling arbitrary agents to integrate with RL in ~3,500 lines of code.
Lightweight, reproducible framework lowers barriers to experimenting with agent RL and was adopted by multiple subsequent frameworks (verl, Uni-Agent, AReaL 2.0).
-
Harnessed agentic RL introduces challenges in retokenization, sample merging, advantage calculation, loss normalization, and backend scheduling that substantially affect training stability.
Identifies concrete failure modes that practitioners must solve to scale agent RL safely and effectively.
§03
Synthesis
The Core Innovation
Traditional reinforcement learning for language models treats agents as black boxes—the RL trainer controls everything, managing tool calls and environment interaction directly. Agent Lightning v1.0 flips this architecture: the agent harness (the deployed system managing tools, context, and control flow) stays in charge of the environment loop, while the RL trainer only observes sequences of LLM request-response pairs. This "harnessed agentic RL" paradigm is simpler to deploy—you train the model the way it actually runs—but introduces new technical challenges that previous approaches glossed over.
The authors' key insight is that these challenges matter. When the harness controls interaction, the trainer faces problems like retokenization (how to handle variable-length tool outputs), sample merging (combining trajectories from different harnesses), advantage calculation (estimating value improvements), loss normalization (stabilizing gradients across variable-length sequences), and backend scheduling (efficient batching). Agent Lightning v1.0 is a 3,500-line framework that tackles these concrete problems and provides a reproducible foundation for study.
Why It Works and Why It Matters
The framework is minimal but complete. It handles arbitrary harnesses—instruction-following systems, search engines, code development agents—without baking in assumptions about task structure. The authors test it on three distinct domains and release full reproducible code for coding agents, removing a major barrier to progress in this space.
The results demonstrate both tractability and impact. On SWE-bench Verified (a real coding benchmark), RL training on Qwen3.5-9B jumps from 41.8% to 56.4% success rate—a 14.6-point absolute gain—using only 6,000 training examples and standard compute. This isn't marginal improvement; it's the kind of gain that justifies the infrastructure.
Why does harnessed agentic RL matter more than it initially appears? In production, agents live in harnesses. The agent's behavior emerges not from the model alone but from the model-plus-harness system. Training that system end-to-end, rather than treating the harness as fixed scaffolding, captures real constraints: how the model must format tool calls, how it recovers from errors, how it reasons within actual latency budgets. This alignment between training and deployment reduces sim-to-real gaps.
The paradigm has already influenced practice—the abstract notes that frameworks like verl, Uni-Agent, AReaL 2.0, and others have adopted the disaggregated architecture—but without shared understanding of the technical pitfalls. Agent Lightning v1.0 centralizes that knowledge and provides a testbed. Future work can focus on the hard problems: better advantage estimators for long-horizon tool use, efficient sample merging across heterogeneous harnesses, or handling distribution shift when harness behavior changes.
The release of reproducible code is crucial. Agentic RL remains a young field where many results don't reproduce and infrastructure dominates the barrier to entry. By opening the full pipeline and training scripts, the authors lower that barrier and create a shared reference point for the community.
Mine your own.
Lode is a workbench, not a feed. Paste a YouTube URL. The model proposes a transcript, a set of quote-grounded snippets, a synthesis essay, and the fan-out. You decide what stays.