{"version":"2.1.293","anchor":"quiet-shell-check-ins-now-cover-all-background-commands-per","canonical_anchor":"quiet-shell-check-ins-now-cover-all-background-commands-per","heading":"Quiet background command check-ins are now grouped per agent","tier":"notice","area":"Bash","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/quiet-shell-check-ins-now-cover-all-background-commands-per","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Quiet background command check-ins are now grouped per agent\n\nCheck-ins about silent background shell commands now come once per agent, list every quiet command and say when the next one is due\n\n**What**\n\nWhen a background shell command goes quiet, Claude Code sends the model a check-in reminder about it. A background command is one Claude started that keeps running while the conversation continues. These check-ins now work per agent instead of per command. An agent is the main Claude or a helper Claude doing part of the work.\n\n- One timer now runs for each agent that owns background commands, instead of one per command.\n\n- A check-in names the command that has been quiet the longest and lists the other quiet commands with their output files. Those commands get no check-in of their own.\n\n- The text now says \"The next check-in comes after another \u2026\" with a real duration, and the growing wait is capped. Before it said \"The next check-in comes after twice as long a silence.\"\n\n- Check-in messages from `shell-checkin` are now tied to an agent by `agentId` instead of by the origin slug.\n\n**Why**\n\nThe model gets fewer, more useful reminders about stuck background commands, and each reminder reaches the right agent.\n\n- Area: Bash\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}