Connect Composio

Composio is the broker behind Cyborg7’s agent integrations. It handles the sign-in with each provider (Gmail, Notion, Jira, and many more) and exposes their actions to an agent as tools. You connect the Composio account once on a machine. After that, connecting an individual app takes a few clicks.

Requirements

• You can sign in with Composio in your browser.
• You have a machine that is online. The Composio connection is stored per home machine (the machine an agent lives on), and only that machine’s owner can set or remove it.

Step 1: Connect your Composio account

1. In Cyborg7, open an agent and go to its Tools step.
2. At the top, click Connect next to Integrations account not connected. Once connected, the line reads Integrations · <email> with a Disconnect link.
3. In the dialog Connect an integrations account to give your agent tools, click Continue in browser →. Sign in with Composio in your browser. Cyborg7 fetches the key automatically. The dialog shows Waiting for sign-in… for up to 10 minutes. After that it shows “Sign-in timed out after 10 minutes. Try again.”
4. To paste a key instead, and if you own the machine, click Paste a key manually and fill in Account key and (optionally) API key.

Self-hosted setups can instead set COMPOSIO_API_KEY (and COMPOSIO_CONSUMER_KEY) in the environment of the machine that hosts the agent, then restart it.

Step 2: Connect an app

Use either place:

• Settings → Integrations: find the app, click its row, and use Connect account (Your account) or, for admins, Connect shared account (Shared account). See Connect an integration.
• The agent’s Tools step: pick the app’s card under For this agent and complete the provider’s sign-in.

Approve the scopes in the provider’s window. The app then shows Connected.

Step 3: Grant it to an agent

1. Open the agent’s Tools step.
2. Under For this agent, enable the app’s card.
3. Choose Acts as: Whoever runs it (the person who prompts the agent) or Shared account (for scheduled or unattended runs).
4. Optionally open the per-action picker to see which actions the agent gets, including any that the default cap drops.
5. Save.

You can also grant from the app’s sheet in Settings → Integrations with Agents with access → Add agent.

What a grant covers today

A grant is app-level, and the agent receives that app’s read actions: fetch, list, search, get. Two limits apply:

• Write actions are not granted. Send, create, update and delete are excluded. There is no approval policy to configure yet, and an action left waiting for one would never execute, so nothing is placed there.
• When you pick no actions, the default read set is capped at 30 actions per app, in the order the provider returns them. A large app can lose the remainder, and the per-action picker shows which actions the cap drops. The cap does not apply to actions you pick yourself.

Troubleshooting

• “Sign-in timed out after 10 minutes.” Click Continue in browser → again and finish the sign-in in the browser window.
• Your browser blocked the sign-in window: click the open it manually link that appears.
• An app stays “Not connected”: the sign-in window was closed or blocked. Retry and allow pop-ups for Cyborg7.
• “No machine of yours is online, so personal accounts can’t be checked or connected.” Turn a machine on in Settings → Machines.
• An agent can’t see a tool: the app is connected but not granted to that agent (Step 3), the run needs a Shared account it doesn’t have, or the action is a write, or it fell outside the 30-action cap of the default grant.