{"version":"2.1.314","anchor":"timed-out-shell-commands-are-flagged-in-the-result","canonical_anchor":"timed-out-shell-commands-are-flagged-in-the-result","heading":"Shell commands stopped by their time limit are now marked as timed out","tier":"notice","area":"Bash Tool","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/timed-out-shell-commands-are-flagged-in-the-result","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Shell commands stopped by their time limit are now marked as timed out\n\nWhen a shell command is stopped for running too long, its result now also carries a flag saying it timed out\n\n**Unclear.** Whether the `timedOut` flag reaches Claude or the output of the Agent SDK is not stated.\n\n**What**\n\nShell commands Claude runs have a time limit. When a command is stopped because it reached that limit, its result now carries a `timedOut` flag set to true. Before, there was only the \"Command timed out after\" message.\n\n**Why**\n\nAnything reading the result can now tell a timeout apart from other kinds of failure without reading the message text.\n\n- Area: Bash Tool\n- Names: `timedOut`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}