feat: generic hook relay + notification badges

[aterrylu]

Summary

Event bus architecture for Claude Code → autonomOS communication. A single hook script relays ALL lifecycle events to the server, which decides how to handle each one.

graph LR
  CC[Claude Code] -->|hook event JSON| HS[autonomos-relay.sh]
  HS -->|POST /api/hooks/:id| S[Server]
  S -->|stores| N[Notifications]
  D[Dashboard] -->|polls every 3s| S
  D -->|shows badge| SB[Sidebar]

Loading

Key design decisions:

• Env var gating: Only sessions spawned by autonomOS have AUTONOMOS_SERVER set. Regular Claude Code sessions are completely unaffected.
• Fire-and-forget: 2s timeout, async, silent on failure. If the server is down, the hook exits cleanly.
• Server-side handling: The hook is a dumb pipe. All logic for what constitutes a "notification" lives on the server, so we can iterate without redeploying the hook.

What's included

Component	File	What it does
Hook script	packages/server/hooks/autonomos-relay.sh	Reads stdin event JSON, POSTs to server
Hooks API	packages/server/src/routes/hooks.ts	Receives events, stores notifications
Session env	packages/server/src/sessions.ts	Injects AUTONOMOS_SERVER + AUTONOMOS_SESSION_ID
Store	packages/dashboard/src/store.ts	notificationCounts, fetch/mark-read actions
Sidebar	packages/dashboard/src/components/Sidebar.tsx	Blue dot badge, mark-read on click

Test plan

• Start a session via dashboard — verify AUTONOMOS_SERVER is in env (env | grep AUTONOMOS)
• Regular Claude Code session (outside dashboard) — AUTONOMOS_SERVER is NOT set
• Trigger a Notification/Stop/PermissionRequest event — blue dot appears on sidebar
• Click the session — badge clears
• Kill the server, trigger hooks — no errors in Claude Code, no delay

🤖 Generated with Claude Code