--- title: Routing subagents to different models saves tokens and... description: Multiple AI coding tools are independently converging on the same cost-saving pattern: run the orchestrator on a powerful model but route subagents to cheaper... canonical: https://daily.dev/posts/routing-subagents-to-different-models-saves-tokens-and-improves-results-jhewcyrth twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Routing subagents to different models saves tokens and improves results | daily.dev og:description: Multiple AI coding tools are independently converging on the same cost-saving pattern: run the orchestrator on a powerful model but route subagents to cheaper... og:url: https://daily.dev/posts/routing-subagents-to-different-models-saves-tokens-and-improves-results-jhewcyrth og:image: https://api.daily.dev/og/posts/jHewCYRth.png og:image:alt: Routing subagents to different models saves tokens and improves results og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Routing subagents to different models saves tokens and improves results **[Collections](https://daily.dev/sources/collections)** · 2 min read · 1 upvotes · 0 comments ## Summary Multiple AI coding tools are independently converging on the same cost-saving pattern: run the orchestrator on a powerful model but route subagents to cheaper or faster models for simpler tasks. Claude Code supports setting CLAUDE_CODE_SUBAGENT_MODEL to send subagents to a different model than the main agent, which one developer used to cut usage significantly. opencode2 recently added per-subagent model selection, useful for pulling in a smarter model just for code review. Vercel's v0 goes further, mixing models and reasoning budgets across a pipeline (e.g. Claude for planning, Grok for execution) without needing special server-side routing - the orchestrating model itself decides which subagent to spawn and how to configure it. The shared principle: match reasoning effort to task complexity to cut costs without much quality loss. ## Content A few teams have landed on the same trick independently: run your orchestrator on a powerful model, but route subagents to something cheaper or faster. The pattern shows up in a few different tools right now. **Claude Code** lets you set `CLAUDE_CODE_SUBAGENT_MODEL=opus` to send subagents to Opus instead of whatever the main agent is using. Lydia Hallie found this cut her usage significantly on Claude 5.1 - the orchestrator spawns subagents constantly, but most of them don't actually need frontier-level reasoning. **opencode2** added optional per-subagent model selection in a recent release. The practical use case there is pulling in a smarter model specifically for code review, while keeping the main loop on something faster. **v0 / Vercel's setup** takes this further by letting you mix models and reasoning budgets across the whole pipeline. The example Guillermo Rauch gave: Claude planning, Grok executing. One model thinks carefully about what needs to happen, another just does it quickly. You steer the whole thing conversationally and can interrupt whenever you want. What's interesting about the Vercel approach is that it doesn't require any special server-side routing infrastructure. The orchestrating model just... decides which subagent to spin up and with what configuration. It's the model's own ability to follow instructions doing the work. The general principle is the same across all three: not every step in an agentic workflow needs your most capable model. Matching reasoning effort to task complexity is an easy way to cut costs without giving much up. ## Questions this post answers ### How do I make Claude Code use a different model for subagents than the main agent? Set the environment variable CLAUDE_CODE_SUBAGENT_MODEL to the desired model, such as opus, to route subagents to that model while the main orchestrator agent uses whatever model it's already running on, such as Claude 5.1. This lets you keep frontier-level reasoning only for the orchestrator while cheaper subagent calls handle simpler spawned tasks. _daily.dev surfaces practical configuration tricks like this for developers tuning agent costs._ ### Does opencode support using different models for different subagents? Yes, opencode2 added optional per-subagent model selection in a recent release. A common use case is assigning a smarter model specifically to code review subagents while keeping the main orchestration loop on a faster, cheaper model for everyday steps. _Developers picking agent frameworks compare feature updates like this one on daily.dev._ ### What models does Vercel's v0 use for planning versus execution in agent pipelines? Vercel's v0 setup, as described by Guillermo Rauch, uses Claude for planning and Grok for executing, mixing models and reasoning budgets across a pipeline without requiring special server-side routing infrastructure. The orchestrating model itself decides which subagent to spin up and how to configure it, and the whole process can be steered conversationally and interrupted at any time. _Teams choosing between agent orchestration setups follow tool comparisons like this on daily.dev._ --- Tags: [#llm](https://daily.dev/tags/llm), [#ai-agents](https://daily.dev/tags/ai-agents), [#claude-code](https://daily.dev/tags/claude-code), [#opencode](https://daily.dev/tags/opencode) [View this post on daily.dev](https://daily.dev/posts/routing-subagents-to-different-models-saves-tokens-and-improves-results-jhewcyrth) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Routing subagents to different models saves tokens and improves results","url":"https://daily.dev/posts/routing-subagents-to-different-models-saves-tokens-and-improves-results-jhewcyrth","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/routing-subagents-to-different-models-saves-tokens-and-improves-results-jhewcyrth"},"datePublished":"2026-09-16T15:53:43.121Z","dateModified":"2026-09-16T15:54:31.310Z","description":"Multiple AI coding tools are independently converging on the same cost-saving pattern: run the orchestrator on a powerful model but route subagents to cheaper...","image":"https://pbs.twimg.com/media/HSWXdZ2XUAA2Mjr.png","thumbnailUrl":"https://pbs.twimg.com/media/HSWXdZ2XUAA2Mjr.png","isAccessibleForFree":true,"articleSection":"Collections","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Collections","logo":"https://media.daily.dev/image/upload/s--fk_6ycEi--/f_auto,q_auto/v1780996001/logos/collections?_a=BAMAMiWQ0","url":"https://daily.dev/sources/collections"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/routing-subagents-to-different-models-saves-tokens-and-improves-results-jhewcyrth","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"llm,ai-agents,claude-code,opencode","timeRequired":"PT2M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Collections","item":"https://daily.dev/sources/collections"},{"@type":"ListItem","position":3,"name":"Routing subagents to different models saves tokens and improves results"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/routing-subagents-to-different-models-saves-tokens-and-improves-results-jhewcyrth#faq","mainEntity":[{"@type":"Question","name":"How do I make Claude Code use a different model for subagents than the main agent?","acceptedAnswer":{"@type":"Answer","text":"Set the environment variable CLAUDE_CODE_SUBAGENT_MODEL to the desired model, such as opus, to route subagents to that model while the main orchestrator agent uses whatever model it's already running on, such as Claude 5.1. This lets you keep frontier-level reasoning only for the orchestrator while cheaper subagent calls handle simpler spawned tasks. daily.dev surfaces practical configuration tricks like this for developers tuning agent costs."}},{"@type":"Question","name":"Does opencode support using different models for different subagents?","acceptedAnswer":{"@type":"Answer","text":"Yes, opencode2 added optional per-subagent model selection in a recent release. A common use case is assigning a smarter model specifically to code review subagents while keeping the main orchestration loop on a faster, cheaper model for everyday steps. Developers picking agent frameworks compare feature updates like this one on daily.dev."}},{"@type":"Question","name":"What models does Vercel's v0 use for planning versus execution in agent pipelines?","acceptedAnswer":{"@type":"Answer","text":"Vercel's v0 setup, as described by Guillermo Rauch, uses Claude for planning and Grok for executing, mixing models and reasoning budgets across a pipeline without requiring special server-side routing infrastructure. The orchestrating model itself decides which subagent to spin up and how to configure it, and the whole process can be steered conversationally and interrupted at any time. Teams choosing between agent orchestration setups follow tool comparisons like this on daily.dev."}}]} ```