TokenRhythm's NeoHorse-1 Beats Its Base Model by 6 Points on Agentic Benchmarks

TokenRhythm fine-tunes Qwen3.5-4B with a routing harness that turns agent traces into training data, gaining 5.93 points across ten benchmarks.

·
·
TokenRhythm's NeoHorse-1 Beats Its Base Model by 6 Points on Agentic BenchmarksPRO
  • NeoHorse-1-4B is an Apache 2.0 fine-tune of Qwen3.5-4B for agents, tool use, and coding.
  • Scores 64.87 average across ten benchmarks, +5.93 over Qwen3.5-4B base.
  • Trained via routing-guided curriculum SFT and on-policy distillation from agent trajectories.
  • Native 262K context, extensible to 1M tokens, BF16 safetensors.
  • HumanEval jumps to 96.95; BFCL v4 tool-calling barely improves over base.
  • Framed as a first step toward recursive self-improvement via a routing harness.

A small Chinese lab called TokenRhythm has quietly dropped a 4B parameter model that beats its base by nearly 6 points on average across ten agentic, coding, and instruction-following benchmarks. The release frames itself as a prototype toward recursive self-improvement, where the model's own agentic behavior in a routing harness feeds back into its next training run.

NeoHorse-1-4B is a text-only fine-tune of Qwen3.5-4B released under Apache 2.0. It ships in BF16 safetensors with a GitHub repo, a technical report, and ready-to-run recipes for both SGLang and vLLM.

How the routing harness works

The central design is what the team calls a routing harness. It assigns tasks to a heterogeneous model pool, records tool interactions and outcomes, estimates capability demand, and uses capability-level feedback to shape the next training mixture. Updated models then re-enter the harness, closing an evaluation, selection, and update loop that the authors treat as a first step toward recursive self-improvement.

Concretely, the post-training pipeline combines two techniques: routing-guided curriculum SFT and routing-guided on-policy distillation. Together they convert execution trajectories into training signal while preserving execution and harness context around each response. Think of it as harvesting the model's own agent runs, filtering them by where the router says the fleet is weakest, and feeding those filtered traces back as supervised examples with the surrounding tool state intact.

Pro article

This story is for Pro members

You've reached the end of the free preview. Upgrade to AlphaSignal Pro to read the full article - and everything else behind the paywall.

Trending
  • No trending articles

Comments

avatar

Next Reads