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.80entry #1

Claude Code v2.1.80 ·

Channels (MCP Inbound Push Notifications)

Entry
JSON All of v2.1.80
EntryKind: in v2.1.80,
ChangesSection of the release
What

A new system that allows MCP servers to push notifications directly into your Claude Code session, enabling real-time event-driven workflows.

Usage
claude --channels server1 server2
Details
  • MCP servers that declare the claude/channel capability can send notifications/claude/channel messages that appear in your session
  • Use --channels <servers...> to specify which servers may push notifications
  • Use --dangerously-load-development-channels <servers...> for local development of channel-enabled servers (shows a confirmation dialog at startup)
  • Requires claude.ai authentication (/login)
  • Org administrators can control availability via the channelsEnabled managed setting
  • Plugin-based channels must be on an approved allowlist (controlled by the tengu_harbor feature flag and tengu_harbor_ledger)
  • A warning is displayed: "Experimental · inbound messages will be pushed into this session, this carries prompt injection risks"
  • Channel messages are rendered with a ← prefix showing the source server name
Evidence

Channel notification system — notifications/claude/channel protocol (search for "claude/channel")

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Read from
Feature flag
tengu_harbor On for this account, and not off by default

The flag server returned on for the one account this site reads, and nothing in this release compiles it off by default. The compiled default is shown below, and says which it is when we cannot read one: a fifth of gates compile in a string or a number rather than on or off, and most published releases have no gate table behind them at all. No client can see what the server returns for your account.

This account: on · anonymous baseline: on · compiled default in v2.1.80: no gate table built for this version

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.

tengu_harbor_ledger 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.80: no gate table built for this version

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.80. 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 on for tengu_harbor, 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_harbor, 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
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agreeAdded --channels (research preview) — allow MCP servers to push messages into your session

See this entry in the whole of v2.1.80 →

Feedback