From 8 requests to 12,000 a week: how a new frontier model takes over a fleet

Claude Opus 5 was added to the Weave router in late July and grew from eight requests in its first week to more than 12,000 weekly requests within five weeks, reaching 10.8% of router traffic without a fleetwide manual rollout. The router uses a bandit policy that classifies requests by task type and routes them among competing models based on measured success, cost, speed, and failure patterns, allowing new models to begin with cautious traffic informed by offline evaluation and gain usage where live results justify their cost. Safety controls restrict experimentation to suitable fresh sessions, while user-selected models, designated low-cost internal tasks, and ongoing sessions remain pinned. Routing data indicated that Opus 5 became concentrated in longer, complex multi-file sessions rather than broadly distributed across users, while lower-cost models such as deepseek-v4-flash handled subagent tasks like codebase exploration. The approach frames frontier-model adoption as a continuously measured routing decision, enabling models to earn or lose traffic gradually with transparent records of each choice.

No tracked trend matches for this post yet.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.