Status: Available. Connect Slack from Settings → Integrations and authorize the channels Corivo should use.
Most decisions don't live in the codebase. Most context doesn't live in the wiki. It lives in Slack — in a thread that's three days old, with five people in it, that resolved the thing you're now being asked about.
With Slack connected, Corivo's agent draws on those threads as part of its context graph. You won't copy-paste threads into ChatGPT to give it the picture; you'll give Corivo the command, and the picture is already there.
What Corivo's agent does with Slack
Decisions. "Why did we go with the new auth provider?" Corivo searches the channels you authorized for the thread where the decision landed — and surfaces the cite, not just a guess.
Owners. "Who's the right person to ask about onboarding?" Corivo surfaces the channel where onboarding gets discussed, and who shows up most.
Recent context. "What did the team ship this week?" Corivo summarizes cross-channel activity in a way that lines up with what you have in tickets and PRs.
The thread you just closed. Corivo notices the thread on your active screen via screen context and can pull the rest of the thread, including messages above the fold, into context.
What Corivo reads in Slack
With the scope you authorize:
- Channels and DMs you explicitly chose to expose.
- Recent messages and threads in those channels.
- Participants and reactions on those messages.
What Corivo does not do:
- Read channels you didn't authorize.
- Post messages on your behalf.
- Auto-join channels.
- Persist Slack content to a Corivo server. Your local context graph stays on your machine.
Authorization
You'll authorize Slack once, scoped to the channels you choose. Corivo gets a token scoped to that authorization, stored on your device. You can revoke at any time from inside Slack's app management.