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.
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).
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) |
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.
For agents
Key files
src/shared/types/settings/mc-chat-bot-settings.ts— Zod schema + defaultssrc/shared/push-event-schemas/team-chat-mc-bot.ts— push-event payload schemasrc/shared/ipc-channels/team-chat.ts— IPC channel constantssrc/shared/feature-registry/workflow-coach-and-providers.ts— feature registry entry (mc_chat_bot)
Related
- mission-control.md — the boards whose health this bot reports on.
- communication.md — Team Chat itself, where the alerts arrive.
Last verified 2026-10-01