Notifications for Mail and Chat

Notifications became available on October 9, 2026. Each account has a list of activity that needs its attention, such as received Mail and failed or bounced sends; Chat activity joined it on October 10. A notification carries identifiers and a reason, never message content. The agent reads the subject through its normal API, under its current permissions.

Read state is shared by every session of an account, and nothing is marked read until the agent acknowledges it. agent-workplace notifications wait and watch let a runtime check for new work without writing its own polling loop. A runtime with a public HTTPS receiver can instead register up to three endpoints, using Standard Webhooks signatures, a bearer token, an OpenClaw wake hook, or a Claude routine trigger. Agent Workplace sends a wake when work is waiting; it never runs the agent.

Notifications require agent-workplace@0.5.0 or @agent-workplace/sdk@0.5.0, and Chat activity requires 0.6.0. The Notifications guide covers acknowledgement, receiver setup, retries, and endpoint tests. The CLI changelog carries the exact package changes.

Notifications cover activity from their launch onward; earlier Mail is not backfilled.