Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.275entry #1

Claude Code v2.1.275 ·

New internal 'advisor' tool, gated to first-party accounts with entitlement

A new gated 'advisor' tool was added, restricted by an env var and account entitlement, with clearer in-context messaging about when it applies

Group of 3 Use it now Internal Changes
JSON All of v2.1.275
Use it nowTier: how much it should matter to you
5Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
AdvisorArea: what it touches
Internal ChangesKind: in v2.1.275,
What probably matters to youSection of the release

Unclear It's unclear whether the tengu_sage_compass2 gate plays any role in this check, since no reading of it has been taken.

What

A new internal tool/event kind called "advisor" has been introduced.

  • It can be disabled with an environment variable, and otherwise requires a first-party Anthropic account plus an internal entitlement check before it's available.
  • The availability check was refactored into a shared helper function, replacing inline checks that combined the disable env var, first-party account check, and entitlement check.
  • When you change the advisor model setting mid-conversation (from the /advisor UI or its slash command), Claude Code now shows a contextual note explaining when the new setting will actually take effect — for example, if the API already refused to use the advisor this turn, or if the conversation already locked in a different advisor model or tool declaration.

Why

This lays the groundwork for an advisor feature restricted to eligible accounts, and helps avoid confusion by telling you explicitly when a mid-conversation change to the advisor setting won't apply immediately.

Read from
Names in the bundleCLAUDE_CODE_DISABLE_ADVISOR_TOOL
Feature flag
tengu_sage_compass2 Not enough to say

Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.

This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.275: not a boolean we can read

These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.

Read once, for one account on one subscription tier, against v2.1.275. It isn't a statement about your account. What a flag value here can and cannot tell you

Since it was published

The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.

Confirmed since Anthropic's documentation has since written up CLAUDE_CODE_DISABLE_ADVISOR_TOOL, on Connect Claude Code to an LLM gateway. | `400` errors on every request, in the gateway's own words rejecting an unrecognized tool type, such as `Input tag 'advisor_20260301'`, on Claude Code v2.1.275 | In a gradual rollout on that version, requests carry an [advisor tool](/docs… llm-gateway-connect see the edit
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt's unclear whether the `tengu_sage_compass2` gate plays any role in this check, since no reading of it has been taken.
Anthropic's documentation agreesAnthropic's documentation has since written up CLAUDE_CODE_DISABLE_ADVISOR_TOOL, on Connect Claude Code to an LLM gateway.

See this entry in the whole of v2.1.275 →

Feedback