Description
Notification Management brings the personal attention queue into headless workflows, allowing users and agents to review and maintain it without the app UI. dots notifications lists records and unread counts, changes read, dismissed, unread, and archived states, performs safe bulk actions, edits preferences, and manages muted source identifiers.
The workflow is designed for operators and coding agents. It uses the same authenticated, company-scoped service contracts as the rest of Dots, so terminal or protocol convenience never creates a second source of truth. Inputs are validated before or at the route boundary, and outputs preserve identifiers and structured details needed for a reliable next step.
Selling Points
- Lets agents check attention demand before starting work.
- Supports precise state changes and bulk cleanup through explicit commands.
- Keeps preference changes and muted sources scriptable across devices.
- Separates archive, dismiss, and read semantics instead of collapsing them.
- Returns structured results suitable for dashboards and daily summaries.
User Story
At the start of a shift, an operator checks the unread count, lists the newest notifications, marks one for later, dismisses a resolved item, and mutes a noisy automation source. Their queue now reflects actual attention priorities. The result is a concrete, inspectable outcome that another person or automation can continue from without reconstructing hidden state.
Extension Surface
The surface is automatable: packages/cli/src/commands/notifications.ts exposes the supported notification state machine and preference routes. It does not allow external notification verbs to be registered. The rating reflects the most-open supported seam that is true for this capability, not a transitive implementation detail. The cited path is the operational proof: consumers can use the documented seam, while unsupported changes still require a core release.
Capabilities & Limits
- Capability: List, unread count, read, unread, dismiss, archive, and bulk read cleanup.
- Capability: Preference get and set operations.
- Capability: Muted-source list, add, and remove operations.
- Limit: The command family manages notifications already produced by platform sources; it does not define new delivery channels or source event types.
The limit is intentional product truth rather than missing documentation. Calls also remain subject to authentication, tenant selection, schema validation, and the permissions enforced by the authoritative service.
Implementation Map
packages/cli/src/commands/notifications.tspackages/cli/src/commands/notifications-client.tsdocs/cli/module-and-chat-commands.md