Corivo's screen context covers what's right in front of you. Connected tools cover the rest of the picture — the tickets, threads, docs, and emails that are part of your project but not on your screen at this exact moment.
Corivo supports a broad integration catalog from Settings → Integrations. This page documents the core tools most teams ask about first.
Tools you can connect today
Open Settings → Integrations and click Connect on any of the rows below. The tool's own OAuth flow handles login; tokens come back to your Mac and stay there.
| Tool | What it contributes |
|---|---|
| Notion | Pages and databases you authorize. Decision docs, specs, and the wiki context that codifies how your team works. |
| Slack | Channels and DMs you authorize. The thread where the decision was made; who's in conversation about what. |
| Gmail | Threads in labels you authorize. Recent emails, participants, the back-and-forth you'd otherwise summarize by hand. |
| Google Calendar | Events on calendars you authorize. Who's in your 3PM, what was scheduled with whom. |
| Google Docs | Folders you authorize. The spec doc, the meeting notes, the design that landed yesterday. |
| GitHub | Repos you authorize. PRs, issues, recent commits, the diff you're reviewing. |
| GitLab | Projects you authorize. MRs, issues, recent commits. |
| Linear | Issues, projects, and comments. What's in flight; the acceptance criteria; the project structure. |
| Feishu | Docs, messages, and tasks in workspaces you authorize. |
| Sentry | Issues and recent events you authorize. The alert, the deploy that introduced it, the trace. |
| Intercom | Conversations and contacts in inboxes you authorize. The customer thread that's about to escalate. |
| Mem | Notes you authorize exposure for. Personal capture and brain-dumps that already live there. |
Settings may show more tools than the list above. The principle is the same for each one: connect only what you actually use, authorize the minimum useful scope, and let Corivo call the tool when a command needs that context.
How authorization works
The same shape for every live integration:
- Click Connect in Settings → Integrations for the tool you want.
- The tool's normal OAuth flow takes over — you log in with your existing account, see exactly what Corivo is asking for, and approve or deny.
- Corivo gets a token scoped to what you approved. The token lives on your device.
Two consequences worth knowing:
- You can revoke any time, from the tool itself. Removing Corivo's access from inside Notion, Slack, etc. immediately stops Corivo from reading more.
- Tokens never leave your device. The data flows from the tool to your Mac directly — not through a Corivo server.
What Corivo does with what it reads
Corivo's agent calls these tools on demand when it needs the context to answer your command. Nothing is silently mirrored to a server; nothing is used to train ML models; nothing is sold or shared with third parties for advertising.
Beta-tier limits
While Corivo is in public beta, the integration-count limits in the paid pricing tiers (Free, Pro, etc.) aren't enforced. You can connect anything you have credentials for. Tier limits start applying when Pro launches.
Where to send requests
If there's a tool you live in and you don't see it in Settings yet, send a note to [email protected]. We triage by what real users actually need.