{"version":"2.1.246","anchor":"a-second-kind-of-periodic-check-in-alongside-goal-check-ins","canonical_anchor":"a-second-kind-of-periodic-check-in-alongside-goal-check-ins","heading":"A second kind of periodic check-in alongside goal check-ins","tier":"use","area":"Subagents","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/a-second-kind-of-periodic-check-in-alongside-goal-check-ins","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### A second kind of periodic check-in alongside goal check-ins\n\nCoordinator worker check-ins are their own check-in type with their own interval setting and reset behaviour.\n\n**What**\n\nCoordinator worker check-ins are wired in as their own check-in type next to the existing idle goal check-in, with separate stored state that is cleared on conversation reset and its own interval variable, `CLAUDE_CODE_COORDINATOR_WORKER_CHECKIN_SECONDS`.\n\n**Details**\n\n- The injected message is delivered as a task notification rather than a user turn.\n- The variable sets the interval; what enables the check-in in the first place is not settled by this code path.\n\n**Evidence**\n\n`CLAUDE_CODE_COORDINATOR_WORKER_CHECKIN_SECONDS`\n\n- Area: Subagents\n- Names: `CLAUDE_CODE_COORDINATOR_WORKER_CHECKIN_SECONDS`\n- Tier: Use it now\n- Useful: 2\/5\n- Signal: 3\/5"}