feat(orchestrator): per-Agent LLM model selection#387
Open
sneumannb5 wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Per-Agent orchestrator LLM model selection (Closes #296). Each Agent can pin its own model (and per-turn triage routing) via the Admin builder instead of one
global
ORCHESTRATOR_MODEL. Model picker is populated from the@omadia/llm-providerregistry.Why
Cost/latency differ per Agent — a high-volume support Agent can run on a cheap model while a reasoning-heavy one stays on the frontier model. Turns an
operator runtime choice into a per-instance setting instead of a deploy-time env decision. The pluggable-provider work only pays off once instances can
actually pick different models.
Test plan
configStoreModelRoutingValidation,agentBuilderAgentNode,agentGraphStoreSubAgentModelValidation,orchestratorRegistry,subAgentModelResolution,agentBuilderSubAgentToolseffectiveModelbadge + registryagent rebuiltlog, turn runs without 404Risk / blast radius
agents.model_routing(JSONB) +agent_subagents.model.ORCHESTRATOR_MODELkept as the fallback tier → existing deployments unchanged.modelraw to a single provider adapter.Per-Agent refs are now resolved to the active provider's bare
modelIdbefore build (resolveModelIdForProvider): registry-known same-provider →modelId; cross-provider → dropped to default (out of scope, would 404 on the wrong adapter); registry-unknown → passed through raw (preservespre-resolution behaviour, e.g. the default classifier).
GET /v1/builder/modelsnow returnsmodel_id(bare vendor id) alongsideid.Naming-decisions still pending
SUB_AGENT_MODEL) is listed out-of-scope in Allow defining the LLM model per orchestrator instance #296 but this PR adds the sub-agent picker + validation. Confirm keep, or split out.