Skip to content

Commit 462355b

Browse files
nicofishmanclaude
andcommitted
docs: describe alert dismissal after reading a thread elsewhere
Co-Authored-By: Claude Opus 5.5 <[email protected]>
1 parent b30bbf8 commit 462355b

2 files changed

Lines changed: 2 additions & 2 deletions

File tree

‎docs/operations/android-notifications.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -68,7 +68,7 @@ vp run push:android:smoke /path/service-account.json /path/device.json completed
6868

6969
Supported states are `running`, `approval`, `input`, `completed`, `failed`, and `end`. Firebase acceptance is not proof that a device displayed the message. Check the actual notification, background the app, and test a notification tap. Also test dismissal, disabling ongoing activity, sign-out, token rotation, and delivery after the app process has exited. Android Settings **Force stop** intentionally prevents delivery until the app is opened again.
7070

71-
With the app in the foreground, Android suppresses an alert only for the thread currently on screen, matching iOS notification presentation; alerts for other threads still show. Activity cards still update in the foreground and retain finished results silently. Check that completion stays quiet while its thread is open, alerts while another screen is open, alerts after backgrounding, and that retrying a suppressed alert does not show it later. This uses the app lifecycle and route on the receiving phone, not thread visibility on other clients.
71+
With the app in the foreground, Android suppresses an alert only for the thread currently on screen, matching iOS notification presentation; alerts for other threads still show. Activity cards still update in the foreground and retain finished results silently. Check that completion stays quiet while its thread is open, alerts while another screen is open, alerts after backgrounding, and that retrying a suppressed alert does not show it later. This uses the app lifecycle and route on the receiving phone. Separately, reading a finished thread on any client publishes it as visited: the relay sends `dismiss_group` and the phone cancels that thread's alerts and summary, leaving other threads' alerts in place. Check that opening the thread on desktop clears the phone's alert.
7272

7373
With ongoing activity enabled, verify two threads entering approval/input together produce one `2 agents need attention` alert, and two observed active threads completing/failing together produce one `2 agents finished` alert. The body lists their titles. The relay shares iOS transition selection and retains its delivered baseline when work finishes; publishing the same states again must not produce another alert. Grouped alerts open the aggregate’s priority thread; individual alerts retain their thread link.
7474

‎docs/user/mobile-notifications.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ Sign in to T3 Connect, link your environments, and enable **Device Notifications
44

55
Enable **Ongoing Agent Activity** on Android or **Live Activity Updates** on iOS to follow work without opening the app. Finished results remain visible for up to 15 minutes. You can dismiss an Android activity card without disabling alerts; turn off ongoing activity in Settings to stop future cards.
66

7-
Ordinary alerts stay quiet while the mobile app is in the foreground. Ongoing activity continues to update. Viewing a thread on another device does not silence your phone's alerts.
7+
Ordinary alerts stay quiet while the mobile app is in the foreground. Ongoing activity continues to update. Once you read a finished thread on any device, its alerts are removed from your phone, and a thread you already read does not alert. iOS removes them on a best-effort basis: the system can delay the update, and it does not reach an app you force-quit until you open it again.
88

99
Android notifications require Android 7.0 or newer and Google Play services. Android 16 and newer can promote ongoing activity to a Live Update, subject to system settings and device support. Other devices show a regular ongoing notification. Android 7's battery-saving modes can delay removal of expired cards.
1010

0 commit comments

Comments
 (0)