Follow Discord
Sweep 27 Oct 2026 · 19:04Z Build v2.1.312 531 read Stable v2.1.308 Latest v2.1.312 Next v2.1.312 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.312 ·

Claude in Slack and Teams sessions skip server-managed settings

Sessions run by Claude in Slack or Teams now skip server-managed settings, marked by a new claude_tag reason; policy limits are decided separately

Group of 2 You'll notice Improvements
JSON All of v2.1.312
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
Managed SettingsArea: what it touches
ImprovementsKind: in v2.1.312,
What probably matters to youSection of the release

What

Server-managed settings are settings an organisation sets centrally and Claude Code downloads from the server. A new claude_tag reason now marks sessions that do not use them. Claude Code's own message says: 'Claude in Slack and Claude in Teams sessions don't apply server-managed settings; organization policy limits are decided separately'.

  • When Claude Code decides whether to fetch these settings, it now answers no with reason claude_tag when three things hold: a surface check passes, a second check fails, and no stored claude.ai login is found. The login helper warns 'could not read the claude.ai login' when it cannot read the login.
  • The same claude_tag case was added to the list of reasons a session cannot use these settings and to the handling of login attempts, next to sandboxed_entrypoint.

Why

Organisation admins should know that sessions run by Claude in Slack or Claude in Teams will not apply server-managed settings. Organisation policy limits for those sessions are decided separately.

See this entry in the whole of v2.1.312 →

Feedback