Integrations

Integrations connect Cogno to the tools your team already works in. Most are sources — Cogno reads their activity as events the agent learns from. GitHub is the main action — where finished work lands as a pull request. See Concepts for how sources and actions fit the loop. Open Integrations from the left nav. Services use the same compact settings rows whether connected or not: name on the left, status and action on the right.

​

How the page is laid out

GitHub’s status comes from Workspace GitHub App connections. Google Calendar shows Connected when at least one calendar account is connected. Personal GitHub sign-in is managed separately in Account → Profile → GitHub. For services that open browser authorization, choose Connect once in the list. After confirmation, Cogno opens their settings. Direct visits to an unconnected service page still offer Connect and Setup guide; longer information on connected service pages is under Details. The Microsoft Teams row reads the current connection and your unfinished setup for this Workspace: While the state is loading, the button is disabled. If loading fails, Retry checks again instead of treating the connection as absent. Starting or resuming setup requires permission to manage integrations. Teams settings shows the connected Team and tenant names. Connect and Resume start Microsoft sign-in in a popup on the web, or in the system browser when using the Cogno desktop app. When approval is needed, choose Open admin approval or Copy approval link to share it with your Microsoft tenant admin. After approval, use Select a Team to choose one Team, then Connect Team to confirm. In Channels, choose Start importing or Stop importing for each channel and review its current status. In Chats, verify your Microsoft account once, then Include the group or meeting chats where the Cogno app is installed; each Project selects channels and included chats in its own Integrations settings. Existing tenant-wide connections retain their Event listening controls in compatibility mode until they are disconnected.

​

Set up an integration

These are the integrations you can connect today. Each has its own page with the connect steps.

​

Set Workspace Tool permissions

Slack, Microsoft Teams, and Jira connection settings list the agent capabilities that Cogno manages. Choose Block, Ask, or Allow for each capability. This Workspace value is the security ceiling: a Project can inherit or reduce it for the same connection, but cannot increase it. Autonomous runs deny Ask because nobody is present to approve the action. Each capability names the Tools it grants. Under the choice, Tools lists every Tool an agent may call through it — search_slack_messages, send_slack_message, and the rest — so the choice is not read from the description alone. A Tool carries a check when the current mode runs it without asking, a question mark on a dashed outline when the mode asks first, and a struck-through name when the mode blocks it.

​

Coding agents

Integrations also lists Claude Code and Codex under Engineering. These are the coding agents Cogno runs on your machine to implement tasks — there’s nothing to connect on this page. Choosing Configure opens that coding agent’s page: an Overview of what it does on your machine, what it can do for you, and a Learn more about coding agents link.

• In the desktop app, select Configure to jump to Settings → Machines and set that coding agent up on this computer.
• On the web, the page is marked Desktop app feature — agent runs happen on your own machine, so the coding agent is set up from the desktop app. Get the desktop app links to the download.

See Run an agent on a task for how agent runs work and how to follow them.

​

Your connectors

Open Account → Connections to control your personal MCP servers. Settings follow your account across machines and projects. On Desktop versions that support only a shared switch, Enable / disable all controls Claude Code and Codex together. Off prevents personal connector use in Cogno runs. On uses each CLI’s existing settings and permissions; it does not force every configured connector to connect or grant new service access. Rows show Reject when off and Uses CLI settings when on. The shared switch remains usable without a Desktop update. A new shared choice replaces previous per-connector choices for both CLIs. Separate Claude/Codex bulk controls and per-connector Allow, Ask first, and Reject require a Desktop version that supports individual control. Those choices are not shown as editable on an older Desktop. On a supporting Desktop, expand Claude Code or Codex. The All connectors row places Enable all and Disable all above the indented server list. Both groups default to off when no preference has been saved. Changing Claude Code does not change Codex. Individual edits show Some connectors enabled when the group has mixed settings. You can allow one server after switching everything off, or reject one after switching everything on. New servers follow the group’s last bulk choice until individually edited. Saved changes apply from the next turn, including the next turn of an existing conversation. They do not cancel a tool call that is already running. Connection errors, sign-in requirements, and provider permissions still apply. Connector credentials stay with Claude Code or Codex. Ask first requires a new decision for each call, including in a full-access Session. Refresh re-reads the machine’s server inventory; it does not change permissions. A project’s folder can add more servers, listed under Project MCP servers in project settings. Older Desktops show their shared-switch status; supporting Desktops can edit their individual choices in the same account preference. See Set up a project.

​

Coming soon

The page also lists planned integrations with Coming soon and no connection action.

​

Related docs

• Concepts — how sources and actions feed the loop.
• Work with Tasks — where a connected source shows up on the task it created.
• Run an agent on a task — hand a task to a coding agent on your machine.
• Getting started with Cogno — set up the loop end to end.