amal66 brings Slack workspace context to Mike, with the brakes on

The proposal would let Mike draw on Slack conversations and knowledge while keeping write actions disabled by default.

integrationknowledge-management

amal66 set out to add Slack as an account-level connection, using Slack's official assistant-tool service. After authorisation, Mike could work with selected workspace context rather than treating Slack as a separate place to search.

Search workspace messages and conversations.
Read channels, threads, canvases and member profiles.
Keep tools that could change Slack switched off by default.

The work also strengthens the underlying sign-in process, addressing a Slack-specific handoff that could otherwise omit the permissions needed for authorisation. The improvement was designed to help other connected services too.

This pull request was closed without merging, so these capabilities are not part of Mike through this change.

So what Legal teams weighing Slack as a knowledge source should watch this direction: it aims for useful internal context without casually giving an assistant permission to act in the workspace.

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