Follow Discord
Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.275 ·

In-process teammate polling gets an idle timeout, behind tengu_zinc_harbor

In-process teammate polling can time out after a period of inactivity, gated off for now

TierNothing to try yethow much it should matter to you
Useful1my rating, 1 to 5
Signal2worth watching, 1 to 5
AreaElsewherewhat it touches
KindIn Developmentin v2.1.275,
Nothing to try yet

In-process teammate polling can time out after a period of inactivity, gated off for now

What

The loop that polls an in-process teammate (a subagent running in the same process) for updates can now give up and report an idle_timeout result if nothing happens for a set number of milliseconds, in two places within that polling logic. This behavior is controlled by a setting called tengu_zinc_harbor.

Why

This would let Claude Code stop waiting on a teammate that has gone silent instead of polling indefinitely, but the setting controlling it is currently off for this site's account and for the general population, so it is not active yet.

Read from
Feature flag
tengu_zinc_harbor 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.275: 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.275. It isn't a statement about your account. What a flag value here can and cannot tell you

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: tengu_zinc_harbor

See this entry in the whole of v2.1.275 →

Feedback