-
Notifications
You must be signed in to change notification settings - Fork 29
I used to use opencode go cli, it can configure subagents by specific format like:
- opencode-go/deepseek-v4-flash
- openrouter/deepseek-v4-flash
- /
but in vscode copilot, i don't know if it was the same format when insturct the model to spaw some subagent
Is there any model full id list ? I can't see it from extension configure page.
vscode copilot model config json
{
"name": "OpenCode Go",
"vendor": "opencodego",
"apiKey": "${input:chat.lm.secret.-33b8da4f}",
"settings": {
"opencodego:deepseek-v4-flash::session-2026年05月21日-b": {
"reasoningEffort": "max"
}
}
}
opencodego.json
image
All reactions
Replies: 2 comments 2 replies
|
Hey @dengyakui. Good question, and the short answer is the format here is not the same as the OpenCode Go CLI. Model ID formatEvery model this extension registers follows one shape:
For your case, that becomes:
That suffix The raw ID in the middle, Getting the full listThe CLI-style format (
You copy the Using it in a custom agentHere's where it diverges from the CLI. VS Code Copilot custom agents ( If you want a specific agent to always run on a specific OpenCode model, the practical workflow:
The One caveatThe Anything unclear, ping back. |
All reactions
Would naming the models in a certain way impact the GHCP prompts being injected into them?
https://github.com/microsoft/vscode/pull/323500/changes
All reactions
@CogitoBurrito good catch. Short answer: yes, but it comes from the family value we register, not the vendor name.
Looking at vscode#323500, isKimiFamily() checks model.family or model id starting with kimi-k2.6 / kimi-k2.7-code. If it matches, Copilot injects the Kimi-specific prompt and routes Kimi to replace-string edit tools (no insert-edit/apply-patch). If it doesn't, the model falls back to the default prompt.
In this extension we set family as {vendor}-{rawModelId}-{revision} (e.g. opencodego-kimi-k2.7-code-session-...). So the vendor prefix makes it not match startsWith('kimi-k2.7-code'). Copilot sees it as unknown family, default prompt applies.
The fallback path matters here: the matcher also checks getModelId(model). If that returns the raw id (kimi-k2.7-code), the Kimi prompt still kicks in. In practice Kimi flows through the OpenCode gateway with the same id the CLI uses, so Copilot's Kimi prompt should activate, which is what we want.
The vendor prefix in family is intentional: without it two deepseek-v4-flash entries look identical in the picker. Trade-off is picker uniqueness vs. matching Copilot's family-specific prompts. So far no user reports, but I'll watch it once 1.127 hits stable. Thanks for flagging the PR.
All reactions
Thank you for the explanation! I think they just made some improves.
https://github.com/microsoft/vscode/pull/324814/changes