{"version":"2.1.242","anchor":"computer-use-actions-can-be-interrupted-and-inner-failures-n","canonical_anchor":"computer-use-actions-can-be-interrupted-and-inner-failures-n","heading":"Computer-use actions can be interrupted, and inner failures no longer kill the whole call","tier":"notice","area":"Computer Use","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/computer-use-actions-can-be-interrupted-and-inner-failures-n","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Computer-use actions can be interrupted, and inner failures no longer kill the whole call\n\nYou can interrupt computer-use waits and typing, and one failed action no longer sinks the batch.\n\n**What**\n\n`wait` now polls in slices and stops on interrupt, and typing, key repeat, hold-key and drags re-check for interrupt before each keystroke or movement. In `computer_batch` and `teach_step` each inner action is wrapped so a throw becomes an `executor_threw` tool error for that action instead of failing everything.\n\n**Details**\n\n- Batch results are rendered per action as `[i\/n] action:` lines, with images dropped after an error.\n- Inner throws are logged as `[computer-use] computer_batch action=\u2026 threw:`.\n\n**Evidence**\n\n`Wait aborted (user interrupt).`\n\n- Area: Computer Use\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 3\/5"}