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.232 ·

Cloud sessions can be addressed as message targets

Cloud sessions on your account can be message targets, but the enabling flag is off in this build.

Nothing to try yet Notable No documentation found New Features
JSON All of v2.1.232
Nothing to try yetTier: how much it should matter to you
3Useful: my rating, 1 to 5
5Signal: worth watching, 1 to 5
Cross-Session MessagingArea: what it touches
New FeaturesKind: in v2.1.232,
What probably matters to youSection of the release

Cloud sessions as cross-session message destinations are fully wired but need CLAUDE_CODE_HARBOR_KITE_CLOUD or a server flag that is off here.

What

Claude Code can now list the cloud sessions on your account and treat them as destinations for cross-session messages. It needs first-party login, the allow_remote_sessions capability on your account and an organization ID, plus either the CLAUDE_CODE_HARBOR_KITE_CLOUD environment variable or the tengu_harbor_kite_cloud remote flag, which is off in this build unless your server config turns it on.

Details
  • Sessions come from the /v1/code/sessions endpoint, fetched page by page and memoized for the process.
  • Archived sessions, bridge entries and placeholder "husk" records are filtered out of the list.
  • If the list cannot be fetched in time, the code says so rather than quietly returning a short list.
Evidence

tengu_harbor_kite_cloud

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

Read from
Feature flag
tengu_harbor_kite_cloud Off in both readings

The flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.

This account: off · anonymous baseline: off · compiled default in v2.1.232: off

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.232. 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 off for tengu_harbor_kite_cloud, 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_kite_cloud, 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.
The name it cites is new in this buildNew in this build: CLAUDE_CODE_HARBOR_KITE_CLOUD

See this entry in the whole of v2.1.232 →

Feedback