Notifications

Receive alerts when a subshell needs attention or completes a turn.

Before you start

Use a browser or installed PWA that supports notifications and secure contexts. The server must have the corresponding notification delivery setup available.

Enable alerts

1. Open the profile menu at the bottom of the server dashboard's sidebar, choose Preferences, and turn on Subshell notifications in the Notifications section.
2. In the same section, select Enable notifications on this device and allow the browser's permission request.
3. Choose Subshells in the dashboard sidebar, open the ⋯ menu on a session you own, and choose Notify when done.
4. Use Mute notifications to silence that subshell again.

Both the account master preference and the subshell's bell must allow delivery. A notification is not a substitute for checking the session's actual status.

Who receives alerts

Notifications go to the subshell owner's devices. Sharing does not subscribe another user, even when that user has edit access.

Agent-created helper panes start with the notification bell off and appear under Cross-agent comms. Their owner can enable the bell later.

Agent signals

Attention reporting depends on the harness's hooks and capabilities. A terminal-only shell does not report agent turn completion. A running agent waiting on background work may remain active rather than reporting completion.

For iPhone and iPad web push, open the home-screen web app and request permission there.

Next steps

Review Devices or Notification troubleshooting.

Edit on GitHub