Skip to content

ADR: Web Push for agent attention #1459

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
rsindall wants to merge 3 commits into
base: main
Choose a base branch
from
Open

ADR: Web Push for agent attention #1459

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
ce0fef2
adr: Web Push for agent attention
rsindall Sep 20, 2026
0f28ab4
adr: shorten Web Push pitch to informal CONTRIBUTING style
rsindall Sep 20, 2026
f549172
adr: match upstream pitch style for Web Push note
rsindall Sep 20, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions adrs/web-push-needs-attention.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
# Web Push when an agent needs you

QM already shows "needs attention" in the browser, but that only helps if the tab is open. With chat bridges turned off, there's no lock-screen ping when an agent stops or is waiting on an answer.

I'd like optional first-party Web Push for those existing attention moments. Opt-in only. Small payload: title, short body, deep link into the session. No prompts, secrets, or tool output in the notification. Reuse the attention signals you already have rather than inventing a parallel event bus. VAPID keys as deploy config. Chat connectors stay for teams that want them; this is for people who live in the web UI.

What I'm not asking for: replacing Slack or email, rich media, action buttons that mutate agent state, pushing transcripts, or promising every OS and browser on day one.

Open calls if you're aligned: which statuses should fire (waiting vs failed vs both), whether multi-device users get one notification per subscription or a short coalescing window, and what to document for iOS home-screen install. Happy for you to implement once the direction looks right.
Loading