Fixed, available in the next version. A step set to a full Claude model name such as claude-sonnet-5-5 was mistaken for a model of another tool we support, and replaced by Opus when its console started. When the run came back to that step, it then switched the model with Claude Code's /model command, which also saves that model as the default of the whole Claude account. Each step now starts on the model set on its node, and a step that has to change model restarts its console on that model, keeping the conversation, instead of using /model, so a run no longer changes your account's default model. One exception: if the run's project is not open on screen at that moment, the step still switches with /model so that it runs on the right model. If the problem is still there after this update, please reopen this ticket with as many details as possible (a screenshot or a video helps a lot).
Team run step ignores its configured model on first entry and rewrites the shared account default
From Rob ZappDone 14 hours agovia agent-mcp
A team node is configured with model claude-sonnet-5-5. The first time the step runs, its console starts on the Claude account profile's default model (claude-opus-5-5), not on the node's model. The runner sends /model <node model> only when the step is entered again in a later cycle. That /model call writes into the shared profile settings, so the last step that ran sets the start model of every Claude console on that profile. Removing the default by hand does not last.
Seen on 2026-10-21 on at least five runs of one team: the "Code Reviewer (Sonnet)" and "Technical Documentation (Sonnet)" steps ran on Opus. agents_list_live showed model: "opus" for those step consoles, while backlog_get showed claude-sonnet-5-5 for the same nodes.
Effect: every review that must run on a set model had to be redone by hand with another reviewer.
AgentsRoom diagnostics
- App version: 1.225.0
- OS: darwin 27.2.0 (arm64)
- Agent CLI: claude
- App language: system
Expected behavior
Each step console starts on its node's configured model on first entry, and running a step does not change the shared profile default.
Actual behavior
First entry uses the profile default model. A later /model call for a re-entered step changes the default for all Claude consoles on that profile.
Steps to reproduce
- Create a team with two Claude nodes on different models (one Sonnet, one Opus). 2) Start a run on a ticket. 3) While the Sonnet step runs, call agents_list_live: the step console shows model opus. 4) Compare with backlog_get, which lists claude-sonnet-5-5 for that node.
Replies
Sent automatically with your message
Your browser sent this along so the team can reproduce what you saw. Nothing here was typed by you.
- Browser
- AgentsRoom-MCP/1.225.0 (darwin arm64)