{"version":"2.1.224","anchor":"advisor-entry-added-to-managed-agents-multiagent-rosters","canonical_anchor":"advisor-entry-added-to-managed-agents-multiagent-rosters","heading":"Advisor entry added to Managed Agents multiagent rosters","tier":"notice","area":"Claude API Skill","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/advisor-entry-added-to-managed-agents-multiagent-rosters","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Advisor entry added to Managed Agents multiagent rosters\n\nMultiagent rosters can include one advisor entry so the main thread consults a stronger model mid-turn.\n\n**What**\n\nRosters 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.\n\n**Details**\n\n- Consultations run as a platform-spawned thread under a reserved name and do not count against the 25-concurrent-thread limit.\n- Advice arrives as an `agent.thread_message_received` event, either plaintext or `[{\"type\": \"redacted\"}]` depending on the advisor model.\n- Fable 5 is documented as temporarily unavailable in the advisor role.\n\n**Evidence**\n\n`anthropic.advisor`\n\n- Area: Claude API Skill\n- Names: `advisor`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 4\/5"}