Omniscio

Ops Engine (PM Operations Engine)

The rule-based operations layer of Omni. It watches agent sessions linked to board work and acts on per-board policies, and its dashboard now opens from the Operations row on the Omni page.

On this page

What it is

The Ops Engine surfaces operational metrics and execution health for Omni, and runs the rule-based automation behind them: it restarts stalled agent sessions, moves finished work and proposes actions for you to approve. It costs nothing to run (no AI calls).

Where to find it

The Ops Engine now lives inside Omni. It no longer has a sidebar item of its own.

  • Open it — on the Omni page (the AI Project Manager item in the sidebar), pick Operations at the bottom of the Projects list. The dashboard opens in the middle of the page. It shows on a computer while Mission Control is on; it is not shown on a phone.
  • Old links still work. A saved link, keyboard shortcut, bookmark, deep link or pinned toolbar button that pointed at the old Ops Engine opens the Omni page instead, and so does reopening the app when it was last closed on the Ops Engine.
  • One switch. The engine runs only while Turn on Omni is on. Its old Settings → Lab toggle is gone and the old setting is ignored.

How it behaves

The OpsEngineDashboard view renders six component sections over data fetched via PM_OPS_GET_DASHBOARD, PM_OPS_GET_SHIFT_HANDOFF, and PM_OPS_GET_ACTION_LOG IPC channels:

  • Workspace Health (WorkspaceHealthWidget) — blocked, overdue and stalled counts, plus how many projects are off track, at risk, on track or not judged yet, colored from those on-track verdicts (no score)
  • Active Agent Sessions (ActiveAgentSessionsWidget) — how many of your agents are working now (running, starting or waiting): sessions on none of your boards count too, and the per-project list names the boards in this workspace. A guest copy of someone else's shared session, a private project's session and a session the app hides are left out
  • Risk Heatmap (RiskHeatmapWidget) — projects ranked by risk, with workspace, timeframe and "At risk only" filters and honest "Not enough data yet" rows (see pm-predictive-analytics.md)
  • Shift Handoffs (ShiftHandoffCard) — unread handoff summaries, each with Mark read. Each shift raises ONE inbox card for every workspace together (pm-ops-handoff:shift), titled by the part of the day the shift started in your own clock ("Omni's morning report", afternoon, evening, overnight, or "Omni's catch-up report" when it spans days) and reading like "9:04 AM to 1:04 PM: Omni took 3 actions on 2 projects. 2 done. 1 waiting for your OK." A shift where Omni did nothing reads "a quiet shift. Omni had nothing to do." Quiet shifts are NOT reported by default: the Report quiet shifts switch (Settings → Mission Control → Omni, and Omni's own settings; pmOpsQuietShiftReportsEnabled, off by default since November 12, 2026) turns them on for anyone who wants the reassurance that Omni is still watching. Busy shifts are always reported, and every report is still saved. Here in the Control center the same switch applies: off, no quiet briefing is listed; on, one quiet briefing stands for the shift (not one per workspace), and its Mark read marks them all read. The card has an Open shift report button that opens this panel. A report covers only the boards of the account that made it, so two people sharing a workspace each see their own; a report from an older version that mixes both people's boards is hidden from both
  • Decision Queue (DecisionQueueItem) — pending proposed actions, each explained in plain words: what Omni wants to do and why (for example "The agent working on Launch page finished. If you approve, Omni moves it to Done."), what Deny does ("If you deny it, nothing changes."), the Project and Item by name, and when Omni asked. Each has Approve, Deny (Deny asks first) and, when the request is about one item, Open item. It shows one board's queue: the first board by deadline confidence, unless you came from an inbox card. The card a new proposal raises (pm-ops:<board>:<action>:<item|board>) shows the proposal on the shared approval layout with Approve (Enter), Deny and Open decision queue. It names things in plain words, never by an internal ID: the title reads "Omni needs your OK: Send notification on Launch AI assistant feature" (the item, or the project for a project-wide proposal), and the body carries the same explanation as the queue row: what and why, what Deny does, and the Project and Item. Every other Omni card does the same (see "Omni's cards speak plainly" below). A board or item that no longer exists reads as "an item that no longer exists" (and the like). A card raised before this change keeps its old wording until it is answered or expires. Approve and Deny decide that proposal right on the card, through the same approve and deny the queue uses, then archive the card. The card finds its action at click time: the key names one board, action and item, and the engine allows only one open proposal for that trio. If the proposal was already decided or has expired, the card says so and archives without deciding anything; if the answer is refused, the card stays. All three buttons are desktop-only, like the rest of the drill-in. Open decision queue opens the drill-in on that proposal's board with the proposal highlighted; approving or denying it there returns the queue to the first board
  • Daily action budget (OpsDailyBudgetPanel) — how many automatic actions the engine has used today against its daily limit (pmOpsDailyActionBudget, default 200), when the count resets (midnight UTC, shown in your own time), and an Actions per day field to change the limit. It is a count of actions, never money; starting or restarting a session counts as 10 (pmOpsSessionSpawnCostWeight)
  • Project rules (OpsPolicyPanel) — pick a project, then set each of the ten actions to Do it automatically, Ask me first or Never. An action with no rule of its own reads Default: it asks you first, unless you have approved that action 5 times in a row on another project. A change keeps the rule's stored cooldown and reason, and saving needs the project's owner or admin role
  • Notification Preferences (PmNotificationPrefsPanel) — per-board prefs

An empty state is shown until boards are connected and workspace data populates. Nothing loads until a Control Center widget, an Ops inbox card or the portfolio heatmap button opens it.

Three inbox cards now open these sections. The approval-streak card (pm-ops-trust:, you approved the same action 5 times in a row) and the auto-escalation card (pm-ops-auto-escalation:, an action runs automatically on a project with no rule of its own) have Open project rules, which opens the drill-in on that card's project with that action's rule highlighted. The budget cards (pm-ops-budget-80, -90, -exhausted) have Open daily budget, which opens the drill-in scrolled to the budget. On a brand-new install the budget cards are held for the first day, like other startup cards, and the next crossing raises them again. Every Operations card button, including Open decision queue and Open shift report, opens the drill-in itself rather than only the Omni page. Rules can still be changed through POST /pm/ops/policies or by accepting an Omni recommendation, and the budget through the settings API.

Omni's cards speak plainly

Every card that lands in Omni's inbox is written for someone who is not an engineer: it says what happened and whether anything is needed, names projects and items, gives times in the person's own clock, and uses the assistant's chosen name. No card shows an internal ID, a raw timestamp, "UTC", "PM Ops", an action code such as update-status, or the machine's own error text (that stays in the app log). Examples:

  • An agent is waiting for an answer: Omni raises no card at all. The agent's own row in Needs You already says it is waiting. Before November 12, 2026 Omni asked "Omni needs your OK: Send notification on ..." for this, and until November 13 it raised "The agent working on Launch page needs your answer".
  • An agent working on an item stops with an error: Omni asks once, "The agent working on Launch page stopped or hit a problem. If you approve, Omni restarts it" (or restarts it on its own, by the project's rules), and the session waits under Interrupted. Until November 13 Omni also raised a separate "The agent working on Launch page hit a problem" card for the same error. Both retired cards, and their switches in Settings → Notifications, are gone; any left in your inbox are cleared the next time Omni starts.
  • A finished item could not be moved: "Omni couldn't mark Launch page as done".
  • An approved action did not work: "Omni couldn't finish: Move item".
  • Requests nobody answered in 24 hours: "2 requests for your OK ran out of time".
  • The daily action limit: "Omni has used 80% of today's actions … The count starts over at 6:00 PM" (the reset is midnight UTC, shown in your own time).
  • A deadline under strain: "Product Roadmap may miss a deadline" with the due count, a due date like "Nov 14", the team's pace and the chance of finishing on time.
  • The assistant's own AI limit: "Omni is close to today's AI limit".
  • The 8 AM digest: "What changed yesterday: 9 updates in 2 projects", one line per project, then the biggest changes.

The words live in three pure builder files (omni-card-copy.ts, omni-status-card-copy.ts, shift-card-copy.ts under src/main/services/pm/ops/), translated into every shipped language. The names of the card types — what a card's Options menu offers to turn off, and what Settings → Notifications lists — read the same way: "Omni shift reports", "Omni asking for your OK", "Omni's daily action limit", "What changed yesterday", and "All Omni project updates" for the switch that covers every Omni project card.

A saved rule always belongs to its project's own workspace: the app reads it from the project when the rule is saved, so neither the panel nor a CLI caller sends one (a workspaceId in the request is ignored). Saving a rule for a project that is gone is refused. Until T-184 (2026-11-04) the panel stamped every rule with a made-up workspace default; nothing reads that value, and each such rule is corrected the next time it is saved.

The Ops Engine is part of Omni, so ai-project-manager.md is the page that hosts it and mission-control.md is the parent product. pm-intelligence-advisor.md is its nearest sibling — that one turns the same board data into advice, where this one reports execution health. Several widgets here are backed by the forecasting layer in pm-predictive-analytics.md, and the per-board notification preferences it renders are documented in pm-notification-preferences.md. The full list of library pages is in INDEX.md.

Last verified 2026-11-02