Omniscio

PM + Team Chat Integration (item mentions, sending to Mission Control, status updates)

A bridge between Mission Control boards and Team Chat that ships inside Team Chat: mentioning an item with # in the composer, sending a chat message to Mission Control, announcing item status changes in a channel, and listing an item's linked chat messages. Its off switch is the Mission Control box "Link Team Chat conversations". Covers each capability, the off switch, usage tracking, and the channels behind it.

On this page

What it is

PM + Team Chat Integration is the bridge between PM (Mission Control) and Team Chat, shipped as part of Team Chat. Four capabilities connect PM items with Team Chat conversations:

  • #item mentions -- type # in the Team Chat composer to open a PM item typeahead; selecting inserts a reference that renders as a rich inline chip (title + status dot) in sent messages.
  • Send to Mission Control from chat -- right-click a chat message, choose "Send to Mission Control", pick a board, and a new PM item is created pre-filled with the message text. Bidirectional link rows are inserted (message-to-item + channel-to-item). The create result reports linked (true/false): if the link writes fail the item is kept, the failure is logged with the item, message and channel ids, and linked: false comes back on the IPC and POST /pm/chat/items responses. The menu row is named for its destination on purpose: a separate "Create task" row files the message in the user's own Tasks project and belongs to Tasks, not to this bridge.
  • Status updates in channels -- when a PM item linked to a channel changes status (via sync), a system-style message appears in that channel showing the old-to-new status transition. Deduped by a deterministic client message ID. The channel's own workspace is recorded with the link, so an update still lands in the right channel after you switch to another workspace; if it cannot be posted, you are told why instead of finding a stale channel later.
  • Chat links on PM items -- the PM item detail drawer shows a "Chat Messages" section listing linked messages with preview text and timestamps.

Where to find it

All of this lives inside Team Chat, with one surface on the board side. The # typeahead is in the Team Chat composer, "Send to Mission Control" is on the right-click menu of a chat message, status messages arrive as system-style messages in the channel they belong to, and the linked-message list is the "Chat Messages" section of the PM item detail drawer.

Turning it on and off

  • It shows only while Team Chat is on (Team Chat is still a Lab feature, off by default) and Mission Control is on.
  • Its own switch is the Mission Control checklist box "Link Team Chat conversations": Mission Control settings, then How you work, then Customize, under Collaboration. Untick it to turn the whole bridge off; tick it to turn it back on. A board can also have its own choice.
  • Settings search finds it: search "Link Team Chat conversations" (or "team chat mission control") and the result opens Mission Control settings. It is listed only while Team Chat is on.
  • Its old Lab entry ("PM + Team Chat") is marked shipped, so the old pmTeamChatEnabled switch does nothing any more; the box replaced it.

How it behaves

  • A mention renders as a rich inline chip carrying the item's title and status dot, so a reference reads as part of the sentence rather than as a bare link.
  • Creating a task from a message inserts the link from both ends at once -- message-to-item and channel-to-item -- so the connection is visible whichever side you look from.
  • Channel status messages are deduped by a deterministic client message ID, so the same transition never appears twice.
  • A channel status message goes to the workspace its channel lives in, taken from the link, not to whichever workspace you are viewing when the update arrives. A link recorded before the workspace columns existed carries no workspace of its own and is treated as belonging to the company (org) workspace, so it keeps updating instead of dropping out of every workspace.
  • Nothing appears unless Team Chat and Mission Control are on and the "Link Team Chat conversations" box is ticked: every renderer surface and every main-process handler checks all of them.
  • Desktop app only. Opened through the phone link, Team Chat shows no "Send to Mission Control" action, no # item typeahead and no linked-message list, and does not listen for status updates: all 5 pm:chat:* calls are blocked on the phone link because they read local data and Mission Control credentials on the computer. Plain Team Chat keeps working there.
  • Its speed cost is measured together with Team Chat's: Mission Control is on in both arms and this link is on only in the Team Chat-on arm, with linked task chips in the seeded messages. It runs no timers or background listeners of its own. Numbers: the Speed cost section of team-chat.md.

Both halves of this bridge have their own page: team-chat.md covers the built-in channels and DMs the mentions and tasks appear in, and mission-control.md covers the boards the items come from. pm-session-link.md is the sibling that links a board item to a working session rather than to a conversation. The full behavioural contract is recorded in pm-team-chat-integration-contract.md, and every other page in this library is listed in INDEX.md.

Last verified 2026-11-06