Skip to Content
How-to guidesHow-to guidesNotifications inbox

Use the notifications inbox

/notifications is the unified inbox for everything that needs your attention. It’s grouped by type, with a link to the full-page list of each kind.

Page layout

  • Title: Notifications
  • Subtitle: “Items that need your attention.”
  • Empty state: ”✓ All clear — nothing needs attention.”

Sections

Agents awaiting activation

Agents in pending status. Each row:

  • Agent name
  • Time it was registered
  • “pending activation” tag
  • Activate → button → opens /agents/{id} in the Pending tab

Pending uninstall requests

When an MCPB or CLI agent has been deleted locally (npx @agentvalet/register uninstall) but is still active server-side, it appears here:

  • Agent name
  • Reason (if provided) and request time
  • Approve Uninstall (green) → marks the agent revoked server-side
  • Reject (red) → keeps the agent active and tells the local install to re-register

Agent self-reports

When agents call report_self_diagnostic (see Read agent self-reports for the full surface):

  • Severity badge — CRIT / ERRO / WARN / INFO
  • Title and body summary
  • Metadata: time, platform, agent ID
  • Review → button → opens the full report on /agent-reports

Agent registration requests

The same pending agents as the first section, but framed from the “requests we haven’t decided on” angle:

  • Agent name
  • Requested time + token expiration
  • Review → button → opens the approval card

Tip: notifications versus the queue

Notifications is broad — it surfaces anything that might need attention. The narrower pages (/approvals, /agents, /agent-reports, /anomalies) are where you actually action items.

Treat the inbox as the “did anything happen?” check; treat the action pages as the working surfaces.

Push notifications

If you’ve enabled push, most of these items also reach you via Web Push the moment they’re created. The inbox is the catch-up surface for when you’ve missed pushes or come back after a while.

Next