Composio
A connector that lets agents act in a thousand-odd outside apps — Gmail, Slack, GitHub, Notion, Linear and the rest — through a service that already holds the logins. It is also the second road for Google: if you cannot sign in to Google directly, you can connect Google through your own Composio account and the built-in Gmail, Calendar, Drive, Sheets and Docs screens then work through it.
On this page
What it is
Status
On by default. Turn it off in Settings → Lab → Composio. Existing installs that had it saved as off are switched on once by a one-time migration; turning it off again after that is kept.
A connector that links Omniscio to Composio — an "auth-to-action" layer that manages logins for 1000+ external apps (Gmail, Slack, GitHub, Notion, Linear, …) and exposes them as agent tools. Path B (Omniscio-managed): you connect apps from a dedicated Composio screen, and Omniscio automatically injects your per-user Composio Tool Router MCP server into every spawned Claude session, so agents can act in those apps with no per-session setup.
User-brings-own-key: you paste your OWN free Composio API key. Omniscio stores it encrypted at rest and never returns it to the renderer.
Where to find it
Once the feature is switched on, Composio is its own row in the left sidebar, and that screen is where you paste your key and browse the catalog of apps to connect. Each app's sign-in then happens in your normal browser rather than inside the app. Nothing else in the app needs to be opened or configured for the tools to reach your sessions.
How it behaves
How to use it
- Make sure Composio is on (it is by default; Settings → Lab → Composio).
- Open the Composio tab in the sidebar and paste your Composio API key (create one free at app.composio.dev). Give that key read AND write access to connected accounts and auth configs, plus "Proxy execute" if you will use Google through it — Composio grants read-only by default, and a read-only key can list your apps but cannot connect one.
- Browse the app catalog and click Connect on an app (e.g. Gmail). Composio opens its own secure sign-in in your browser; complete it and return.
- Connected apps' tools are automatically available in every new AI session.
Clicking Connect reuses the app's existing sign-in setup when it already has one, and asks Composio to create its own managed setup only when the app has none. Either way the sign-in you complete is Composio's, so you never need a Google Cloud project of your own.
Google through Composio
Use this when you cannot sign in to Google directly (for example, while Omniscio's own Google sign-in is waiting on Google's approval).
It is automatic until Google approves Omniscio's own sign-in. While that approval is pending, every Connect Gmail / Reconnect Google button in the app (the Gmail page, Settings → Google Account, alerts, Quick Launch, the Docs tab, the setup wizard) goes through Composio by itself:
- With a Composio key saved, the press opens Composio's Google sign-in in your browser (one sign-in for every Google app) and the app waits — checking every 10 seconds, for up to 5 minutes — until Composio reports a NEW active Google connection, then lights up the Google screens. Reconnecting a Composio connection that went bad opens a fresh sign-in rather than trusting the old one. Pressing twice shares one wait.
- With no Composio key, the press opens the Composio tab and says plainly that a Composio key is needed; it never starts Omniscio's own (not-yet-approved) sign-in.
- A sign-in you finish later (after the 5 minutes, or from the Composio tab) is picked up the next time a Google screen checks its status — the app re-asks Composio at most once a minute, in the background.
- Already signed in to Google directly? Nothing changes: you keep your direct sign-in. Google test users and developers can also press Sign in with Google directly on the Gmail page to use Omniscio's own sign-in.
- When Google approves the app, one switch in the code (
GOOGLE_OFFICIAL_SIGN_IN_APPROVEDinsrc/main/services/google/google-oauth-client.ts) sends new connects back to Omniscio's own sign-in.
To connect by hand instead:
- Open the Composio tab (or press Connect through Composio on the Gmail page when Omniscio's own sign-in is the road).
- In the Google through Composio card, pick ONE of the two roads:
- Connect all Google apps — a single Composio sign-in that covers Gmail, Calendar, Drive, Sheets and Docs at once. Google shows one consent screen listing every permission together. This is the default road and the one most people want.
- Connect apps one at a time — one sign-in per app, and each one asks Google only for that app's own permissions.
- Finish the sign-in(s), then press Refresh. The card shows "Connected as <your address>" and which Google apps are connected.
Either road reaches the same place: once every Google app is covered — whether by one Google Super connection or by the five per-app ones — the card stops offering to connect and leaves only Disconnect. Both roads skip whatever is already connected, and neither can be started twice at the same time.
What changes once Google is connected this way:
- The built-in screens work. Gmail, Calendar, Drive, Sheets, Docs and Contacts send each Google request through Composio's Proxy Execute with your key. Omniscio never asks for, stores or logs a Google token from Composio.
- A direct Google sign-in always wins. If you are also signed in to Google directly, nothing changes for you.
- Background checks slow down. Each Google background check (new mail, calendar changes, labels, the Supermail mirror) runs at most once every 15 minutes, because each call may count against your Composio allowance. Calendar reminders can therefore arrive up to 15 minutes late.
- Google data stays away from DeepSeek, exactly as with a direct sign-in: connecting Google through Composio closes running DeepSeek sessions, and DeepSeek stays off while it is connected. An agent that asks to start a DeepSeek session while Google is connected (a
worker-tier helper included) is told no at once, with the reason and the fix, instead of being handed a session that never starts. - Some features need a direct Google sign-in and say so in plain words: the Google Workspace and Drive tools for agents (agents get Google tools from Composio instead), plugin Google sign-in, Google Meet, and extra Supermail accounts.
- Uploading files to Drive is not available through Composio yet; reading and downloading files is.
- A dead connection never blocks a live one. A request only ever goes out on a connection Composio reports as active: if a per-app connection has expired while your one Google Super connection is still live, every Google app keeps working through it, and the expired entry stays recorded so Google is never silently signed out. A request is never sent to a dead connection.
- A Google connection that dies says so plainly. When Composio reports that a Google connection has expired, been removed, or was never made for that app — and nothing live covers that app — the screens answer "Reconnect … in the Composio tab" and the failure is logged in the app's own log instead of being filed as a crash. A real Google or Composio failure (a switched-off API, a server error, a malformed request) still reports. A request Composio refuses outright — its own
400, which its API defines as invalid parameters/body or an endpoint the connection'sbase_urldoes not cover — says it was refused and points at the Composio tab to reconnect, rather than being reported as an unexplained error; a Google failure reaches the app INSIDE a200reply, so a400is always Composio's own verdict on the call.
Disconnecting: press Disconnect Google in the card, or Disconnect in Settings → Google Account. Both remove the Google connections at Composio and, when no other Google road remains, delete the local Google-derived data exactly like a normal Google disconnect. Removing the Composio key does the same. Turning the Composio Lab switch off hides the tab and the agent tools but does not disconnect Google, so the DeepSeek protection never lifts by accident. A connection that Composio marks expired, or a reply the app cannot read, never counts as a disconnect.
How the session tools work
- Omniscio mints a per-user Composio Tool Router MCP URL in the BACKGROUND and caches it — never during session startup, so the spawn hot path stays fetch-free.
- A dedicated layer in
mcp-config-orchestratorinjects{ type: 'http', url: <tool-router url>, headers: { 'X-API-Key': <your key> } }into the session's MCP config — but ONLY when the feature is on, a valid key is set, a URL is cached, and at least one app is connected. - The key-bearing entry is never injected into secret-sensitive (KMS / secret-excluded) sessions, and any error building it simply omits Composio, so it can never break a spawn.
Data & privacy
- Composio holds your connected accounts server-side (keyed by a stable per-user id). Omniscio stores only your encrypted API key + a small local cache (the user id, the minted URL, the connected-app list) — no cloud storage, no database migration.
- Tool calls run against your own Composio account and count toward your Composio quota (the free tier is generous).
Related
The mechanism this feature rides — a server being attached to each session so its tools show up — is described generally on the MCP servers page. If what you want is a connector to one specific outside app rather than a hundred at once, Zapier integration is the comparable approach, and the encrypted-at-rest treatment of the key you paste here is the same one described on API keys.
Last verified 2026-11-04