Repository navigation
[FEATURE]: @agent:provider/model syntax to override subagent model on the fly #11215
Description
Feature hasn't been suggested before.
- I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
I’d like OpenCode to support an explicit per-subtask model override when invoking subagents, via @agent:provider/model syntax (example: @explore:openai/gpt-5.2).
What I want to add:
- Allow users to specify the model for a specific subagent invocation inline, without changing global defaults.
- Ideally this is supported anywhere
@agentinvocations are supported (at least TUI first), with autocomplete for available providers/models. - The chosen model should be stored on the message/subtask metadata so it’s visible/auditable and can be surfaced in the UI.
Benefits:
- Lets users pick a faster/cheaper model for simple subtasks and a stronger model for harder ones, per call.
- Avoids needing multiple nearly-identical agents just to switch models.
- Makes model selection explicit and reproducible when reviewing a session history.
Reacted by katkatfarkat, wv9rtdxnn, Hicham Boushaba and Umeayo Onyekachukwu
Activity
github-actions commentedon Jan 29, 2026
This issue might be a duplicate of existing issues. Please check:
These issues all address the core need for per-task/per-command model selection without changing global defaults. The proposed @agent:provider/model syntax in this issue provides an alternative approach to the tiered model system proposed in #6651.
Feel free to ignore if this specific syntax approach addresses a gap not covered by those issues.
farukg commentedon Feb 16, 2026
Love this idea. Related use case that goes a step further: shell-specialist → summarizer pipeline.
I want to delegate shell command execution (fd, rg, eza pipelines) to a cheap code-specialist model (
opencode/grok-code), then have the main expensive model (Opus/GPT-5) interpret and summarize the raw results. Today I achieve this with a customshell-execsubagent pinned to a specific model, but the@agent:provider/modelsyntax would make ad-hoc overrides much more ergonomic — especially when I want to temporarily test whether a different model handles a specific subtask better, without editing agent config files.github-actions commentedon Apr 18, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.
RajatGarga commentedon Aug 22, 2026
So is this not going to happen?