Menu β–Ύ β–΄

#381 feat(notifications): pause notifications from the tray and Dock menus

closed
nobody
None
2026-11-07
2026-11-07
Anonymous
No

Originally created by: kristofferR

Silencing Carrier for a meeting or the night meant toggling Mute Notifications in Settings and remembering to turn it back on, which is easy to forget for days.

A Pause Notifications submenu in the tray menu (macOS, Windows and Linux) and the macOS Dock menu offers:

  • For 1 Hour
  • Until Tomorrow Morning (08:00 local; today's if it is still ahead)
  • Until I Turn Them Back On (the existing Mute Notifications setting)

While paused, the menu shows "Paused until 14:30" and Resume Notifications, and Settings shows the end time next to Mute Notifications.

The pause is stored as an end time, not a timer, so it survives restarts and a pause that ended while Carrier was closed is already over. Native delivery, sync alerts and the page's global-mute gate all compare that time with the clock; the unread badge keeps counting. A watcher refreshes the menus when a pause ends, rechecking the wall clock every 30 seconds so sleep or clock changes cannot leave a stale "Paused" label.

Message notifications also wait while a Messenger call window (/groupcall/) is open, so banners don't interrupt a call. Other popups, such as login windows, don't count.

Stacked on [#378], whose global-mute gate the page side extends.

Manual check still needed: each menu on macOS, Windows and Linux (ksni); pause, restart, and confirm it holds and ends on time; a call window holds notifications back.

Ref [#348]

CodeRabbit reviews this change in the combined PR [#394].

Related

Tickets: #348
Tickets: #378
Tickets: #394

Discussion

  • Anonymous

    Anonymous - 2026-11-07

    Originally posted by: chatgpt-codex-connector[bot]

    Codex Review Summary: βœ… Completed This comment shows the latest Codex review activity on this pull request. | Review | Status | Commit | Review trigger | | --- | --- | --- | --- | | πŸ“ **Code Review** | βœ… **Completed** <relative-time datetime="2026-11-07T19:31:47.350176Z">2026-11-07T19:31:47.350176Z</relative-time> | `f8b6f9a` | Manual request |
    ℹ️ About Codex in GitHub
    [Your team has set up Codex to review pull requests in this repo](https://chatgpt.com/codex/cloud/settings/general). Reviews are triggered when you - Open a pull request for review - Mark a draft as ready - Comment "@codex review" or "@codex security review". Codex reacts with πŸ‘€ while any review is running, comments if it has suggestions, and reacts with πŸ‘ once all reviews finish with no findings.
     
  • Anonymous

    Anonymous - 2026-11-07

    Originally posted by: chatgpt-codex-connector[bot]

    Codex Review: Didn't find any major issues. Already looking forward to the next diff.

    Reviewed commit: 1258e8760f

    ℹ️ About Codex in GitHub
    [Your team has set up Codex to review pull requests in this repo](https://chatgpt.com/codex/cloud/settings/general). Reviews are triggered when you - Open a pull request for review - Mark a draft as ready - Comment "@codex review". If Codex has suggestions, it will comment; otherwise it will react with πŸ‘. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
     
  • Anonymous

    Anonymous - 2026-11-07

    Originally posted by: kristofferR

    ⏸️ crq will not request further automated reviews for this pull request.

    Reason: CodeRabbit reviews these changes once, in combined PR [#394]

    Resume with crq unhold kristofferr/carrier 381.

     

    Related

    Tickets: #394

  • Anonymous

    Anonymous - 2026-11-07

    Originally posted by: kristofferR

    [!NOTE]
    πŸ€– Claude Opus 5.5 responding on behalf of Kristoffer

    @codex review

     
  • Anonymous

    Anonymous - 2026-11-07

    Originally posted by: chatgpt-codex-connector[bot]

    Codex Review: Didn't find any major issues. πŸŽ‰

    Reviewed commit: f8b6f9a14d

    ℹ️ About Codex in GitHub
    [Your team has set up Codex to review pull requests in this repo](https://chatgpt.com/codex/cloud/settings/general). Reviews are triggered when you - Open a pull request for review - Mark a draft as ready - Comment "@codex review". If Codex has suggestions, it will comment; otherwise it will react with πŸ‘. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
     
  • Anonymous

    Anonymous - 2026-11-07

    Ticket changed by: kristofferR

    • status: open --> closed
     
  • Anonymous

    Anonymous - 2026-11-07

    Originally posted by: kristofferR

    βœ… The administrative hold has been retired because this pull request merged. crq will not request further automated reviews.

     

Log in to post a comment.