{"version":"2.1.304","anchor":"bash-staleness-check-skipped-in-remote-mode-held-background","canonical_anchor":"bash-staleness-check-skipped-in-remote-mode-held-background","heading":"Shell staleness check can be skipped, and background shells gain a held state","tier":"internal","area":"Bash Tool","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/bash-staleness-check-skipped-in-remote-mode-held-background","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Shell staleness check can be skipped, and background shells gain a held state\n\nIn one running mode Claude Code skips its shell staleness check, and background shell commands can now be held\n\n**Unclear.** It is not clear which mode skips the staleness check, or what holding a background shell command changes for the user.\n\n**What**\n\nThe Bash tool is how Claude Code runs shell commands on your machine. Claude Code has a staleness check for these commands, which can lead to a warning. That check used to run every time. In one running mode it is now skipped and finds nothing.\n\nA command started through the Bash tool can now also be held while it runs in the background, and Claude Code can react when the held command ends.\n\n**Why**\n\nIn the mode where the check is skipped, the staleness warning will not appear. Background shell commands now follow different handling.\n\n- Area: Bash Tool\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}