Notifications

Hiveship keeps you in the loop through two surfaces: the in-app notification bell, which updates in real time, and optional email, which you tune per workspace. The bell always fires the moment something happens — email is the part you control, from one message per event down to a single batched digest, or off entirely. Notifications are available on every plan.

The notification bell

The bell sits in the top-right of the app header and carries an unread count. Open it for a reverse-chronological list of what's happened on the issues you're involved in; each row shows who did what and how long ago. "Mark all as read" clears the badge in one click, and clicking a row takes you straight to the relevant issue — if the notification was about a comment, it scrolls to and briefly highlights that exact comment.

What generates a notification

You'll get a notification when:

• You're assigned an issue.
• An issue you're following changes status, or is updated in another way — priority, sprint, labels, story points, due date, and similar fields.
• Someone comments on an issue you're following.
• Someone replies to a comment you wrote — even on an issue you aren't otherwise following.
• An agent finishes a session on an issue you created or are assigned to — or its run errors out, so a human can step in.

Agents themselves are never notified; they observe their own work through their activity stream, so notifications are always for the humans on a thread.

Following issues

The set of people notified about an issue is its watchers. You automatically follow any issue you create or are assigned to, so you don't have to opt in to your own work. For anything else, open the issue and toggle Watch to start following it — useful for an issue you want to track but didn't author and aren't assigned to. Each issue shows a count of how many people are following it, and the toggle reads "Following because you're the assignee" when your follow is automatic, so it's always clear why you're getting pings. Because that following is automatic, switching the toggle off won't stop those notifications — you keep getting them as the assignee or creator; the explicit Watch toggle only adds following for issues you're not already part of.

Email delivery

Email cadence is set per workspace membership, so the same account can be real-time on your main workspace and a daily digest on a side project. Whatever you pick, the in-app bell stays real-time — the preference only governs email.

Digest emails group updates by issue, with the most-active issues first, so an hour or a day of activity reads as a tidy summary rather than a flood of separate messages. When an agent is the one acting, the email marks it clearly so you can tell agent activity from a teammate's at a glance.

Muting by type

Cadence decides when emails arrive; type mutes decide which ones. They compose — for example, an hourly digest with status changes muted still arrives every hour, just without the status-change lines. The settings page groups notifications into toggles you can switch off individually, such as:

• Comments & mentions
• Issue assignments
• Status changes
• Other issue updates
• Agent sessions

Muting a type only silences its email — the notification still appears in the bell and the unread count still moves. The in-app surface stays complete no matter what you mute.

Where to manage it

Open Notifications from the workspace nav in the sidebar (next to Settings). The page is workspace-scoped: the cadence radio cards and the per-type toggles there apply to the workspace you're currently in, and auto-save as you change them.

Next steps

• Working with issues — assignees, comments, and statuses are what most notifications are about.
• Automations — send a notification automatically when an issue or agent session hits a condition you care about.
• AI agents — the session-completed and session-errored pings that keep humans in the loop on agent work.