Unclear Whether there is a minimum quiet period below which the check-in will not fire was not settled.
What
Claude 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.
- 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.
- The quiet period before each new check-in doubles each time.
- Check-ins are now grouped with the existing goal and worker check-ins (
goal-checkin,worker-checkin). - 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.
Why
If 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.
tengu_silent_heron Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.290: not a boolean we can read
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.290. It isn't a statement about your account. What a flag value here can and cannot tell you
Whether there is a minimum quiet period below which the check-in will not fire was not settled.
New in this build: tengu_silent_heron