PHI
Startup Intelligence
Markets
  • Signal Feed
  • Startups
  • Categories
  • Founders
  • Revenue
  • Beyond the launch
Intelligence
  • Content Desk
  • Editorial QA
  • Ask Market
  • Signature Index
  • Trends
Lab
  • Metric Bench
  • Tagline Lab
  • Smart Search
Yours
  • Watchlist
  • Alerts
  • Search
PHI
Sync
PHI
Startup Intelligence
Markets
  • Signal Feed
  • Startups
  • Categories
  • Founders
  • Revenue
  • Beyond the launch
Intelligence
  • Content Desk
  • Editorial QA
  • Ask Market
  • Signature Index
  • Trends
Lab
  • Metric Bench
  • Tagline Lab
  • Smart Search
Yours
  • Watchlist
  • Alerts
  • Search
Sync now
/
17,045 products · 82,562 snapshots
Weave Router 2.0

Weave Router 2.0

Strong signal

Subscription aware coding agent router

Launched 1mo ago
Signal
74
Velocity
3

What this means

Decaying
Vote pace down to 3% of launch speed.
60%Strong buyer-intent signal in the discussion.
60% of commenters sound like potential buyers — mostly developers.
Users are asking for custom cost caps + VS Code extension.
Feature requests surfaced from the comment thread.
Recurring concerns: lack of unique features, unclear model decision process.
Pain points raised more than once by different people.

Prediction

Top-5 finish probability
22%
today
Projected end-of-day votes
338range 254–456
Trajectory
decaying
Vote pace down to 3% of launch speed.

About

Use Claude models in Codex and GPT models in Claude Code on your existing plans, routed to whichever has quota left. Weave Router 2.0 routes each coding agent request to the cheapest model that can get it right. On Terminal-Bench 4.0 and SWE-Atlas it matches GPT-6 Astra at half the cost, 2x faster. Powered by a new classifier that scores task complexity and cache-aware switching that only moves when savings beat the rebuild cost.

AI Summary

Weave Router 2.0 is an AI-driven coding agent router that optimizes model usage by routing requests to the most cost-effective option based on available quotas. It offers performance comparable to GPT-6 Astra at half the cost and twice the speed, utilizing advanced task complexity classification for efficient resource allocation.

Attention & discussion velocity

Performance

Velocity3
Vote pace vs average
Momentum3
Sustained over 6h
Virality8
Spread × engagement
Engagement27
Discussion per unit of attention

Signal sources

3 of 6 active
  • Launch tracking9 readings since we picked it up
  • AI analysisDeveloper Infrastructure
  • Comment intelligencethread analysed
  • Outside discussionnot checked — domain is a storefront or shared
  • Revenue signalsno match on this domain
  • Editorial scoringbelow the signal threshold for this pass

A source that found nothing is a measurement. A source that has not run is a gap. Neither means the launch lacks the thing.

Founders

Andrew Churchill
Andrew Churchill
@adchurch
rep 67
Adam Cohen
Adam Cohen
@adambcohen
rep 67
Drew Bailey
Drew Bailey
@drew_bailey
rep 67
Steven
Steven
@steventohme
rep 67
Brennan Lupyrypa
Brennan Lupyrypa
@brennan_lupyrypa
rep 67
Ben Lang
@benln · hunter

Topics

Developer ToolsArtificial IntelligenceOpen Source

Comment Intelligence· 21 comments analysed

Sentiment

Positive65%
Neutral25%
Negative10%
Buyer intent
60%
of commenters sound like potential buyers
Audience
developers
Sentiment over 58 days
Positive
Negative
Buyer intent
Overall vibe

Overall, the comments reflect a positive reception with interest in cost-saving features and workflow improvements.

Top themes
  • cost optimization
  • workflow improvement
  • model selection
Feature requests
  • custom cost caps
  • VS Code extension
  • visibility into quota savings
Complaints
  • lack of unique features
  • unclear model decision process

Top comments

[REDACTED]
↑ 10

The Problem Coding agents send every request to one model. A one-line config change and a cross-service migration both go to the same frontier model at the same price. Teams are paying frontier rates for routine work, and the bill grows with every agent they add. Most tools in this space follow one of two flawed approaches: ❌ Gateways – They give you one endpoint and a menu of models. You still pick the model yourself, so nothing actually gets cheaper. ❌ Manual model switching – Flipping /model mid-session breaks your prompt cache, and on long sessions the re-billed context eats the savings. After running into this on our own agent traffic, we built Weave Router to solve it. How Weave Router 2.0 is Different 🚀 Weave Router plugs into Claude Code, Codex, and Cursor as a drop-in endpoint. It reads every request your agent makes, scores how hard it is, and sends it to the cheapest model that will get it right. The benchmarks We ran 2.0 head to head against GPT-6 Astra, each task run twice (pass@2). 📊 Terminal-Bench 4.0 – Tied pass rate within the confidence interval. 52% of Astra's cost. 2.2x faster. 📊 SWE-Atlas Codebase QnA – Tied pass rate within the confidence interval. 46% of Astra's cost. 2.5x faster. Full results at weaveos.com/router. 🔹 Complexity-scored routing – A new classifier trained on 10x more real agentic coding sessions routes on task difficulty, not task type. DeepSeek, GLM, and Kimi handle the simple turns. Astra and Fable handle the hard ones. 🔹 Cache-aware switching – 2.0 tracks cache state per provider and per session. It only switches models when the expected savings beat the cost of rebuilding the cache. This is where most of the cost win comes from. 🔹 Multi-subscription routing – Use Claude models inside Codex and GPT models inside Claude Code. Route by complexity, by cost, or by whichever plan still has quota this month. Who is this for? If you or your team run coding agents daily, Weave Router gets you Astra-level results at about half the cost and more than twice the speed, without changing your tools. 🔗 Get started today Try it at weaveos.com/router. Install with one command: npx @workweave/router. Source-available under Elastic License 2.0. Teams of 50+ engineers can book time with our FDEs.

[REDACTED]
↑ 4

congrats on the launch,its a great product. my question to Weave Router team is, what is the most unique feature of your product have that make it different from others products.

[REDACTED]
↑ 3

​how does weave handle token routing when multiple AI models are running together?

[REDACTED]
↑ 3

​using weave allowed our lead engineers to optimize overall workflow speed by sixteen percent.

Sentiment computed via openrouter