Multiagent rosters can include one advisor entry so the main thread consults a stronger model mid-turn.
What's wrong with this entry?
Rosters accept a new {"type": "advisor", "model": ...} entry, at most one per roster, letting the main thread consult a more capable model partway through a turn.
- Consultations run as a platform-spawned thread under a reserved name and do not count against the 25-concurrent-thread limit.
- Advice arrives as an
agent.thread_message_receivedevent, either plaintext or[{"type": "redacted"}]depending on the advisor model. - Fable 5 is documented as temporarily unavailable in the advisor role.
anthropic.advisor
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.232
Advisor results no longer render as blank
Both mention advisor
-
v2.1.232
Clearer message when a model cannot be an advisor
Both mention advisor
-
v2.1.232
Advisor results validate their stop reason
Both mention advisor