{"version":"2.1.283","anchor":"worker-check-in-interval-becomes-an-escalating-schedule-via","canonical_anchor":"worker-check-in-interval-becomes-an-escalating-schedule-via","heading":"Worker check-ins now follow a schedule set by CLAUDE_CODE_WORKER_CHECKIN_SCHEDULE","tier":"use","area":"Background Tasks","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/worker-check-in-interval-becomes-an-escalating-schedule-via","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Worker check-ins now follow a schedule set by CLAUDE_CODE_WORKER_CHECKIN_SCHEDULE\n\nOne schedule variable replaces the two single-interval check-in variables, and setting the old ones no longer changes anything\n\n**Unclear.** Exactly what Claude Code does at each check-in is not shown.\n\n**What**\n\nCheck-ins on workers, meaning background tasks Claude Code is running for you, used to happen at one fixed interval set by `CLAUDE_CODE_COORDINATOR_WORKER_CHECKIN_SECONDS` or `CLAUDE_CODE_AUTO_BACKGROUND_WORKER_CHECKIN_SECONDS`. Both variables have been removed. Check-ins are now set by `CLAUDE_CODE_WORKER_CHECKIN_SCHEDULE`, which takes a stepped schedule instead of one number.\n\n- `CLAUDE_CODE_WORKER_CHECKIN_SCHEDULE` is a comma-separated list of seconds, each from 1 to 86400.\n\n- Claude Code works through the list one step at a time.\n\n- The timer ticks at the shortest step or every 60 seconds, whichever is shorter.\n\n- The schedule goes back to its first entry when a worker starts and no other worker is running.\n\n- It applies only in coordinator mode (`CLAUDE_CODE_COORDINATOR_MODE`) or when `CLAUDE_AUTO_BACKGROUND_TASKS` is set.\n\n**Why**\n\nIf you set either old variable, it is now ignored without any warning, so move your interval into `CLAUDE_CODE_WORKER_CHECKIN_SCHEDULE`.\n\n- Area: Background Tasks\n- Names: `CLAUDE_CODE_WORKER_CHECKIN_SCHEDULE`\n- Tier: Use it now\n- Useful: 5\/5\n- Signal: 3\/5"}