{"version":"2.1.309","anchor":"gettask-called-as-a-tool-now-returns-a-dedicated-error","canonical_anchor":"gettask-called-as-a-tool-now-returns-a-dedicated-error","heading":"Claude is told GetTask cannot be called if it tries to use it","tier":"notice","area":"Background Tasks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/gettask-called-as-a-tool-now-returns-a-dedicated-error","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Claude is told GetTask cannot be called if it tries to use it\n\nCalling GetTask now returns an error telling Claude that background command results arrive on their own\n\n**What**\n\nIf Claude tries to call GetTask, which is not an available tool, it now gets a dedicated error back. The error says GetTask cannot be called and that a background command's result, from a command left running while Claude does other work, arrives by itself when the command finishes, unless the message that started it said otherwise.\n\n**Why**\n\nIt stops Claude from repeatedly checking on background commands instead of waiting for their results.\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"}