Companions act where the company already works — Slack, email, calendar, issue trackers, code — and anything else through MCP.
Built-in integrations
- Slack: companions are reachable teammates — they read channels, reply in threads, react, upload files, open DMs. An incoming Slack message routes to the right companion, and the answer goes back to the originating thread.
- Gmail: search and read email; sending and replying are available and disabled by default (explicitly enabled per companion).
- Google Calendar: list, create, update, and cancel events.
- Jira: fetch, search (JQL), create, update, and transition issues.
- GitHub: follow pull requests and CI runs (the watchdog wakes a companion when a check completes or a PR merges), and react to repository events.
- Sentry: production errors become work items a companion can pick up and fix.
Email intelligence
Beyond raw email access, companions track business email: senders are classified automatically, threads needing a response are tracked and reminded, newsletter knowledge is extracted, and emails are mapped to the right project domain by pattern — so "waiting on a reply about the Acme contract" is something your companion knows.
Events and routing
External events (Slack, GitHub, Sentry, email) flow into a prioritized queue with per-company routing rules deciding which companion handles what — urgent events first, retries handled automatically.
Extensible through MCP
Any Model Context Protocol server adds new tools to a companion:
- Third-party or in-house servers, over stdio, HTTP, or SSE — OAuth-based authentication supported.
- Scoped sharing: an MCP server can be private to one companion or shared with the whole company's companions.
- Per-tool permissions: tool access is managed from the desktop settings, with sensitive outbound actions requiring human consent (see Security).