Event-to-delivery pipeline#

Remote creates notifications from persisted chat events, not directly from a single interactive request. This covers interactive runs, scheduled runs, and recovery paths.

flowchart LR Event["Persisted chat event"] --> Classify["Choose notification type"] Classify --> Audience["Choose users"] Audience --> Presence["Remove users watching"] Presence --> Devices["Load devices"] Devices --> Encrypt["Encrypt and sign"] Encrypt --> Send["Send Web Push"]

Event classification#

Persisted event	Result
`AskUserQuestion` starts	Urgent question notification
Interactive `complete`	Turn-finished notification
Interactive `error`	Run-failed notification
Scheduled `complete` or `error`	Scheduled-task notification
Other event	No notification

When a run stops after AskUserQuestion, Remote suppresses the immediately following terminal event. Otherwise that routine event would replace the more important question notification in the tray.

Audience#

A project chat notifies project members and administrators.
A loose chat notifies every registered user.
Stale project access entries are discarded unless the email still belongs to a registered user.
Duplicate email addresses are removed.
A user currently viewing the chat is removed before device lookup.

Delivery#

Remote serializes the notification once, then sends it to every stored device for each remaining user. webpush-go performs payload encryption and VAPID request construction. Remote supplies the safe HTTP client and interprets the response.

Result	Action
`2xx`	Record the successful send time
`404` or `410`	Delete the retired subscription
Other error	Log the failure and retain the subscription

Question notifications use high urgency and a one-hour TTL. Other notifications use normal urgency and a 12-hour TTL.

Forked chats#

Forking still copies the full visible event history into the new chat. Those append operations are marked as historical replay, so persistence and workspace updates run while notification side effects are suppressed.

Current delivery gaps#

Devices are processed sequentially under one 30-second deadline.
There is no bounded queue or retry for 429 and temporary 5xx responses.