Push Notifications

Available on Android

Snippbot for Android is on Google Play (US-only rollout for now). iOS is planned but not available yet.

The Snippbot mobile app can receive push notifications from your daemon about session-join requests and agent activity, even when the app is in the background. Push is opt-in and off until you turn it on.

Turning notifications on

1. Open Settings → Notifications in the app
2. Tap Request Permission and allow notifications when Android asks
3. The app registers its push token with your daemon
4. Tap Send Test Notification to check that notifications display

Your daemon sends notifications through Expo’s push service, so the daemon’s machine needs internet access. No Snippbot server is involved.

What the daemon sends today

Notification	When
Session Join Request	Another device asks to join one of your chat sessions and owner approval is required
Agent reply	An agent replies in a conversation while no client is connected (at most one per conversation every 20 seconds)
Scheduled job results	A scheduled job or loop delivers its result to push

Notifications for task failures, insights, and channel messages are not sent yet.

Session join approvals

When another device requests to join your session and owner approval is required:

1. Your phone receives a Session Join Request push showing the requesting device name and platform
2. If Snippbot is open on the Chat tab, an in-app approval banner slides in with Approve and Deny buttons and a countdown
3. The request expires after 120 seconds if nobody responds, and the join fails

Tapping the notification opens the Chat tab.

Approval is partial today

Session-join approval works in-app only. These pieces are not built yet:

• Approve / Deny action buttons on the notification itself
• Biometric confirmation of approvals
• Push notifications for elevated tool-call approvals — those appear in the conversation as an approval card and are auto-rejected after 5 minutes
• Owner approval of new device pairing
• A full audit trail of approve / deny decisions

Android notification channels

On Android, notifications are organized into channels with configurable importance:

Channel	Importance
Default	HIGH
Approval Requests	MAX
Security Alerts	MAX
Insights	DEFAULT
Task Updates	HIGH
Channel Messages	HIGH

You can customize notification behavior per channel in Android Settings > Apps > Snippbot > Notifications.

Managing permissions

To change notification permissions later:

1. Open device Settings > Apps > Snippbot > Notifications
2. Toggle channels individually
3. Set importance level per channel
4. Configure Do Not Disturb exceptions for the approval channel

Push token registration

The app registers its push token with the daemon when you grant notification permission:

• Provider: Expo Push Notifications
• Token format: ExponentPushToken[...]
• Registration endpoint: POST /devices/{device_id}/push-token

Caution

Push notifications require a physical device. They do not work in the Android Emulator.

Troubleshooting

Not receiving notifications

1. Check permissions: device Settings > Apps > Snippbot > Notifications must be enabled
2. Open Settings → Notifications in the app and confirm permission shows as granted (this also re-registers the push token)
3. Verify the daemon connection in Settings → Connection
4. On Android, check that the relevant notification channel isn’t muted
5. Ensure the daemon can reach Expo’s push service (requires internet access on the server)

Approval requests time out

1. Keep Snippbot open on the Chat tab while you expect a join request — the in-app banner only appears for requests that arrive while the app is open
2. Respond within 120 seconds
3. Have the joining device try again after the request expires

Notifications arrive late

1. Battery optimization may defer notifications — exempt Snippbot in Settings > Battery > App battery usage
2. Check your daemon’s push delivery logs