⛔ #371 Support external_ref get-or-create on POST /chat/create +156 -1 13d ago by
christopher-soapbox ↗ analysis ↗ GitHub ## Summary
christopher-soapbox/mike-1
An early Mike fork exploring safer, duplicate-free chat creation for Slack-connected workflows.
christopher-soapbox is exploring an integration-friendly way for outside systems to create and recognise Mike chats using their own stable reference. The immediate use case is Slack: one conversation should map cleanly to one Mike chat, even if a request is repeated.
That is a practical workflow concern rather than a broad product repositioning. There is no tracked product divergence to try yet, but the direction suggests interest in making Mike easier to connect to existing chat-based operations. Curious readers can follow the GitHub link for the underlying discussion.
What's in it
- Stable external chat references A proposed option would let an integration reuse its own conversation reference and receive the existing Mike chat instead of creating a duplicate.
- Slack-friendly chat workflows The stated aim is to keep Slack threads from spawning multiple Mike chats for the same conversation.
Direction
integrationworkflow
Activity
📝 Christopher-soapbox wanted Slack threads to stop spawning duplicate Mike chats 0 commits — integrationchat-ui draft
The proposal would let an outside system recognise a conversation without separately storing Mike's internal chat ID.
Threads of work (detailed view)
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.
Pull requests (detailed view)
⛔ Closed without merge (1)
by
christopher-soapbox · opened 13d ago · closed 13d ago