Slack + Kylon: Your AI agent for what was decided

Every team has a decision that was made in Slack and never written down. It was argued out over two days in one channel, confirmed in another, and now nobody can find it. Search returns forty messages and none of them is the answer.

A Kylon agent can search the channels you give it, read around the hit, and tell you what was decided, by whom and when, with the message it came from.

What the connection can do

Slack is connected with OAuth from your own workspace. Once it is, an agent in a room can:

• Search channels and messages across the workspace your account can see
• Read the context around a message, so a decision is not quoted out of the argument it came from
• Send a message to a channel, after a person approves it

This is your own account, not a shared one. You connect Slack from your workspace with OAuth, you choose which rooms and which agents can use it, and you can revoke it at any time. The agent works inside the permissions your Slack account already has, nothing wider.

Reading around the message is the whole point

A message that says "fine, 15 percent then" is meaningless on its own. It matters that it came after two people argued for 10, that it was said by the person who owns the number, and that nobody objected afterwards.

So the agent reads the messages around the one it found, names who said it, and gives you the link. If the only evidence is a joke in another channel or a secondhand quote from a DM, it says so instead of counting it.

What a question looks like

Someone asks in the room: where did we land on the enterprise renewal discount?

The agent searches the channels it has access to, comes back with four messages that actually decided something, each with the person and the date, and separates what was decided from what was merely suggested. If the account team keeps asking the same question, it writes the summary as a message for the channel, and waits for someone to approve it before posting.

Why it lives in a Kylon room

Because the answer usually has to meet something that is not in Slack: the record, the contract, the number in a table. An agent in a Kylon room has both, so the answer arrives next to the work it affects instead of scrolling away.

Getting started

Connect Slack from your workspace, put an agent in the room where the decisions matter, and ask it the question your team keeps re-asking. Add the channels it should read as you go.