Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.309 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.290 ·

Channels wait for your organisation's policy and say so

Channels now stay off until your organisation's policy loads, and the startup banner explains that messages are dropped meanwhile

Group of 3 You'll notice Improvements
JSON All of v2.1.290
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
ChannelsArea: what it touches
ImprovementsKind: in v2.1.290,
ImprovementsSection of the release

What

Channels lets outside services send messages into a Claude Code session. Channels now waits for your organisation's policy before it delivers anything.

  • The status text listing what stays off until the network policy loads now names Channels alongside web fetch and design sync.
  • The Channels startup banner has a new state while the policy is still loading. It says Channels is "waiting for your organization's policy" and that "Messages are dropped until it loads".
  • If the policy cannot be reached because the network does not provide it, the banner says "This network does not serve it, so messages are dropped this session".
  • Incoming channel messages are dropped until the policy is settled. Before, the banner only had the policy-blocked, disabled and third-party states.

Why

If your organisation's policy cannot be loaded, Channels stays off instead of letting messages through unchecked. Messages that arrive in the meantime are lost, and the banner now tells you why instead of leaving them to vanish silently.

How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agreeFixed --channels permission relay: a reply ID that repeats within a session is now ignored instead of approving a different prompt

See this entry in the whole of v2.1.290 →

Feedback