Why connect Slack
Your team already lives in Slack. Architecture calls happen in #engineering, roadmap trade-offs in #product, critique in #design, approvals in #ops — and the reasoning behind each one scrolls away by Friday. Connecting Slack to SageOx closes the gap between where the work is discussed and where it's remembered — so the knowledge your AI coworkers capture shows up in the place your team is already looking, and the conversations your team is already having become knowledge your coworkers can use.
Today: your captured knowledge, delivered to Slack. Once you link a channel, SageOx publishes distilled knowledge straight into it — session recaps, the decisions a discussion settled, and the distillations your AI coworkers produce. Nobody has to log into a separate app to find out what was captured; it arrives in the channel, in context, as it happens. A #decisions, #product, or #design channel becomes a living, searchable record of what your team concluded and why — written for you, not by you.
This is currently one direction — publish only. SageOx pushes knowledge out to Slack; it does not yet read your Slack conversations back in. Native capture is on the way (below) — we're calling the current scope out plainly so the integration does exactly what you expect and no more.
Coming soon: two-way — Slack conversations become Team Context. Native capture is next: the discussions your team has in #product, #design, and everywhere else will flow into Team Context automatically, transcribed, distilled, and indexed alongside every other conversation. A decision made in a thread becomes something your AI coworkers can cite months later — no bridge, no bot to wire up, no copy-paste. Publish plus capture is the whole loop: Slack as both an output surface for your team's knowledge and an input source for it.
Set up Slack
Open your team's integration settings
Go to Settings → Integrations for your team and find the Slack card.
Connect your workspace
Click Connect and authorize SageOx in Slack. This installs the SageOx app into your workspace so it can post to the channels you choose. It does not read your workspace's messages.
Choose where to publish
Add a publishing destination and pick a channel — a #decisions, #product, or #design channel works well. You can publish to more than one.
Confirm it's working
The next time an AI coworker distills a discussion, the recap posts to the channel you linked. No bot to babysit.
What gets published
- Session recaps — what an AI coworker worked on and concluded.
- Decisions — the calls a discussion settled, with the reasoning behind them.
- Distillations — the structured memory your coworkers extract from a conversation.
Raw transcripts and recordings are never posted to Slack — only the distilled knowledge, written to be read at a glance.
Slack is currently publish-only. SageOx posts knowledge to the channels you link; it does not read your Slack conversations. Native capture — turning Slack threads into Team Context — is on the roadmap.
What's next
- All integrations — the other chat platforms SageOx connects to.
- Team Context — where the knowledge SageOx publishes to Slack comes from.