{"version":"2.1.265","anchor":"advisor-tool-added-to-several-telemetrycontext-injection","canonical_anchor":"new-advisor-tool-feature-gated-off-by-default-tengu-refl","heading":"New \"advisor tool\" feature, off by default","tier":"soon","area":"Advisor Tool","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/advisor-tool-added-to-several-telemetrycontext-injection","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### New \"advisor tool\" feature, off by default\n\nA new advisor tool mechanism can announce its availability to the model, gated off by default behind a feature flag\n\n**Unclear.** What event or feature the \"advisor_tool\" category actually classifies is not stated.\n\n**What**\n\nA new \"advisor tool\" mechanism has been added. It can send the model an attachment (`attachment.type === \"advisor_tool\"`) telling it whether an advisor tool is or isn't currently available, with messages like \"The advisor tool is no longer available\" or \"is available\". A new \"advisor_tool\" category token was also added to several of the internal lists used for telemetry and context-injection categorization, alongside existing tokens like `remote_session_change`.\n\n**Why**\n\nThe feature is controlled by a feature gate and is off by default, so it doesn't affect current sessions, but lays groundwork for Claude to be told when an advisor tool becomes available to it.\n\n- Area: Advisor Tool\n- Names: `advisor_tool`\n- Tier: Nothing to try yet\n- Useful: 5\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}