Scheduled messages were tracked only in one browser's localStorage, which caused two problems:
Other sessions of the same account couldn't see or cancel them.
After logout they still sent, and no client could show them.
Synapse lists every pending one through MSC4140 GET /delayed_events.
Change
New fetchScheduledMessages / parseDelayedEvents. They handle Synapse's delayed_events shape and the MSC's scheduled shape. Only non-state m.room.message events are kept, so call-membership delayed events are skipped.
The tray loads from the server on mount and on window focus. localStorage remains only as a first-paint cache and is left alone if the request fails.
Logout shows "N scheduled messages. Scheduled messages still send after you log out…", with Logout and keep scheduled messages and Cancel scheduled messages and logout.
Verified (local Synapse):
Second device: a message scheduled from another session. Before: the fresh session showed nothing. After: "1 scheduled message", which it can cancel.
Logout: a message scheduled 63 min out, then "Cancel scheduled messages and logout". The server's list goes from 1 to 0.
Unit tests for parsing and grouping. tsc clean · unit tests pass · ESLint clean.
Fixes #322.
Scheduled messages were tracked only in one browser's localStorage, which caused two problems:
- Other sessions of the same account couldn't see or cancel them.
- After logout they still sent, and no client could show them.
Synapse lists every pending one through MSC4140 `GET /delayed_events`.
**Change**
- New `fetchScheduledMessages` / `parseDelayedEvents`. They handle Synapse's `delayed_events` shape and the MSC's `scheduled` shape. Only non-state `m.room.message` events are kept, so call-membership delayed events are skipped.
- The tray loads from the server on mount and on window focus. localStorage remains only as a first-paint cache and is left alone if the request fails.
- **Logout** shows "N scheduled messages. Scheduled messages still send after you log out…", with **Logout and keep scheduled messages** and **Cancel scheduled messages and logout**.
**Verified** (local Synapse):
- **Second device:** a message scheduled from another session. **Before:** the fresh session showed nothing. **After:** "1 scheduled message", which it can cancel.
- **Logout:** a message scheduled 63 min out, then "Cancel scheduled messages and logout". The server's list goes from 1 to **0**.
Unit tests for parsing and grouping. `tsc` clean · unit tests pass · ESLint clean.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
https://claude.ai/code/session_017PCb59uY3UKqDqt7B6hzd5
The tray only knew what this browser had scheduled (localStorage), but
Synapse lists every pending one via MSC4140 GET /delayed_events. Load it
when the tray mounts and on window focus (localStorage stays as a first-
paint cache), keeping only non-state m.room.message events. Logout now
says "N scheduled messages still send after you log out" and offers to
cancel them.
Fixes#322
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017PCb59uY3UKqDqt7B6hzd5
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Fixes #322.
Scheduled messages were tracked only in one browser's localStorage, which caused two problems:
Synapse lists every pending one through MSC4140
GET /delayed_events.Change
fetchScheduledMessages/parseDelayedEvents. They handle Synapse'sdelayed_eventsshape and the MSC'sscheduledshape. Only non-statem.room.messageevents are kept, so call-membership delayed events are skipped.Verified (local Synapse):
Unit tests for parsing and grouping.
tscclean · unit tests pass · ESLint clean.🤖 Generated with Claude Code
https://claude.ai/code/session_017PCb59uY3UKqDqt7B6hzd5