{"version":"2.1.315","anchor":"scheduledtriggered-run-system-note-and-interrupted-agent-me","canonical_anchor":"scheduledtriggered-run-system-note-and-interrupted-agent-me","heading":"Messages for unattended runs and interrupted helper agents have changed","tier":"internal","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315\/e\/scheduledtriggered-run-system-note-and-interrupted-agent-me","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315","markdown":"### Messages for unattended runs and interrupted helper agents have changed\n\nThe note Claude gets in scheduled or triggered runs, and the result it sees for an interrupted subagent call, have both changed\n\n**Unclear.** Where these two messages are used, and how their wording differs from before, is not clear.\n\n**What**\n\nTwo fixed messages that Claude receives have changed:\n\n- The note for scheduled or triggered runs. These are runs started on a schedule, by a webhook (a message from another service) or by watching for changes. The note begins \"You are running as a scheduled or triggered run\". It says nobody is watching live and that the final message must be a complete record.\n\n- The result for an interrupted subagent call. A subagent is a separate helper Claude starts to do part of a task. When one is cut off, the result Claude sees begins \"[Agent call interrupted:\".\n\n**Why**\n\nThese change what Claude is told when it works with nobody watching. They also change what it sees when a helper's work stopped before it finished, for example when a conversation is picked up again.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}