Junyao Yang, Yucheng Shi, Zhongzhi Li, Ruhan Wang, Zongxia Li, Haitao Mi, Leowei Liang
37 pages, 18 figures
A 122B MoE model post-trained with reinforcement learning on executable terminal tasks, using TITO and rollout routing replay to stabilize MoE training and a dense per-assertion verifier reward, raises Terminal-Bench 2.1 performance from 43.8% (base) or 49.4% (SFT) to 64.0%, placing it near or above much larger frontier models, and reaches 27.9% on Long-Horizon Terminal-Bench.
Post-training of Qwen3.5-122B-A10B with PPO across three epochs on ~15,000 synthesized terminal tasks executed in real cloud sandboxes (up to 300+ tool-call turns per task), evaluated on three held-out execution-scored benchmarks: Terminal-Bench 2.1 (89 tasks), Long-Horizon Terminal-Bench, and Terminal-Bench Hard, against GPT-5.4, Claude Opus 4.6/4.7, DeepSeek-V4-Flash/Pro and Gemini-3.1-Pro under an identical agent harness.
On Terminal-Bench 2.1: base 43.8% to 64.0% resolved, a 28.5% relative gain from RL alone over the 49.4% SFT checkpoint, beating GPT-5.4 (54.8%), DeepSeek-V4-Flash (56.9%) and Claude Opus 4.6 (63.8%), just short of Claude Opus 4.7 (66.1%). On Long-Horizon Terminal-Bench: 27.9%, matching Gemini-3.1-Pro. Terminal-Bench Hard: 38.0%. Domain gains are uneven (100.0% debugging, 88.9% system administration) and concentrated on Medium-difficulty tasks; training-inference log-probability gap cut from 0.021 to 0.013 with zero token drift in the loss region.
The authors concede: conditioning is exact only up to re-tokenized history; no single-axis reward ablation exists so the contribution of dense reward versus TITO/R3 is unattributed; verifier integrity is filtered by an LLM audit rather than enforced; the long tail is paid for twice (straggler rollouts plus repeated compute); data-distribution skew (top five categories are 67.9% of the pool, debugging only 1.3%) predicts where residual failures land; staleness/asynchrony and reporting gaps remain; scope is limited to terminal tasks. Unstated: Terminal-Bench 2.1 has only 89 tasks, so headline differences of a few points sit on very small effective samples; the binary-reward campaign never beat its supervised baseline, so the pipeline's headline depends on the dense-reward variant on curated data.
A fair skeptic would note the 89-task evaluation set makes GPT-5.4 versus T1 differences statistically fragile; synthesized training tasks and the evaluation both come from the RST synthesis lineage, so the claimed out-of-distribution guarantee rests on the authors' own seed-disjointness and LLM audit rather than independent verification; the harness, verifier filtering, and reward design are all self-controlled and could still leak task-specific advantage; comparison numbers for frontier competitors are produced by the authors under one harness with no independent replication; and dense partial-credit rewards invite subtle reward farming that the authors mitigate by monitoring, not proving, absence.
Little or nothing yet for the AI economy in the next 12 to 24 months as a direct read, but one signal matters: a mid-sized open-lineage MoE model (122B total, ~10B active) trained by RL on executed verifiable outcomes reaches near-frontier terminal-agent performance, which, if replicated, supports falling capability-per-dollar at the agent layer and intensifying model commoditization from below.
Technical Capability: Engineers and researchers building agents should care that the paper shows executable, per-assertion verification rewards plus training-inference consistency fixes are what unlock long-horizon RL, while binary outcome rewards failed to beat the SFT baseline.
Market & Valuation: Investors should note the claimed compression of frontier-versus-mid-size gaps on agentic terminal benchmarks, which bears on how long frontier-lab pricing power lasts.
Labor & Knowledge Work: If terminal autonomy genuinely improves, the software-engineering task surface (debugging, sysadmin, packaging) moves closer to automation, though one benchmark paper is far from labor-market evidence.