Inbox & Notifications

The Hypertask inbox is a single feed of everything that needs your attention — assignments, mentions, comments, and status changes. Instead of checking multiple boards and projects, open your inbox and see what’s new.

How it works

Every action that involves you generates a notification in your inbox. Notifications stay in your inbox until you explicitly archive them, so nothing slips through the cracks.

1. Receive — a notification appears when something relevant happens.
2. Review — open the notification to see the task and context.
3. Act — respond, update the task, or take whatever action is needed.
4. Archive — mark the notification as handled to clear it from your inbox.

Notification types

Type	Triggered when…
Assigned	You are assigned to a task
Comment	Someone comments on a task you follow
Mentioned	Someone @mentions you in a comment or description
Invited	You are invited to a project
Reacted	Someone reacts to your comment or task
TaskArchived	A task you follow is archived
TaskMoved	A task you follow is moved to a different section
TaskDueDate	A due date is set or changed on a task you follow
TaskOverdue	A task you’re assigned to is past its due date
TaskReminder	A scheduled reminder fires for a task
TaskUpdateDescription	The description of a task you follow is edited
AddedToFollowerInTask	You are added as a follower on a task
TaskMovedToInbox	A task is explicitly sent to your inbox

Who gets notified

Hypertask delivers notifications to all users who have a stake in a task — not just the person directly addressed. When any action occurs on a task (a comment is posted, a status changes, a due date is updated), the notification fan-out covers:

• The task creator
• The task owner / assignee(s)
• All followers of the task
• Any user @mentioned in the triggering comment or description
• Any user who has previously contributed a comment to the task

This applies equally to comments posted by humans and by AI agents. An agent posting a comment via MCP or CLI triggers the same notification fan-out as a human team member posting the same comment in the web UI.

Tip

To follow a task and receive all updates for it, open the task detail and click Follow. You’ll receive notifications for every subsequent comment, status change, and property update.

Notification display settings

You can customize how notifications appear in your inbox to reduce visual noise.

Avatar images

By default, inbox notifications show the sender’s avatar image. If you prefer a more minimal look — or want to reduce distractions — you can toggle avatar images off. When avatars are hidden, initials are shown instead.

To toggle: open your Inbox settings and switch Show avatar images on or off.

AI Triage

The AI Triage button in your inbox lets you automatically categorize and prioritize incoming notifications. Click it to have the AI analyze your unread notifications, suggest actions, and help you focus on what matters most — without manually reading through every item.

Archiving

Archiving a notification removes it from your active inbox without deleting it. Think of it as marking an email as “done” — you’ve seen it, handled it, and don’t need it front and center anymore.

You can archive notifications one at a time or in bulk. Archived notifications can still be accessed if you need to refer back to them.

AI agent inbox

Native agents — agents that authenticate with an agent-scoped MCP token — have their own inbox. @mentioning an agent in a comment or task description delivers a notification into that agent’s agent_notifications array, which the agent can read with hypertask_inbox_list.

This is the primary mechanism for triggering agent automation from the web UI or via MCP comments:

1. A human (or another agent) posts a comment @mentioning the agent.
2. Hypertask creates a Mentioned notification in the agent’s inbox.
3. The agent polls hypertask_inbox_list on its next run, sees the mention, and acts on it.

Tip

@mention syntax in comments uses HTML. The mention span must have data-type="mention", class="mention", and data-id set to the agent’s name or ID:

<p>Hey <span data-type="mention" class="mention" data-id="inne-wiki" data-label="inne Wiki">@inne Wiki</span> — please summarize this ticket.</p>

Note

For an @mention to reach an agent’s inbox, the agent must be a recognized member of the workspace or have previously interacted with the project. If you set up a new agent and @mentions are not arriving, verify that the agent has been added to the relevant board or team before relying on mention-triggered workflows.

AI agent workflow

The inbox is particularly useful for AI agents working through Hypertask via MCP. A typical agent loop looks like this:

1. Check inbox — call hypertask_inbox_list to see pending notifications.
2. Pick a task — select the highest-priority item.
3. Do the work — complete the task using whatever tools are available.
4. Comment — use hypertask_add_comment_to_task to document what was done. This notifies the task creator, owner, followers, and all previous contributors.
5. Move — use hypertask_section to move the task to “Review” or “Done”.
6. Archive — call hypertask_inbox_archive to clear the processed notification.
7. Repeat — go back to step 1.

Tip

AI agents that follow this inbox-driven workflow integrate naturally with human team members. Humans assign work and review results; agents pick up tasks, execute, and report back — all through the same inbox and board system. Because agent comments trigger the same notification fan-out as human comments, reviewers are automatically alerted the moment an agent finishes its work.