Sub agent ignoring model configuration in version 2.5

Support Bug Reports
1

This bug is not fixed in version 2.5

My version:
Version: 2.5.17
VSCode Version: 1.105.1

I created a sub agent that is supposed to use claude-4.5-haiku, but instead uses claude-4.6-sonnet-medium. The subagent is invoked with a slash command, and I can confirm that slash command actually invokes the subagent.

One of the goals of using a sub-agent is to save cost on specific tasks that don’t require an expensive model.

Sub-agent slash commands do not use the model specified for the sub-agent
2

Hey there!

Could you share a subagent file that reproduces this?

3

Here’s the relevant portion of this sub-agent:

---
name: git
description: Git and GitHub specialist for branch, commit, push, and PR workflows. Enforces safe workflows, conventional commits, Git Flow branch naming, and force-push confirmation.
model: claude-4.5-haiku
---

# Git and GitHub Agent

You are a Git and GitHub specialist. You handle all local Git operations and GitHub interactions (branches, commits, PRs, merges) and enforce safe workflows.

## Tool Restrictions

- Do **not** write or edit files. You have no file-write or file-edit access.
- Only use shell commands for git, gh, ls, and echo operations.
- Do **not** run arbitrary shell commands outside of git/gh workflows.
- Force push commands (`--force`, `-f`, `--force-with-lease`) require explicit user confirmation — never run them automatically.
....
4

Interesting, it works well on my end (Claude 4.5 Haiku is used for the subagent)

Screenshot 2026-02-21 at 18.43.47
Screenshot 2026-02-21 at 18.43.474388×2190 551 KB

  • Anything look different here from what you’re doing?
  • Do you have a Request ID with Privacy Mode disabled you could hare
  • What parent model is calling the subagent?
5

The issue wasn’t the correct model being shown in the IDE itself when I ran the sub-agent, but instead that the billing page was showing an incorrect model, specifically the one that I was using outside of the sub-agent.

I was also in contact with one of the reps by email who notified me that this issue has been fixed. I was able to confirm that as of yesterday both the sub-agent and the billing page show the correct model. Thank you for your help with this issue.

1 Like