Source Intelligence
Follow Discord
Sweep 28 Aug 2026 · 00:00Z Build v2.1.250 478 read Stable v2.1.236 Latest v2.1.250 Next v2.1.250 Feeds RSS JSON llms.txt

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

Reference / Feature flags

tengu_harbor_willow

A Claude Code feature flag, read out of the shipped bundle. It has been in the build since v2.1.152, including the newest one read.

What it is

In VS Code sessions, unsafe default permission modes from settings are refused and fall back to normal.

Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.225.

Presence across releases

ReleasesReadingDeclared typeDefault
2.1.245 – 2.1.250 5 releases never mined — —
2.1.152 – 2.1.243 82 releases in the build — bool:false

A row reading never mined is a release with no archived bundle behind it. Nothing was read out of it, so nothing here says whether the name was in it. A declared type or a default is only ever what that release's own bundle stated.

Gate readings

ReleaseResolvedThis accountAnonymousCompiled default
v2.1.248 Off in both readings off off on
v2.1.232 read on another version Off in both readings off off on
v2.1.225 read on another version Off in both readings off off on

Two arms, because they disagree: this account is the one account this site reads and anonymous is a baseline with no identity attached. A reading says nothing about your account, and off cannot rule out a rollout both readings sit outside of. What these readings can and cannot show.

Changelog entries naming it

  1. v2.1.248VSCode gate snapshot loads one gate lazily

    The VSCode extension's gate summary resolves one check later; reported gates are unchanged.

    gate cited by this entry

  2. v2.1.232Host UI is told whether sessions launch in auto permission mode

    The host UI is told whether sessions default to auto permission mode when nothing else picks one.

    gate cited by this entry

  3. v2.1.225VS Code-owned sessions get their own settings defaultMode handling

    In VS Code sessions, unsafe default permission modes from settings are refused and fall back to normal.

    gate cited by this entry

Documentation pages

None of Anthropic's documentation pages this site has a copy of carries this name.

Names beside it

Every feature flag in the inventory starting tengu_harbor, up to twelve of them.

tengu_harborNo description from anybody. 2.1.138 tengu_harbor_kiteMessages from another session render as an @sender header with indented body instead of raw tags. 2.1.224 tengu_harbor_kite_cloudCLAUDE_CODE_HARBOR_KITE_CLOUD turns on cloud peer access; otherwise a server flag decides and it's off. 2.1.232 tengu_harbor_kite_limitsIncoming peer messages now pass rate, duplicate and loop checks before queuing, with drops shown to you. 2.1.242 tengu_harbor_kite_mode_emitMessages from a session with a mismatched permission mode are held and shown with an approve/deny dialog. 2.1.224 tengu_harbor_kite_pacing_offYou can switch off Harbor request pacing with a new environment variable. 2.1.236 tengu_harbor_kite_winSetting CLAUDE_CODE_HARBOR_KITE forces cross-session messaging on, and Windows can now be allowed through. 2.1.229 tengu_harbor_ledgerNo description from anybody. 2.1.138 tengu_harbor_mothNo description from anybody. 2.1.174 tengu_harbor_permissionsNo description from anybody. 2.1.138 tengu_harbor_prismNo description from anybody. 2.1.138

Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the feature flag does. All feature flags.