---
title: Venom Tasks notifications
description: Quiet hours that hold push and email until morning, notifications that open the comment they are about, muting one comment thread, the email when a workspace export is ready, and agent chats you started from an issue reporting back in your Inbox.
section: cloud
order: 84
audience: [user, operator]
sources: [services/nodejs-cloud/lib/tasks/deliver.ts, services/nodejs-cloud/lib/tasks/deliver-pure.ts, services/nodejs-cloud/lib/tasks/thread-mute.ts, services/nodejs-cloud/lib/tasks/agent-notify.ts, "services/nodejs-cloud/app/tasks/api/comments/[id]/mute", services/nodejs-cloud/components/tasks/settings/PersonalSettings.tsx, services/nodejs-cloud/components/tasks/CommentMenu.tsx]
features: [cloud.tasks]
---

This page covers what Venom Tasks tells you and when. Which events reach your Inbox, phone and email is set in
[Settings → Notifications](/docs/cloud/tasks-settings.md#notifications).

## Quiet hours {#quiet-hours}

Settings → Notifications → **Quiet hours**. Off by default. Turn it on and pick when it starts and ends (22:00 to
08:00 unless you change it; the window may span midnight). The times are in your own time zone, which Settings picks up
from your browser; until it has one, they are in UTC and the row says so.

During quiet hours:

- **Push waits.** Nothing is dropped. When quiet hours end you get one push, "7 updates while you were away", that
  opens your Inbox. Reading something in Venom during the night takes it out of that count.
- **Email waits.** An email due during quiet hours goes out when they end, as one email, still only for what you have
  not read.
- **Your Inbox fills as usual.**
- **Reminders you set still push.** A [reminder](/docs/cloud/tasks.md#reminders) is yours, for the time you chose.

Changing quiet hours (or turning them off) takes effect within a quarter of an hour for anything already waiting.
Every notification is still pushed at most once and emailed at most once, and the hourly limits on the settings page
still apply. Clock changes are handled: 08:00 means 08:00 on your clock, in summer and in winter.

Agents set quiet hours with `tasks_notification_settings_update`:
`{"delivery": {"quiet": {"on": true, "from": "22:00", "to": "07:30"}}}`.

## Open the comment {#links}

A push or an email about a comment or a mention in a comment opens the issue scrolled to that comment
(`/tasks/issue/ENG-12#comment-<id>`). The Inbox row's **Copy → Comment link** gives the same link.

## Mute a thread {#mute}

A comment's **⋯** menu has **Mute this thread** (and **Unmute this thread** once muted). It stops notifications for
replies in that thread only: you stay subscribed to the issue and still hear about its other threads and changes, and
someone who @mentions you in the muted thread still reaches you. Anyone who can read the issue can mute a thread for
themselves; it changes nothing for anyone else. Mute from any comment in the thread, its first comment or a reply.

The same entry is in the Inbox row's menu for a notification about a comment, and the toast after muting has
**Undo**. Deleting a thread removes its mutes.

| Endpoint | Does |
|---|---|
| `PUT /tasks/api/comments/{id}/mute` | `{muted: true}` mutes the thread the comment is in, `false` unmutes. Answers `{thread, muted, mutedThreads}` |
| `GET /tasks/api/issues/{id}` | `mutedThreads`: the threads (their first comments' ids) you muted on this issue |

MCP: `tasks_thread_mute {comment, muted}` (in the `core` tool set).

## Your export is ready {#export}

When a [workspace export](/docs/cloud/tasks-export.md) finishes, the person who started it gets one email, "Your Tasks export is
ready", with a link to Settings → Export and the time the file expires, and one push when they have push on. Both follow
your Push and Email switches and the organisation's, wait out your quiet hours, and are sent once. Without a mail
provider there is no email; the bell still shows the export as before. An export downloaded before the notice would go
is not announced.

## Agent chats from an issue {#agent-chats}

When you start an [agent chat from an issue](/docs/cloud/tasks.md#start-an-agent-chat), the chat reports back on that issue in **your**
Inbox, as Venom Tasks:

| Notice | When |
|---|---|
| Your agent chat finished | a turn ended with nothing waiting for you |
| Your agent chat needs you | it asks for an approval or asks you a question |
| Your agent chat stopped with an error | a quick chat's turn failed |

Only the person who started the chat hears about it, never the issue's other subscribers. Each event is told once, and
the same kind about the same chat at most once in ten minutes. They fall under the **Agent updates** row in Settings →
Notifications (Inbox on, Push and Email off by default; Agents' own push for chats is unchanged). A push or email about
one opens the chat. Nothing comes for an archived chat, or for an issue you can no longer open. The Inbox's **From agents**
filter shows them.

The chat on the issue's **Linked** section shows **needs you** for every kind of chat now, code and computer chats
too, while an approval or a question waits; it keeps refreshing until that changes.
