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 ·

Hidden cross-session inbox row in the settings dialog

A cross-session inbox row can appear in settings but stays hidden without a server flag.

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

A cross-session inbox settings row is gated by CLAUDE_CODE_HARBOR_KITE or tengu_harbor_kite, both off, and hardcoded off elsewhere.

What

The settings view can now show a row for a cross-session inbox, controlled by a new crossSessionInboxRowVisible prop. In the main REPL it is on when CLAUDE_CODE_HARBOR_KITE is set, otherwise a Windows sub-gate, otherwise the server flag tengu_harbor_kite, which defaults to off. A second place that builds the settings view hardcodes it to off, so without a server value the row stays hidden.

Usage
CLAUDE_CODE_HARBOR_KITE=1 claude
Evidence

crossSessionInboxRowVisible

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

Read from
Names in the bundleCLAUDE_CODE_HARBOR_KITE
Feature flag
tengu_harbor_kite Off by default, switched on for this account

The shipped code defaults this off, and the flag server returned on for the one account this site reads on this version. That is the reading that makes the entry above worth a second look, and it still says nothing about your account.

This account: on · anonymous baseline: on · 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 on for tengu_harbor_kite, 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 off for tengu_harbor_kite, 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 on for tengu_harbor_kite, 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, 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 →

See this entry in the whole of v2.1.232 →

Feedback