{"version":"2.1.275","anchor":"in-process-teammate-polling-gets-an-idle-timeout-behind-ten","canonical_anchor":"in-process-teammate-polling-gets-an-idle-timeout-behind-ten","heading":"In-process teammate polling gets an idle timeout, behind tengu_zinc_harbor","tier":"soon","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/in-process-teammate-polling-gets-an-idle-timeout-behind-ten","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### In-process teammate polling gets an idle timeout, behind tengu_zinc_harbor\n\nIn-process teammate polling can time out after a period of inactivity, gated off for now\n\n**What**\n\nThe 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`.\n\n**Why**\n\nThis 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.\n\n- Flag `tengu_zinc_harbor`: Off in both readings (read for one account on one subscription tier against v2.1.275; this account: off, anonymous baseline: off, compiled default: 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.\n- Area: Elsewhere\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 2\/5\n- Present in the build but not switched on"}