Mobile Settings
The Settings tab provides access to app configuration — daemon connection, push notifications, app lock, chat session security, and device preferences. Several screens show your daemon’s configuration read-only; change those settings on desktop.
Settings sections
Section titled “Settings sections”| Section | What it does |
|---|---|
| Profile | Your name, email, and timezone from the daemon (read-only) |
| Agent Behavior | Default model, strategy, and proactivity (read-only) |
| AI Providers | Which providers have API keys configured, with keys masked (read-only — manage keys on desktop or CLI) |
| Notifications | Opt in to push notifications — see below |
| Security | Biometric app lock — see below |
| Chat Sessions | Session security settings for remote session joining |
| Voice | Your daemon’s speech-to-text and text-to-speech providers and their status (read-only) — see Voice Input |
| Themes | Preview and apply looks, including Supporter-exclusive themes |
| Interface | Haptics and text size, stored on the phone |
| Memory | Memory stats and settings from the daemon, plus local cache management |
| Connection | Daemon address, endpoints, health check, and re-pairing — see Connection & Auth |
| Channels | Status of connected messaging channels (set them up on desktop) |
At the bottom of the tab, Disconnect unpairs the phone from the daemon, and the footer shows the app version.
Notifications
Section titled “Notifications”Push notifications are opt-in. The screen shows whether notification permission is granted and has a Request Permission button; granting it registers the phone’s push token with your daemon. A Send Test Notification button checks that notifications display on the phone.
The screen also has Task Updates, Agent Alerts, and Security Events toggles. They’re saved on the phone but don’t yet filter what the daemon sends. See Push Notifications for what the daemon currently sends.
Security
Section titled “Security”Turn on Require Face ID / fingerprint to lock the app behind your device’s biometrics. When enabled, the app asks for biometric unlock when it opens and whenever it returns to the foreground. If the phone has no biometric hardware, the screen says so and the toggle isn’t shown. If you haven’t enrolled a fingerprint or face, the app falls back to letting you in rather than locking you out.
Supporter
Section titled “Supporter”The card at the top of the tab opens Support Snippbot, an optional one-time Supporter purchase through Google Play. It unlocks a Supporter badge and three exclusive themes; all core features stay free. Restore purchases brings it back after a reinstall or on a new device when you use the same Google account.
Demo mode
Section titled “Demo mode”If you tapped Explore the demo on the pairing screen, the app runs on built-in sample data and nothing leaves the device. Settings → Connection shows a demo notice until you pair with a real daemon.
Data and privacy
Section titled “Data and privacy”- Device tokens are stored in the device’s hardware-backed keystore
- The app talks only to your own daemon — there is no Snippbot account, and chats are not routed through Snippbot servers
- The app has no third-party analytics or telemetry SDK; crash reports go only to your own daemon
- Chat history is stored on your daemon, not on-device
- Clearing app data removes local credentials but not server-side data
