{"version":"2.1.239","anchor":"scheduled-runs-are-told-to-format-their-notification-as-a-ph","canonical_anchor":"scheduled-runs-are-told-to-format-their-notification-as-a-ph","heading":"Scheduled runs are told to format their notification as a phone banner plus email body","tier":"internal","area":"Terminal UI","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/scheduled-runs-are-told-to-format-their-notification-as-a-ph","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Scheduled runs are told to format their notification as a phone banner plus email body\n\nScheduled runs format notifications so the first sentence becomes a phone banner and the rest an email body.\n\n**What**\n\nWhen Claude Code is started by a scheduled routine on Anthropic's side, the notification tool now gets extra instructions: wrap the message in `<routine_summary>` tags so the first sentence becomes the phone banner and the full text becomes the email body. Ordinary interactive sessions never see this appendix.\n\n**Details**\n\n- Appended only when the launch entrypoint (`CLAUDE_CODE_ENTRYPOINT`) is `remote_trigger` or `remote_cowork_trigger`, both of which are set by the server when it starts a scheduled run.\n- Nothing in the shipped app parses `<routine_summary>`; the tags are read by the server that turns the run into a notification.\n\n**Evidence**\n\n`the notification is how the run reaches its owner`\n\n- Area: Terminal UI\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 4\/5"}