Notification access

With notification access CX could read incoming notifications: power the notification_received workflow trigger, list and reply to notifications, click their actions, read verification codes for the browser agent, and auto-forward chosen apps to your Telegram.

In this build#

Google Play Protect blocks sideloaded apps that ask for Notification access, so the standard CX Agent build ships without the notification listener. Settings → Notifications (notification access page) then shows: "Notification reading is off in this build."

Builds made with the cx.notificationAccess=true option include it. In those builds:

1. CX shows an in-app disclosure first.
2. Open Notification access settings and enable CX Agent.
3. The page shows Service: Connected, the default Telegram chat, Recent activity (captured notifications) and the Auto-route whitelist: apps whose notifications auto-forward to your default Telegram chat. Empty = nothing forwarded. Manage whitelisted apps lets you search apps and toggle each one.

Notification tools in such builds: list_recent_notifications (100-entry buffer), list_active_notifications, notification_reply (WhatsApp, Messages, Telegram…), notification_action_click, dismiss_notification, notification_status.