{"version":"2.1.299","anchor":"task-notification-mentions-messages-that-arrived-too-late-an","canonical_anchor":"task-notification-mentions-messages-that-arrived-too-late-an","heading":"Agent notifications now mention late messages and usage limits","tier":"notice","area":"Subagents","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/task-notification-mentions-messages-that-arrived-too-late-an","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Agent notifications now mention late messages and usage limits\n\nAgent task notifications now say when messages arrived too late and the agent is being resumed, and when a usage limit has paused its work\n\n**What**\n\nWhen an agent (a helper Claude starts to work on a task) finishes or stops, Claude Code sends a notification about it. These notifications can now add:\n\n- Late messages: a note when messages sent to the agent arrived after its last step. It says the agent is being resumed with them and will notify again, and to wait for that notification before resending.\n\n- Usage limits: a note that the agent's work so far is saved, and when the limit resets.\n\nBefore, only the general notification text was sent.\n\n**Why**\n\nClaude no longer resends messages that the agent is about to pick up anyway. It also knows the agent's work is not lost when a usage limit is reached.\n\n- Area: Subagents\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}