Christopher-soapbox wanted Slack threads to stop spawning duplicate Mike chats

The proposal would let an outside system recognise a conversation without separately storing Mike's internal chat ID.

integrationchat-ui

For a Slack bridge, one thread should map to one legal-AI conversation. Christopher-soapbox's proposed change would have allowed an integration to supply its own stable reference when starting a chat.

If the same person and reference appeared again, Mike would return the existing conversation rather than open another one. A new reference would create a fresh chat, while ordinary chat creation would continue unchanged. That is a small but practical piece of integration plumbing: the outside platform keeps using the identifier it already understands.

The pull request included checks for repeat, new and ordinary chat requests, but it was closed before merger.

So what Teams connecting Mike to Slack or another case-workflow system should care because reliable conversation matching is what keeps an integration from becoming a duplicate-chat factory.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?