{"version":"2.1.323","anchor":"background-command-notice-no-longer-mentions-a-call-back-win","canonical_anchor":"background-command-notice-no-longer-mentions-a-call-back-win","heading":"Background command notice no longer promises a call-back time","tier":"notice","area":"Background Tasks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/background-command-notice-no-longer-mentions-a-call-back-win","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Background command notice no longer promises a call-back time\n\nAfter a command moves to the background, Claude is no longer told it will hear back within a set time; it gets a general notice instead\n\n**What**\n\nA command can keep running in the background while Claude carries on with other work. Claude used to be told that it would normally hear back if the command finished while it was still working or within a stated time.\n\nThe stated time has been removed. The notice now says Claude will be told if the command exits while it is still working. It also says that after Claude replies, it may not hear about the command until you write again.\n\n**Why**\n\nThis changes what Claude expects once a command is in the background. It no longer counts on hearing back within a fixed time.\n\n- Area: Background Tasks\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}