Skip to content
Agents tracked: 258 Downloads (7d): 219M up 6.1% GitHub stars: 5.5M VS Code installs: 148M Releases (7d): 293 Agent status: 2 with issues Updated Oct 7, 2026
Showcase Weave

Route between coding-agent models with the open-source Weave Router 2.0

The Weave team presented Weave Router 2.0 in a Show HN post. It is an open-source routing model that sits in front of coding agents and switches between LLMs per turn, and the authors say it matches the pass rate of a single frontier model at lower cost and with faster completion.

The problem

Coding agent sessions can involve around 100 LLM calls, and each call is a chance to pick a different model. Using one top model for everything is expensive, and switching models carelessly wastes money because each switch means filling a different prompt cache. The team wanted a router that could pick the right model per turn without exploring every possible path.

How they did it

  1. Plug the Weave Router into a coding agent harness such as Claude Code, Codex, OpenCode or Pi.
  2. Choose between self-hosting the open-source router from GitHub and the hosted version at weaveos.com/router.
  3. For self-hosting, supply provider access; OpenRouter is suggested as an easy start but is not required.
  4. Let the router send hard tasks such as tricky debugging to a strong model and simple frontend changes to a cheaper one.
  5. Optionally set a predefined budget, which the author confirmed is supported.

Results

  • As reported by the Weave author on Hacker News: on Terminal Bench 4.0 and SWE Atlas, the router had equivalent pass rates to GPT-6 Astra.
  • As reported by the author: on Terminal Bench the router cost 52% as much as Astra and completed tasks 2.2x faster.
  • As reported by the author: on SWE Atlas the router cost 54% as much as Astra and ran 2.5x faster.
  • The author credits a hidden Markov model plus classifier for bucket selection as the biggest gain, and cache-eviction impact estimation for most of the cost savings.

As reported by the source (Hacker News Show HN post by the Weave Router author); AgentGid did not measure these figures.

Takeaway. If you run coding agents at scale, a router that weighs model capability against the cost of switching caches may reduce spend without lowering pass rates, but test it on your own workloads since the figures are self-reported.
AgentGid's take

This suits developers or small teams already running a terminal coding agent with provider keys, and comfortable self-hosting a router or trying the hosted one. Watch the figures: the pass-rate and cost numbers come from the author, and your savings depend on provider pricing and your own task mix. Pi (Free, OSS) is a no-cost harness to pair it with, since you only pay the model provider.

The agents used here

Compare: Claude Code vs OpenAI Codex · Claude Code vs OpenCode · Claude Code vs Pi · OpenAI Codex vs OpenCode

Similar use cases

Guides