Notifications

The point of C3 Mobile is not watching agents — it's being interruptible. Notifications close the loop: when an agent blocks on a decision, your phone tells you, and Signal tells you what.

Opting in

Notifications are off until you enable them in Settings → Notifications. Your phone registers its push token with each paired bridge over the encrypted channel; the bridge — not any C3 service — is what triggers delivery through the platform push systems (FCM on Android, APNs on iOS).

What a notification contains

Always and only:

C3 — An agent needs your attention.

plus a random identifier. No host name, no agent name, no session, no prompt text. Push infrastructure (Google's and Apple's servers) learns that something happened — never what or where. Tapping through opens the app, and the attention queue has the specifics, fetched over your encrypted hub connection.

Delivery behavior

• Debounced — rapid-fire events from one agent collapse (3-second window) instead of buzzing repeatedly.
• Rate-limited — at most one notification per device per 30 seconds.
• Self-cleaning — if the platform reports a device token dead (app uninstalled, token rotated), the bridge drops it automatically.

If notifications don't arrive

1. Confirm the opt-in in Settings, and that the OS allows notifications for C3 Mobile.
2. Check the bridge is running (c3bridge service status) — a stopped bridge can't send.
3. Re-check c3bridge devices on the host: your phone should be listed with push enabled.
4. Battery-saver modes on some Android vendors defer push; exempt C3 Mobile if timeliness matters.

NOTE — > Notifications are best-effort by design — the decision surface is the app, not the notification. Nothing is ever approved, rejected, or executed from a notification itself.