Skip to main content
Composio Composio Composio connects AI agents to the apps their users already use. Orgo is a Composio toolkit, with the slug orgo. An agent built on Composio can create an Orgo computer, run code on it, read its screen, click and type, and stop or delete it, through the same session it uses for Gmail, GitHub or Slack. The toolkit has 34 tools, listed in Tools in the Orgo toolkit. It reaches Orgo with your Orgo API key, so it can do what that key can do and no more.
Computers the agent creates run on your Orgo account and bill to it, the same as computers you create from the dashboard, the API or the CLI.
Composio also works the other way round. Orgo’s own Connectors sign an agent on an Orgo computer into Gmail, Slack, Notion and other apps through Composio, as described in Composio inside Orgo.

Before you start

You need three keys:

Choose what the key can reach

The toolkit acts with the Orgo key you give it. Give it a key made for the agent, not your own account key.
  • Limit it to one workspace. A workspace-scoped key reaches that workspace’s computers and no others.
  • Limit what it can do. A key can be restricted to some permission groups at read or write, as described in API key permissions.
  • Give it an end date. A key can expire, as described in Key expiry and rotation.
The four template tools need an account-wide key: ORGO_LIST_TEMPLATES, ORGO_GET_TEMPLATE, ORGO_LIST_TEMPLATE_VERSIONS and ORGO_VALIDATE_TEMPLATE. With a workspace-scoped key they fail with 403 and the code workspace_scope_mismatch.
To cut the agent off, delete the key at orgo.ai/api-keys.

Connect your Orgo account to Composio

The Orgo toolkit signs in with an API key, not OAuth. Composio stores the key for one of your users, under the user_id you pass when you create a session. Connect it once per user. There are two ways to connect:
  • Let the agent ask. The first time the agent calls an Orgo tool with no connection, Composio’s COMPOSIO_MANAGE_CONNECTIONS tool returns a Connect Link. Show the link to the user.
  • Connect up front. Create the link yourself, before the agent runs, for onboarding or a settings page.
To create the link up front:
Replace user_123 with a stable ID for the person the agent acts for, such as their database ID. Open the link, paste the Orgo API key, and save. The key goes to Composio, not through your app or the model.

Give an agent Orgo tools

Create a session limited to the orgo toolkit, hand its tools to the model, and run the tool calls it asks for. Each example asks the agent to list your workspaces and create a computer.
Composio’s own guides cover the OpenAI provider, the Claude Agent SDK provider, and sessions over MCP.

Tools that ask for confirmation

Eleven tools change something you may not be able to undo. Each takes a required confirmed boolean, which the model must set to true only after the user approves that exact action: ORGO_CREATE_COMPUTER, ORGO_DELETE_COMPUTER, ORGO_SET_COMPUTER_POWER_STATE, ORGO_SUSPEND_COMPUTER, ORGO_RESUME_COMPUTER, ORGO_EXECUTE_CODE, ORGO_RUN_COMPUTER_AGENT, ORGO_CONTROL_POINTER, ORGO_SEND_KEYBOARD_INPUT, ORGO_DELETE_SCREEN and ORGO_DELETE_FILE.
confirmed is an instruction to the model, not a check. Composio does not send it to Orgo, and an agent running with no one watching can set it itself. Limit what the agent can do with the key, as described in Choose what the key can reach.

Find the IDs the tools need

  • workspace_id. ORGO_CREATE_COMPUTER needs it with your own Orgo key, and Orgo rejects a create without one. ORGO_LIST_WORKSPACES returns every workspace the key can reach, with its computers. Tell the agent which workspace to use, or let it call ORGO_LIST_WORKSPACES first.
  • computer_id. The computer’s UUID, the same ID as in GET /computers/{id}. ORGO_CREATE_COMPUTER returns it, and so does ORGO_LIST_WORKSPACES.
  • screen_id. default is the screen the computer boots with. ORGO_LIST_SCREENS returns the rest.

Tools in the Orgo toolkit

Every parameter, with its type and allowed values, is on Composio’s Orgo toolkit page.

Composio inside Orgo

An agent running on an Orgo computer, such as Hermes or OpenClaw, can use Gmail, Google Calendar, Slack, Notion and more through Orgo’s Connectors. Orgo connects some of those apps through Composio, so their sign-in pages show Composio’s name. Connecting an app there needs no Composio account of your own.

Composio or Orgo’s own MCP server

Use Composio when your agent already runs on Composio, or needs Orgo next to other apps in one session with one place for each user’s connections. For an MCP client that needs only Orgo, such as Claude, Cursor or Codex, connect Orgo’s MCP server directly. To call Orgo from your own code without either, use the API or the CLI.

Good to know

  • Composio’s tools call the same Orgo API as everything else, so the limits on your account apply, as described in Account limits.
  • A tool result comes back as Composio’s { "data", "error", "successful" } object, with Orgo’s response or error inside it.
  • Full reference: docs.composio.dev/toolkits/orgo.