{"version":"2.1.290","anchor":"shell-check-in-notifications-treated-like-goalworker-check","canonical_anchor":"shell-check-in-notifications-treated-like-goalworker-check","heading":"Quiet background commands can now trigger a check-in for Claude","tier":"notice","area":"Background Tasks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/shell-check-in-notifications-treated-like-goalworker-check","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Quiet background commands can now trigger a check-in for Claude\n\nA background shell command that goes quiet for a while can now send Claude a check-in telling it to look at the output and stop the task if stuck\n\n**Unclear.** What produces shell check-in notifications is not settled.\n\n**What**\n\nClaude can run shell commands in the background while it keeps working. A background command that produces no new output for a set time can now send Claude a check-in notification, marked `shell-checkin`.\n\n- The message says it is a check-in, not a completion. It tells Claude to read the command's output file, look at the running processes, and stop the task if it is stuck.\n\n- The quiet period before each new check-in doubles each time.\n\n- Check-ins are now grouped with the existing goal and worker check-ins (`goal-checkin`, `worker-checkin`).\n\n- The quiet period comes from a server-side setting. Its built-in default is 0, and 0 turns the feature off. Nothing has been read about that setting yet.\n\n**Why**\n\nIf the server sets a value, Claude is prompted to notice a command that has hung instead of waiting on it, and to clean it up.\n\n- Area: Background Tasks\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}