Overview
NeoHorse-1-9B is the larger of the two open-weight models TokenRhythm published on 7 September 2026, with the technical report following on 9 September. It is a post-trained model rather than a new pretraining run: TokenRhythm started from Qwen3.5-9B-Base and fine-tuned it on data produced by its own agent infrastructure.
That method is the point of the release. The report — "NeoHorse-1: Towards Recursive Self-Improvement via Agentic Post-Training with Routing Harness" (arXiv 2609.08183) — describes routing agent work across a heterogeneous pool of models, then turning the resulting interaction records into training examples for a smaller model. On TokenRhythm's ten-benchmark macro average the 9B model reaches 69.04 against 65.60 for the Qwen3.5-9B base it was trained from.
The gains are concentrated in agent work rather than spread evenly. PinchBench moves from 74.55 to 82.25 and VitaBench from 31.25 to 42.25, while LiveCodeBench v6 (65.14) and IFBench (66.33) are unchanged from the base and IFEval slips slightly, from 89.46 to 89.09. In TokenRhythm's published table the model leads all six columns on QwenClawBench, PinchBench, BFCL v4, tau2-Bench and the overall average, but trails Gemma-4-12B-it and Muse-Glimmer-30B on instruction following.
It keeps the base model's 262,144-token native context, documented as extensible to 1,010,000 tokens, and is served like any Qwen 3.5 derivative: SGLang or vLLM behind an OpenAI-compatible endpoint, with the qwen3 reasoning parser and the qwen3_coder tool-call parser. Weights are Apache-2.0 on Hugging Face and ModelScope, with GGUF and MLX builds for local use.
| Released | 2026-09-07 |
|---|---|
| License | Apache-2.0 |
| Weights | Open weights |
| Parameters | ≈9B |
| Context | 262,144 tokens (extensible to 1,010,000) |
| Architecture | Causal transformer post-trained from Qwen3.5-9B, BF16 safetensors |
| Modalities | Text |
| Status | Generally available — Apache-2.0 weights on Hugging Face and ModelScope, with GGUF and MLX quantisations |
Benchmarks
TokenRhythm's published 9B comparison, as printed on the NeoHorse-1-9B model card
| Benchmark | NeoHorse-1-9B | Qwen3.5-9B | Ornith-1.5-9B | Gemma-4-12B-it | Muse-Glimmer-30B | Granite-4.2-8B |
|---|---|---|---|---|---|---|
| QwenClawBench | 48.73 | 44.04 | 47.27 | 43.53 | 46.11 | 37.01 |
| WorkBuddy Bench | 40.15 | 39.6 | 29.29 | 29.65 | 45.85 | 35.07 |
| PinchBench | 82.25 | 74.55 | 68.22 | 58.89 | 71.35 | 56.93 |
| VitaBench | 42.25 | 31.25 | 26.75 | 36.5 | 48.5 | 23 |
| BFCL v4 | 67.43 | 64.88 | 65.03 | 62.06 | 53.74 | 52.06 |
| tau2-Bench | 90.82 | 88.04 | 83.68 | 59.37 | 76.64 | 62.28 |
| HumanEval | 98.17 | 92.68 | 93.9 | 100 | 98.17 | 96.34 |
| LiveCodeBench v6 | 65.14 | 65.14 | 47.43 | 73.14 | 65.71 | 72 |
| IFBench | 66.33 | 66.33 | 40 | 77.67 | 78.67 | 78 |
| IFEval | 89.09 | 89.46 | 71.35 | 94.27 | 93.9 | 92.98 |
| Ten-benchmark average | 69.04 | 65.6 | 57.29 | 63.51 | 67.86 | 60.57 |
This model's scores
- tau2-Bench90.82%
- IFEval89.09%
- HumanEval98.17%
- PinchBench82.25%
- Ten-benchmark average69.04%
- BFCL v467.43%
- IFBench66.33%
- LiveCodeBench v665.14%
- QwenClawBench48.73%
- VitaBench42.25%
- WorkBuddy Bench40.15%
Scores on a 0–100 scale (25-point gridlines); higher is better. Each benchmark links to its published source.
Strengths
- Leads TokenRhythm's published comparison on the ten-benchmark average with 69.04, ahead of Muse-Glimmer-30B (67.86) and Qwen3.5-9B (65.60)
- Strong tool-use and agent-harness scores: 90.82 on tau2-Bench, 82.25 on PinchBench and 67.43 on BFCL v4
- 262,144-token native context, documented as extensible to 1,010,000 tokens
- Apache-2.0 weights on Hugging Face and ModelScope, plus GGUF and MLX quantisations for local runs
- Drops into an existing Qwen 3.5 serving stack — SGLang or vLLM with the qwen3 reasoning and qwen3_coder tool-call parsers
Best for
- Self-hosted agent harnesses that need tool calling and multi-step task execution on a single node
- Replacing a hosted mid-size model in a tool-heavy pipeline where weights must stay on your own hardware
- Long-context agent runs — browser or repository work — that would be costly to send to a frontier API
- Reproducing or extending the agentic post-training recipe from the NeoHorse-1 report on your own task mix
How to access
| Provider | Model ID |
|---|---|
| Self-hosted (SGLang) ↗ | neohorse-1-9B |
| Self-hosted (vLLM) ↗ | neohorse-1-9B |
NeoHorse — every version
The full lineage of the NeoHorse line, newest first. Every version has its own page — click any to compare specs, benchmarks and pricing.
| Version | Released | Context | License |
|---|---|---|---|
| NeoHorse-1-9Bcurrent | 2026-09-07 | 262K | Apache-2.0 |
| NeoHorse-1-4B | 2026-09-07 | 262K | Apache-2.0 |
FAQ
What is NeoHorse-1-9B based on?
The model card lists Qwen/Qwen3.5-9B as the base model: NeoHorse-1-9B is a post-trained derivative, not a model pretrained from scratch. It inherits the base architecture, the 262,144-token context and the Qwen 3.5 serving path, including the qwen3 reasoning parser and the qwen3_coder tool-call parser.
What does "agentic post-training with a routing harness" mean?
The NeoHorse-1 report (arXiv 2609.08183) describes routing agent tasks across a heterogeneous pool of models, recording how the work was actually carried out, and converting those interaction records into training examples. The model is then trained on that harvested data, which is why the gains show up mainly on agent and tool-use benchmarks.
How much better is it than the Qwen3.5-9B base?
On TokenRhythm's ten-benchmark macro average, 69.04 against 65.60 — a gain of 3.44 points. It is uneven: PinchBench gains 7.70 points and VitaBench 11.00, while LiveCodeBench v6 and IFBench are identical to the base and IFEval is 0.37 lower.
How do I run NeoHorse-1-9B?
The repository documents two paths. With SGLang: `python3 -m sglang.launch_server --model-path "$MODEL_PATH" --served-model-name neohorse-1-9B --context-length 262144 --reasoning-parser qwen3 --tool-call-parser qwen3_coder`. With vLLM: `vllm serve "$MODEL_PATH" --served-model-name neohorse-1-9B --max-model-len 262144`. Both expose an OpenAI-compatible /v1/chat/completions endpoint.
Is there a smaller version?
Yes — NeoHorse-1-4B, released the same day and post-trained from Qwen3.5-4B. It shows the larger relative jump of the pair (58.94 to 64.87 on the ten-benchmark average) but scores below the 9B on most individual benchmarks.