Omniscio

Mission Control — templates, calendars, meetings and notifications (part 4)

Part 4 of the Mission Control page: how boards connect to the rest of the app and to the world outside it — board and recipe templates, the calendar overlay, session linking, the meeting bridge, voice actions, search and knowledge, outbound webhooks, and the notification intelligence that decides what is worth telling you.

On this page

What it is

This is part 4 of the Mission Control page. It covers everything a board joins on to: other features inside Omniscio, and systems outside it.

Where to find it

Mostly inside Mission Control (templates, the calendar overlay, notifications), with the outbound pieces configured in the integration or settings surface each one belongs to.

How it behaves

Calendar Overlay (Phase 5I)

PM due dates and sprint timelines appear as a visual overlay on the Calendar alongside Google Calendar events. Items with date or timeline column values render as CalendarEvents, color-coded by board with overdue items highlighted in status-error red.

How to use it: enable Settings -> Mission Control -> "PM due dates in Calendar" (on by default when Mission Control is enabled). Due dates appear as single-day or timed events; sprint timelines appear as spanning bars across the calendar. Click any PM event to see the board name, date info, overdue warning, and an "Open in PM" button that navigates to the Mission Control panel.

How it works (internals): the CALENDAR_LIST_PM_EVENTS IPC handler queries the pm_* SQLite mirror tables (joining pm_column_values with pm_items, pm_columns, pm_boards, pm_groups), filters for date and timeline column types, then transforms matching rows into CalendarEvent objects with PM metadata fields (source: 'pm', pmBoardId, pmBoardColor, pmOverdue, pmType). The calendar store fetches PM events in parallel with Google Calendar via Promise.all and listens to pm:sync-updated for live updates. The resolveEventColor() dispatcher routes PM events to getPmEventColor (board color or overdue red) while Google events use the existing cascade.

A Subscribe in your calendar button in a project's Calendar view (and a Calendar switch on Mission Control's own settings page) gives each person a private calendar link listing the due dates assigned to them, for Apple Calendar, Outlook or Google Calendar. Shown once, replaceable, no expiry, hidden until the cloud serves it — see Calendar subscription link.

Session Linking

Sessions can be linked to PM items bidirectionally. A linked session shows a PM item chip in the session header (accent-colored, displays the item name). Clicking the chip navigates to the Mission Control board; right-clicking unlinks.

Linking paths:

  • At session creation: pass pmItemId to createSessionWithPrompt (the sessions.pm_item_id FK is set in the INSERT)
  • After creation: the PM_SESSION_SET_LINK IPC channel sets or clears the link
  • From a PM item: POST /pm/items/:id/start-session CLI route spawns a new session pre-linked to the item, with PM context injected via pmSessionContextProvider

Status sync: registerPmAgentLink() listens to sessionEvents.on('statusChanged'). When a linked session changes status, it maps to a closed vocabulary (idle / running / needs_you / finished / error) and emits a PM_SESSION_LINK_CHANGED push event. The chip subscribes via usePushListener (300ms debounce) for live updates.

Data model: the FK is sessions.pm_item_id (nullable). A companion pm_item_links row (entity_type = 'session') keeps the link browsable from the item side. Both are written atomically in a SQLite transaction.

Time Tracker Bridge (hub-spoke #3)

The item card's Time tab lets users start/stop timers and view logged time against any PM item — directly from the board, without switching to the Time Tracker panel. monday.com paywalls this behind Pro/Enterprise ($16–26/seat/mo); here it is free.

Starting a timer creates a time_entries row linked via pm_item_id (+ denormalized pm_item_name for display). The existing single-running invariant auto-stops any prior timer. The Time tab shows a timer control (Start/Stop with live elapsed), an entries list (newest-first, up to 100), and a summary strip (total time + billable amount using derive-once money). Entries also appear on the Time Tracker Today screen with a PM item name chip.

The bridge uses 5 methods on window.__AMC_MISSION_CONTROL_SESSION__ (installed by MissionControlPanel.tsx): startTimerForItem, stopTimer, getRunningTimer, getTimeForItem, getEntriesForItem. Two new read-only IPC channels (time-tracker:pm-entries, time-tracker:pm-total) are web-access-blocked (desktop-only).

AI Draft in the item card's update box

The AI Draft button (the sparkles icon under the update box) writes a short progress update for the item, in the first person, and puts it in the box as plain text for you to edit before you post. Nothing is posted until you press Update.

The draft is built from what is already on this computer: the item's name, board and group, its filled-in fields, and its last five updates. Email, phone, people and location fields are left out, and past updates are scrubbed of email addresses, phone numbers and similar details, with authors' names replaced by "Author 1", "Author 2". The text is written by the cheap Haiku model, metered under its own pm-item-update-draft cost label with the same daily cap as the other one-click AI suggestions, and limited to 20 drafts a minute. When the item has not synced here yet, the daily cap is reached, or the AI is unavailable, the box shows a plain-English message and the button works again.

It is a desktop feature: the paired phone bridge refuses the channel, as it does every paid one-click AI call, so on the phone the button shows its "not available right now" message.

  • History: the button shipped in Feature Discovery Wave 12 with only its screen half, so it always failed (QA audit #20); the host side above completed it on 2026-10-27.

Meeting Bridge

Bridges PM boards and Meetings so action items flow from a meeting into board items and linked items are visible from both sides. Gated on missionControlEnabled AND meetingsEnabled.

Flow 1 — Push action items to a board. The ⋯ menu on a finished meeting note has a Send to board item (shown when Mission Control is enabled AND the meeting has unchecked action items). It opens a SendActionItemsModal (board picker → group picker → preview of unchecked items). Sending creates one board item per unchecked action item on the chosen board/group via the Mission Control backend REST API, links each via pm_item_links (entity_type = 'meeting'), and triggers a board sync. Partial failures are tolerated — the result reports { created, failed, itemIds }.

Flow 2 — Bidirectional linking. The finished note page shows a Linked board items section (MeetingLinkedItems) beneath the notes: chips for each linked PM item (navigates to Mission Control on click, X to unlink on hover), plus a toggle-open search bar that queries PM_SUGGEST_ITEMS with 250ms debounce and filters out already-linked items. From the PM item side, GET /pm/items/:id/meetings returns meetings linked to that item.

CLI routes (5 new routes under /pm/meetings/): POST /pm/meetings/push-action-items, POST /pm/meetings/:meetingId/links, DELETE /pm/meetings/:meetingId/links/:pmItemId, GET /pm/items/:id/meetings, GET /pm/meetings/:id/items. All feature-gated on both missionControlEnabled and meetingsEnabled.

IPC: 8 channels in pm-meeting-bridge.ts — push, list-boards, board-groups, link-set, link-remove, list-for-item, list-for-meeting, link-changed (push event). All blocked from mobile/web WS bridge.

Search & Knowledge Integration

PM items are discoverable through Omniscio's global search (Ctrl+K) alongside sessions, SMS, Slack, and other channels. Search uses two stages: FTS (LIKE on pm_items.name, enriched with status/assignee/due-date column values for the snippet) and semantic (cosine similarity over 384-dim embeddings in pm_item_embeddings). Results render with a KanbanSquare icon and navigate to the Mission Control virtual project on click.

Board-scoped and cross-board search: searchItems(db, query, filters) in pm-queries.ts accepts boardId, assignee, and status filters. The CLI exposes these via GET /pm/search?q=&boardId=&assignee=&status=.

Session-PM dedup: when a session is linked to a PM item via pm_item_id, the standalone PM result is removed from global search results — the session result represents both.

Embeddings: the pm_item_embeddings table stores 384-dim float32 vectors (1536-byte BLOBs) for each PM item, built from item name + board name + column values. Embeddings are auto-refreshed after each board sync (500ms debounce per item). Backfill runs in batches of 50. The embedding model runs in a utilityProcess child (per the embedding-worker-offload contract).

"Use as context": the Mission Control Cloud item drawer has a clipboard button that copies the full item context (fields, subitems, updates) for pasting into a session. It NEVER spawns a session (cost-safety).

PM_SUGGEST_ITEMS IPC: takes { query, boardId?, limit? } and returns semantically matching PM items for proactive suggestions.

Voice actions (Batch 3)

Five voice commands let you manage PM items hands-free via the wake word or Alt+V:

Phrase examples Action IPC channel
"create a task called deploy API" / "add an item named review PR" Creates item on first board pm:voice-create-item
"move deploy API to done" / "put review PR in backlog" Moves item to a named group pm:voice-move-item
"mark deploy API as stuck" / "set review PR to working on it" Sets a status column value pm:voice-status-update
"read deploy API" / "what is review PR" / "show me the homepage task" Reads item name + column values pm:voice-read-item
"show all items" / "list my tasks" / "get the board" Lists up to 20 items from first board pm:voice-list-items

The regex engine (voice-intent-regex-commands.ts) pattern-matches the transcript; the IPC handlers (pm-voice-handlers.ts) resolve items by fuzzy name match against the local SQLite mirror and proxy writes to the Mission Control backend via pmAuthedFetch. The renderer dispatch (voice-input-deps.ts) wires the five commands into the existing voice action registry.

Feature gating: works whenever missionControlEnabled is on and a board has been synced locally.

Semantic search / embedding pipeline (Batch 3)

An on-device embedding pipeline indexes PM item text (name + column values) using the shared ONNX embedding model, enabling natural-language search across all boards without API calls.

How it works:

  1. Items are embedded on first sync via a backfill (batches of 50, respects model readiness).
  2. On subsequent syncs, changed items are re-embedded (debounced 500ms) automatically.
  3. Search queries are embedded at query time and scored via cosine similarity against the stored vectors (threshold 0.4, top-K results).

Access points:

  • IPC: pm:semantic-search — the renderer or voice can invoke it directly.
  • CLI: GET /pm/search/semantic?q=...&limit=N&board_id=... — agents use this for natural-language item discovery.

Storage: pm_item_embeddings table (item_id, board_id, embedding BLOB as Float32Array, source_text). Reuses the shared embed() / initEmbeddingModel() from the embedding worker host. Deleted items have their embeddings removed automatically.

Outbound webhooks (Batch 3)

Register webhook endpoints that receive signed POST payloads when board events fire (the same BoardEvent objects the automation engine uses).

CLI routes (bearer + rate-limited):

Route Action
POST /pm/webhooks Register: { boardId, callbackUrl, events?, secret } → returns { id, boardId, callbackUrl, events }
GET /pm/webhooks?boardId= List active webhooks for a board (or all)
DELETE /pm/webhooks/:id Soft-delete a webhook

Delivery model:

  • Payloads are JSON-signed with HMAC-SHA256 (X-AMC-Signature header, X-AMC-Event: pm.board.event).
  • Up to 3 attempts with full-jitter exponential backoff (base 2s, capped at 16s).
  • After 3 consecutive failures a webhook is auto-disabled and an inbox alert is raised through the standard agent-alert push (ALERT_CREATED / ALERT_CHANGED).
  • On successful delivery the failure counter resets.
  • Event filtering: if events is set at registration, only matching event types are delivered; empty = all events.

Storage: pm_webhooks table (id, board_id, callback_url, event_filter JSON, secret, is_active, failure_count, last_failure_at, soft-delete).

Project Templates (Phase 5E)

Save a board's full structure as a reusable template and deploy it into new boards. Right-click a board in the left nav → "Save as template" opens a dialog (name, description, shared/private visibility, include-items toggle). Templates are stored on the backend and browsable via a Template Category Picker (opened from the "T" button in the left nav header). The picker shows a two-level modal: first a grid of project category tiles (Boards, Dashboards, Documents, Spreadsheets, Forms) plus a "My Saved Templates" tile, then clicking a category drills into its templates. Documents, Spreadsheets, and Forms each have built-in templates that deploy as their respective entity types (not boards) via EntityTemplateDeployPreview. A back arrow returns to the category grid. Each template carries a projectCategory field tying it to a category (defaults to 'boards'). Categories are defined in src/shared/types/pm-template-categories.ts.

Deploy preview shows the template's groups, columns, views, and automations. Each automation has a toggle and a cost badge ($) on actions that invoke AI or spawn sessions (detected by isCostBearingAction checking the action array for cli_session, auto_respond, summarize, ai_classify, ai_extract). Users can disable cost-bearing automations before deployment.

Template editor lets owners update name, description, icon, visibility, and the template's structure (rename/remove groups, columns, views, automations). Changes autosave with an 800ms debounce.

Portability: column references inside automations are replaced with stable templateKeys (col_1) on save and remapped back to real IDs on deploy (direct dictionary lookup via a caller-supplied key→ID map).

Recipe templates (bundled patterns)

25 bundled recipe patterns under resources/recipe-patterns/pm-*.pattern.json combine the PM CLI routes with the Recipe system for daily workflow automation. The 14 listed below (the daily, sprint, task-management and AI-analysis workflows) all use same-session execution mode with a single step that reads a bearer token from ~/.amc/cli-token and calls GET /pm/boards, GET /pm/boards/:id/items, etc. to produce markdown reports.

Daily workflows: pm-daily-standup, pm-whats-due-today (cross-board), pm-my-work-summary (cross-board), pm-end-of-day-report. Sprint/planning: pm-sprint-retro, pm-sprint-planning-prep, pm-workload-balance, pm-capacity-alert ("Alert When Team Is Overloaded" — passes Mission Control's own overload cards to your inbox, and stays quiet when nobody is overloaded). pm-workload-balance, pm-board-health-check and pm-priority-recommendation read the same shared workload answer (GET /pm/people/workload) and show counts only as facts; the blocked-items recipes suggest a review only for items stuck stuckDays or more days or holding up work due within a week. Task management: pm-task-decomposition (the only write pattern — creates subtasks), pm-blocked-items-report, pm-overdue-items-digest. AI analysis: pm-board-health-check, pm-priority-recommendation, pm-status-update-drafter, pm-meeting-agenda.

Pattern details: recipe-authoring-guide-patterns.md.

Data Import — tooling removed

A one-time Python migration tool formerly at monday-exports/ imported Monday.com xlsx board exports into the Mission Control backend via REST (discover → column-map.json → import). It successfully imported 29 boards (~1,900 items) across all 18 column types before removal.

The monday-exports/ tooling and its committed data were REMOVED from the repo for privacy — column-map.json was a real production Monday.com workspace export (59 real boards + real collaborators' first names committed as swimlane labels). Do not re-add a real workspace export to the repo; use synthetic data if the migration is ever re-run. Design spec (retained for reference): docs/superpowers/specs/mission-control-data-import-design.md.

Data import/export (Phase 5G)

Two CLI routes let agent sessions move data between files and Mission Control boards:

  • Export (GET /pm/data/export/:boardId?format=csv|xlsx|json|txt) — reads the board from the local mirror (the same rows every screen renders, so a board that has never reached the cloud still exports), transforms to the requested format, writes a temp file, returns the path. Includes CSV formula injection defense. A status or priority cell exports the label its column gives it: the cell's own stored display text is used when present, and when it is absent the label is resolved from the column's settings.labels through the shared pm-column-label-resolve helper — the same resolution the board renders with — so an export never shows a blank where the board shows a label. The export holds exactly what the exporter may see: a column whose permission level for that person's role on that board is hidden is left out of the file entirely, title and values both, using the same resolveHiddenColumnIdsForBoards decision the CLI board and item reads, search and the AI apply. A view (read-only) column still exports. The filter is applied where the board is read, so every format and any column-derived extra sheet inherit it.
  • Import (POST /pm/data/import { filePath, newBoardName?, boardId?, format? }) — reads a local file (CSV/XLSX/JSON/TXT), auto-detects format from extension, infers column types (14 types: status, priority, date, numbers, email, phone, link, checkbox, dropdown, rating, long-text, text, plus header-name heuristics), detects groups from a "Group"/"Section" column, and creates boards/groups/columns/items on the Mission Control backend. Caps: 5000 rows, 50MB file size, 20K chars per cell.

Works independently of the Phase 5A local mirror — calls the Mission Control backend REST API directly via pm-auth.

Notification Intelligence (G4)

An additive notification layer (shipped, active for all users) that routes PM board changes to inbox alerts with session-scoped batching, per-board mute/promote preferences, and due-date alerting. Runs alongside the existing pm-inbox-event-detector; uses its own pm_events and pm_notification_preferences tables.

Session-scoped batching: board changes are written to pm_events immediately (write-through, never in-memory). When a session reaches a terminal status (ended/error/archived/paused), all unnotified events for that session are grouped by board, filtered (mute, never-notify-actor), and surfaced as one inbox alert per board. Two listeners cover all engine types (Claude sessions via sessionEvents, external engines via SESSION_STATUS_CHANGED push).

Routing rules: (1) the Inbox level decides what can alert (see "What reaches your Inbox" below); (2) muted boards mark events notified without alerting; (3) your own changes never notify you, and changes made by your own AI sessions only alert at Everything; (4) promoted boards upgrade digest events to inbox severity. Events kept out of the Inbox are still recorded and stay in What Changed.

Due-date notifier: a 15-minute timer scans all boards for overdue and due-approaching items (within 24h) and deduplicates within a 24h window. It records every hit, but raises an inbox alert via raiseAgentAlert() only for items your Inbox level lets through — under Involves me, items assigned to you, items you follow, and anything on a board only you use. Overdue takes priority if both apply. An item the cloud sync brought onto this computer raises no overdue card for a due date that had already passed when it arrived, so a first sync of an old board does not announce years-old deadlines. That is judged date by date: another date on the same item that goes overdue, or comes due soon, after the item arrived still raises its card, and items created on this computer behave as before. Each due-date card has an Open item button that opens the board with that item selected; the offline edit conflict and failed-sync cards and Omni's failed-move card carry the same button. A batch-of-activity card, a board that keeps failing to sync, and Omni's failed-action, deadline-confidence and board-level notice cards have an Open board button; a paused automation's card opens that board's Automations page; a failing import source opens the board it feeds, or the Import page while it has none; and a GitHub review card opens the item its pull request is linked to.

How these cards look: every alert the inbox files under Mission Control (the pm- notices, but not Omni's) reads From Mission Control; the inbox grouping and alert-source.ts share one test for that, isMissionControlAlertDedupKey in src/shared/alert-inbox-group.ts. Only the normal notifications also wear the Mission Control teal-to-gold accent on their rail and icon tile: the due-date cards, the batch-of-activity cards, an automation's own notification and an automation waiting for approval (MISSION_CONTROL_NOTIFICATION_PREFIXES in alert-visuals.ts). Problem reports (a failing sync, an unreachable backend, an edit that could not be sent, a stopped or paused automation, a failing import or webhook) keep the plain alert look, so they never read as routine news. A new normal Mission Control notification joins that list to be branded.

Omni's cards are the mirror image. Every alert the inbox files under Omni reads From Omni, or the user's own name for it (activePmAssistantName(), through isAiProjectManagerAlertDedupKey in src/shared/alert-inbox-group.ts, the same test the inbox grouping uses). The renderer reads the live name; the agent-facing "Raised by" line built in the main process (alert-session-prompt.ts) registers no name source, so it always reads the default "Omni". The Omni look (the Omni icon, a cyan icon tile, rail and header wash; OMNI_ACCENT in alert-visuals.ts) goes the other way round from Mission Control: every Omni card wears it EXCEPT the problem reports named in OMNI_PROBLEM_PREFIXES (a failed action, a failed move, a session error, a budget warning, the daily-AI-limit warning), so a new routine Omni notice is branded with no extra step. A new Omni PROBLEM kind joins OMNI_PROBLEM_PREFIXES, or it will read as routine news.

Per-board preferences UI: PmNotificationPrefsPanel (React) with board notification mode (normal/muted/promoted), email mode (off/instant/digest), and digest frequency (daily/weekly). IPC channels: PM_NOTIFICATION_PREFS_GET/SET/LIST, PM_EVENTS_RECENT, PM_NOTIFICATIONS_UPDATED push.

CLI routes: GET /pm/notification-preferences, PUT /pm/notification-preferences, GET /pm/events.

Inbox source (Phase 5D)

Phase 5D adds a "board" inbox source that surfaces Mission Control board events as unified inbox rows. Six event types create rows: assigned to you, mentioned in an update, status changed (a real change by someone else, shown before → after; a later change shows up again), due date approaching (1 day), due date passed, and automation (a failed run, or a run that changed something that involves you — any item at Everything). Events are detected locally from the Phase 5A SQLite mirror tables on each sync -- no Mission Control API polling beyond what the sync service already does.

An item the cloud sync brings in is not a new item. A "New item created" row is written when someone creates an item on this computer (you, or an agent working for you), never for an item that only arrived through the cloud sync — a first sync of a board you had never opened here, for example, brings in every item on it without one notice each. Other kinds of change that arrive through the sync (an item archived or moved, a comment) still notify as before. Notices the sync wrongly raised before this rule were archived, not deleted.

An item that is already finished never raises an overdue or due-approaching row. The inbox only warns about a date that has passed (or is about to) on work that is still open — an item in a done group, or whose status reads as done, is exempt from both. Without the rule, finished work kept a red "is overdue" row that never cleared, and because an overdue row deliberately pierces quiet hours it also interrupted you instead of waiting. Other event kinds are unaffected: a finished item still raises its "status changed to Done" row. See

A muted assignment raises no "assigned to you" row. When someone assigns you with the people picker's Mute toggle on, your inbox gets no assignment row for that item, just as the cloud bell stays quiet. The board still shows you as assigned, the item's other rows (a status change, a due date) still appear, and the change is still in the item's history. An assignment, like a mention, never pops a desktop notification. See

How to use it: enable Settings → Features -> "Mission Control board events in inbox" (on by default when Mission Control is enabled). Events appear as inbox rows with a status-coloured dot routed through the status-* tokens (so custom themes recolour it): the needs-you attention colour for most events, and the error colour for overdue items. Items are grouped by board (each board gets its own collapsible section) and sorted by priority (overdue first, then due-approaching, then assigned, then status-changed, mentioned, automation-fired).

One row per item. However many updates an item has (a comment, a status change, an assignment), it shows as a single inbox row and the badge counts it once. The row's text is the newest update, for a comment New comment on <item>: "<excerpt>"; its dot is the most urgent update's colour (overdue wins).

Click a row to open the timeline alert:

  • a chip line with board › group, the status, the due date (overdue in red, approaching in amber) and N updates today
  • the item's recent updates, newest first: the newest is marked NEW; a comment shows who wrote it, when, and its full text; a status or field change shows old → new. Status changes and assignments show what changed but not who (the Mission Control server does not send the actor for those)
  • a reply box: type and press Send (or Ctrl+Enter). The reply is posted to the board for teammates and appears in the timeline at once; when the newest update is a comment it threads under it ("Reply to <name>…"). A member who can only view the board sees a short note instead
  • a Mission Control footer: the teal-and-gold Mission Control mark, the board and group, and the last-update time, over a faint orbit watermark

The alert keeps five inline actions:

  • Mark Done — transitions the item via the Mission Control API and dismisses the item
  • Snooze — dismiss and re-surface later (tomorrow, next week, custom)
  • Reassign — dropdown of board members, updates the people column via API
  • Change Date — inline date picker, updates the date column via API
  • Open in Board — navigates to the Mission Control board panel

Dismissing (or Mark Done) hides the whole item; a new update on it brings it back. From the command line, GET /pm/inbox/timeline?boardId=…&itemId=… returns the same timeline, and POST /pm/items/:id/updates posts a comment. The timeline is a members-only read: rows are trimmed to boards the caller is a member of, so a caller with no role on the board gets an empty timeline rather than its history.

What reaches your Inbox (Inbox level): Mission Control → Settings → Updates sets one level for all your projects:

  • Everything — every change except your own.
  • Involves me (the default) — things assigned to you, that mention you, that you follow (an item, its group, its board, or a portfolio), and everything on a board only you use (a board where nobody else appears, such as a Tasks board).
  • Mentions me — only mentions.
  • Nothing — no Mission Control updates in the Inbox.

If you never choose, the level is Everything when your setup answers say you run a department or you picked the Operations style, and Involves me otherwise. If you already used Omniscio before this setting existed, it starts on Everything (even if Mission Control was switched off then), so nothing you were getting disappears; pick a level any time to change it. Two switches sit beside it, both on: Tell me when an automation fails and Tell me when an automation changes something that involves me. At Everything the second one covers any item, not only yours. Due and overdue rows never go wider than Involves me: even at Everything you only get them for things assigned to you, things you follow, and boards only you use. A teammate giving one of your items its first status counts as a status change. The Mission Control project events in Inbox switch in Omniscio Settings still turns all of it off. Changes kept out of the Inbox stay in What Changed. There are no per-board dropdowns any more: boards you had set to "None" stay muted, and boards set to "Assigned to me only" behave as Involves me.

Quiet Hours: suppress PM inbox notifications during a configured time window (pmInboxQuietHoursStart / pmInboxQuietHoursEnd, e.g. 22:00–07:00, in the chosen pmInboxQuietHoursTimeZone). Events still persist, the store still updates and the inbox card still appears; only the Mission Control desktop notification and its sound are held. Overdue items always pierce quiet hours.

Daily Digest: PM events participate as a pm-events source in the daily digest system. When digest mode is active (pmInboxDigestMode), the individual desktop notification is held at every hour in favor of the combined daily summary. Overdue items always pierce digest mode.

How it works (internals): the main-process pm-inbox-event-detector subscribes to the pm:sync-updated push. On each sync it queries the pm_* mirror tables, resolves the current user (cached from GET /auth/me), extracts rich card fields (assignee, status, due date, column IDs for mutations), detects which events are active, upserts them into pm_inbox_events (dedup on event_type + item_id), soft-deletes cleared events of ITS OWN types only, and emits inbox-pm:updated if changed. Event-driven types (comment, created, moved, archived, field, sprint, automation) are bridged in by recordBoardEvents, which refreshes the row's id and time for each new event and emits inbox-pm:updated once per call; the detector never clears those (BRIDGED_INBOX_EVENT_TYPES). Comment events carry the comment id and real time into pm_events.metadata. The renderer's pm-inbox-store (createDerivedInboxStore) listens for the push; pmInboxSelectItems groups records by item into one integration: 'board' row (per-board projectIds kept for smart grouping). Dismiss uses the universal far-future snooze pattern (kind 'board') over every record of the item. The detail pane (BoardDetailPane in ApprovalPaneShell) reads inbox-pm:item-timeline (listItemTimeline: pm_events joined to pm_item_comments, account- and visibility-scoped, off the main thread) and posts replies through inbox-pm:reply (postItemComment, shared with the CLI comment routes).

Last verified 2026-11-03