Agents-A1 proves you can match trillion-parameter agents with 35B and longer horizons

Shanghai AI Lab's 35B MoE agent reaches trillion-parameter benchmark territory by scaling trajectory length to 45K tokens and distilling six domain teachers. Here's what agent-horizon scaling actually means.

SaifullahSaifullah
3 min read
Agents-A1 proves you can match trillion-parameter agents with 35B and longer horizons

The default move in frontier AI for the last year was simple: make the model bigger. Kimi-K2.6 and DeepSeek-V4-pro sit in the trillion-parameter class and top the hard agent benchmarks.

Agents-A1 from InternScience (Shanghai AI Lab) makes the opposite bet. It is a 35B Mixture-of-Experts model with roughly 3B active parameters per token, initialized from Qwen3.5-35B-A3B. On several long-horizon agent benchmarks, it matches or beats those trillion-parameter systems.

The thesis, straight from the paper title: scale the horizon, not the parameters.

What agent-horizon scaling means

Agent work is not primarily about knowing more facts. It is about sustaining a plan across dozens of tool calls, web searches, code edits, and verifier checks without losing the thread.

Agents-A1 trains on trajectories averaging 45,000 tokens. The infrastructure connects external knowledge, actions, observations, and verifier outcomes into long-horizon sequences across six domains: long-horizon search, engineering, scientific research, instruction following, general agentic tasks, and scientific agentic tasks.

Agents-A1 on Hugging Face

Three-stage training recipe

StageWhat happens
Full-domain SFTAlign base model with broad agentic behaviors across all six domains
Domain teacher modelsTrain specialized teachers per domain
Multi-teacher on-policy distillationRoute domains through teachers, distill into one deployable 35B student with salient vocabulary alignment

Full-domain SFT alone was not enough. It improved long-horizon search and scientific research but regressed on general agent tasks and instruction following. The multi-teacher distillation step is what unified heterogeneous domains without catastrophic interference.

Agents-A1 training pipeline from 45K token trajectories through domain teachers to unified 35B student

Benchmark results that matter

Agents-A1 reports leading or highly competitive numbers against GPT-5.5, DeepSeek-V4-pro, and Kimi-K2.6:

BenchmarkAgents-A1Notes
SEAL-056.4Overall SOTA claim
IFBench80.6Instruction following
HiPhO46.4Physics olympiad
FrontierScience-Olympiad79.0Science reasoning
FrontierScience-Research40.0Research tasks
BrowseComp75.5Web search agent
GAIA96.0General agent
HLE (with tools)47.6Hard reasoning

It does not win everywhere. GPT-5.5 still leads BrowseComp (84.4) and engineering tasks like SciCode (56.1). DeepSeek-V4-pro tops GAIA (98.1). The honest read is parity in the frontier band with clear leads in science and instruction following, from a model you can serve on a fraction of the hardware.

Agents-A1 paper on Hugging Face Papers

Why this matters for applied AI teams

If a 35B model with 3B active parameters can sit in the same benchmark band as trillion-parameter agents, the interesting frontier shifts from "how big" to "how long and how varied the training trajectories are."

Practical implications:

  • Serving cost drops. You do not need a trillion-parameter cluster for competitive long-horizon agent behavior.
  • Training data design matters more. 45K-token trajectories with verifier outcomes are the moat, not parameter count.
  • Benchmarks are not production. SOTA on BrowseComp does not mean your messy CRM integration agent will work. Always run your own eval.
Parameter count versus agent horizon length showing Agents-A1 competitive zone against trillion-parameter models

Caveats I would keep in mind

The "trillion-parameter performance" framing rests on benchmark parity, not a fitted scaling law. MoE routing details and expert counts are not fully disclosed. And benchmark SOTA is not the same as robustness in a production loop with stale tools, rate limits, and angry users.

Still, the direction is clear. If you are building agents and assuming you need the biggest model on the menu, Agents-A1 is worth a serious look at your own eval set.

Want help designing long-horizon agent evals or picking a model tier for your workflow? Book a free discovery call.

Share this post

Related posts