luigidemasi commented on issue #33: URL: https://github.com/apache/camel-kit/issues/33#issuecomment-6336808031
> Comment by [vaprea](https://github.com/vaprea) on 2026-05-11 ([original](https://github.com/luigidemasi/camel-kit/issues/60#issuecomment-4419847866)). --- The subagent split naturally opens the door to model tiering, which could significantly amplify the cost savings. The orchestrator itself is the first candidate: routing and merge require no deep reasoning and running it on flagship adds unnecessary latency and cost. From there, MCP lookups and knowledge queries could stay on flash/lite, reviewers on mid, and flagship reserved only for the doubt cycle. OpenCode already supports assigning different models to different agents, which makes it a natural reference implementation for this pattern. A **Model Routing** section covering node-to-tier assignment and provider resolution strategy could be a natural addition to this issue. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
