MC Chat Bot (Mission Control alerts posted into Team Chat)
A bot that posts Mission Control project-health alerts — at-risk items, cascading delays, pattern detections, health drops and periodic digests — into a Team Chat channel, so your team sees project risk without opening Mission Control. Off by default; covers the five alert categories and the settings that configure it.
On this page
What it is
A bot that posts Mission Control project-health alerts into a Team Chat channel so your team sees project risks without opening Mission Control.
What it does
The MC Chat Bot monitors your Mission Control boards and automatically posts categorized alerts into a designated Team Chat channel. It surfaces five categories of project intelligence:
- at-risk — items flagged as at risk of missing their deadline or target
- cascade — cascading delays where one slip affects downstream items
- pattern — detected patterns in project data (recurring blockers, velocity anomalies)
- health-drop — a board's overall health score dropped significantly
- digest — periodic summary of board activity and status
Each alert carries a severity level — info, warning, or critical — and the bot only posts alerts at or above your configured severity threshold (default: warning).
The bot posts under Omni's name, or the custom name you gave Omni in Settings > Mission Control > Name your assistant, no longer under "Mission Control".
Where to find it
There is no settings screen and no sidebar panel for it yet. The four mcChatBot* settings exist in AppSettings and are validated on write, but nothing in the GUI writes them — no Settings section, no MC Chat Bot panel anywhere in the sidebar (no file under src/renderer names mcChatBot at all). The alerts it posts land in whichever Team Chat channel mcChatBotChannelId names, so the bot itself has no panel of its own.
The supported way to configure it today is the control server, not the config file: GET /mc/team-chat/bot/config reads the current settings and PATCH /mc/team-chat/bot/config writes them (src/main/services/cli/cli-server-mc-bot-routes.ts) — that PATCH is the same validated write path a UI would use. The same file also exposes POST /mc/team-chat/bot/post and POST /mc/team-chat/bot/digest to fire an alert or a digest on demand. Only if you have no control server to hand do you write mcChatBotEnabled plus the channel id into the settings directly.
How it behaves
How to set it up
The mcChatBot* settings (no UI writes them yet — set them directly):
| Setting | Default | What it does |
|---|---|---|
mcChatBotEnabled |
false |
Master on/off toggle |
mcChatBotChannelId |
'' |
The Team Chat channel to post into |
mcChatBotMode |
event-driven |
event-driven (post as events happen), digest (periodic summary only), or both |
mcChatBotSeverityThreshold |
warning |
Minimum severity to post (info / warning / critical) |
Asking it a question
The bot can also answer a question in a channel, behind the in-development AI Team Chat switch (aiTeamChatEnabled). It is off for every channel until that channel's creator turns it on.
- Turn it on: the channel's creator opens Edit channel and flips Mission Control answers questions in the AI in this channel section. Only the creator sees that section, and each switch saves the moment it is flipped. The same section holds Omni can summarize this channel, the switch for Omni's channel summary.
- Turn it on for an agent: an agent or Mission Control can read and flip the same two switches over the CLI with
GETandPATCH /team-chat/channels/:channelId/ai, under the screen's own rules: AI Team Chat on, only the channel's creator, and answers only in a private channel or DM. An agent's own token also needs Let agents write to Team Chat with their own token on. - Ask: start or include
@mc(or@mission-control) in a message. The bot replies in the channel with a message labeled Answer. - How often: it answers at most once a minute in a channel and about ten times an hour from one person, and it only answers a question that is really in the channel — a stale channel listing with no message behind it gets no reply.
- What it can see: only boards that the person asking AND every other member of the channel belong to, with each member's own column visibility applied. Because everyone in the channel reads the answer, a board one member cannot see never shapes it.
- When it says no instead: in a public channel (everyone in the workspace can read it), in a channel with more than 50 people, or when no board is shared by everyone, it posts one short fixed reply and asks no AI.
- When the AI comfort level is Low: if the channel creator's AI comfort level is Low, or was never picked (an unpicked level counts as Low), the bot asks no AI and posts one short reply saying Mission Control's AI is off at that level, with a link to Settings > Mission Control > AI comfort level. Pick Medium or High there to turn answers on. It never goes quiet for this reason.
- Cost: each answer is one short AI call, held to the bot's existing small daily cap.
Known gaps: the bot answers only while the channel creator's Omniscio is running with that workspace open, because the creator's own desktop is the one that answers. Questions asked inside a thread are not watched. Public channels always get the fixed reply.
How it works
The bot runs in the main process and listens for Mission Control intelligence events. When an event matches the configured mode and meets the severity threshold, it composes a message and posts it to the designated Team Chat channel via the TEAM_CHAT_MC_BOT_RECEIVED push channel. The push payload carries the channel id, message text, bot name, category, severity, and the board ids involved. Every payload stays inside the limits the stored message allows (mc-bot-meta.ts): a digest reports at most 50 boards and the control-server digest route refuses more, message text is trimmed to the Team Chat message limit, and a client message id that would run past 128 characters is hashed.
Related
- mission-control.md — the boards whose health this bot reports on.
- communication.md — Team Chat itself, where the alerts arrive.
Last verified 2026-11-06