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

Claude Code v2.1.305 ·

Cloud sessions can allow or block MCP servers by host

In Anthropic cloud sessions, Claude Code can check each MCP server's host against an allow or deny list sent by the server

Nothing to try yet In Development
JSON All of v2.1.305
Nothing to try yetTier: how much it should matter to you
4Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
MCPArea: what it touches
In DevelopmentKind: in v2.1.305,
What probably matters to youSection of the release

Unclear It is not confirmed that the default lets every host through, or where a blocked result actually stops a connection.

What

MCP servers are add-on tools that Claude Code connects to, and each one lives at a host, the address of the machine it runs on. In cloud sessions, Claude Code now checks an MCP server's host against a list it receives from Anthropic's server. The list can be in one of three modes:

  • allow: only the listed hosts are permitted
  • deny: the listed hosts are blocked
  • all: every host is permitted

If the list it receives is malformed, Claude Code treats it as an empty allow list, which blocks every host. A server whose host cannot be worked out is blocked too.

This applies only when CLAUDE_CODE_REMOTE is true and CLAUDE_CODE_ENVIRONMENT_KIND is unset or set to anthropic_cloud.

Why

This gives Anthropic a way to limit which MCP servers a cloud session can reach. It has no effect when you run Claude Code on your own machine.

Read from
Feature flag
tengu_gleaming_creek 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.305: 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.305. It isn't a statement about your account. What a flag value here can and cannot tell you

What has happened since
Flag reading moved The flag server now returns [] for tengu_gleaming_creek, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns nothing at all, having stopped carrying it for tengu_gleaming_creek, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns [] for tengu_gleaming_creek, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns nothing at all, having stopped carrying it for tengu_gleaming_creek, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns [] for tengu_gleaming_creek, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.

See this across every release →

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 is not confirmed that the default lets every host through, or where a blocked result actually stops a connection.
The name it cites is new in this buildNew in this build: tengu_gleaming_creek

See this entry in the whole of v2.1.305 →

Feedback