Notifications
Open Settings → Notifications to inspect notification permission, open Android’s category controls, and check push-registration warnings.
Permission and categories
Section titled “Permission and categories”The first row reports Notifications allowed or Notifications blocked. Blocking notifications prevents request alerts; background request delivery continues.
On Android 13 and later, Allow notifications appears when the app lacks notification permission. Tap it to request permission through Android. If Android continues to block notifications, use its notification settings to enable them.
| Category | Status and purpose |
|---|---|
| Requests needing action | Shows Enabled or Blocked by Android settings. Alerts you about pending decisions, pairing attempts, and secret uploads. |
| Background processing | Shows Silent notification shown or Silent notification hidden. Used while Agentknock checks for and processes incoming work. |
Tap a category to open its Android settings. Android controls its sound, vibration, lock-screen visibility, and interruption behavior. Agentknock initially creates the action category with high importance and the background category with low importance, no sound, and no vibration. Your Android settings determine their subsequent behavior.
Hiding the background processing notification does not stop request processing. The app refreshes the displayed notification settings when you return from Android settings.
Opening and deciding requests
Section titled “Opening and deciding requests”Tap a request notification to open that request in the appropriate tab: Requests, Secrets for an upload, or Clients for pairing. Any required app unlock or device setup happens first.
Notifications for secret use, SSH authentication, and Git signing offer Deny once and Allow once while a decision is available. They apply to the individual request and do not create temporary access or change an approval mode. Pairing and uploads require review in the app and do not offer these decision buttons.
On Android 12 and later, notification decision buttons require the device to be unlocked. On earlier supported versions, Allow once opens the request in the app for review; Deny once can act from the notification. If the request has already ended, an old notification cannot make it active again.
Request notifications include context such as client, requested secrets, command, and available review information. Agentknock supplies a generic Request waiting public version for lock screens that hide private content. Android’s visibility settings control what appears. Background notifications are marked to stay off the lock screen.
Push delivery needs attention
Section titled “Push delivery needs attention”The Delivery section appears when push registration is incomplete or rejected:
- This device has not finished registering: Agentknock will retry registration.
- The relay rejected the registration: Agentknock will retry after the rejected registration.
These warnings describe push registration, independently of notification permission. Enabling alerts does not itself repair registration. The warning disappears when registration is reported as complete.
For connection state, refresh, and request errors, see Requests. For broader delivery problems, see Troubleshooting.