Composio

Composio connects services such as Gmail to DorkOS. Composio holds each service's login access in its vault. DorkOS keeps the stable connection, your agent choices, and the exact action versions you approved.

Pick a route

Both routes use Composio's vault for the connected service login. Bring-your-own setup changes who supplies the Composio project. It does not move Gmail or another service's login token into DorkOS.

DorkOS searches Composio's current service catalog instead of keeping a short list of services. A service can still appear when it needs custom setup. Its tile explains the missing requirement instead of hiding it.

DorkOS billing is off. Usage records identify the route and attempt, but DorkOS does not charge you or create an invoice.

Use your own Composio project

Your installation calls Composio directly for this route. It also receives signed notifications directly when you configure them. If your installation is offline, recovery depends on the service's own retry behavior. DorkOS hosting does not relay or buffer bring-your-own notifications in this release.

Use DorkOS-managed access

Open Connections → Accounts. If the app asks you to link your DorkOS account, choose Link DorkOS account. This opens Settings → Access. Select Link this instance and finish the DorkOS sign-in flow.

Return to Connections → Accounts and select Connect service. Search for Gmail, Google Drive, Linear, or another service. Choose its account button, such as Use a Gmail account. You do not need your own Composio key for this route. The service tile opens a sign-in flow bound to your account. DorkOS uses its server project key and a private account identity derived from your signed-in owner and linked installation. The browser cannot choose another owner, installation, Composio user, or callback.

DorkOS chooses the sign-in method in this order:

1. An explicit setup for that service takes priority. If it is broken, DorkOS stops and shows the problem instead of silently choosing another method.
2. A service with supported managed OAuth opens the service's consent flow. The consent page may name Composio because Composio handles the service connection. DorkOS owns the surrounding product flow and your access choices.
3. A service with supported account fields opens a secure form on dorkos.ai. The form identifies the service and account context, uses the field labels supplied by the service, masks secret values, and keeps DorkOS sign-in separate. Our servers pass these details to Composio without saving them. They never pass through your local installation or an agent.
4. A service that needs no account fields asks the owner to confirm before continuing.
5. A service that needs an unsupported method or custom developer setup stays visible with that requirement.

The actions available after OAuth depend on the scopes approved during consent. You then grant a named agent only the exact action versions it may use. For example, Gmail can offer read or write actions when the approved scopes allow them, but neither set is automatic. Gmail send and draft actions are available to review when consent allows them. Actions whose effects are uncertain require the stricter approval level.

Composio-managed apps use shared quotas and default scopes, and their polling triggers have a 15-minute minimum interval. That interval does not describe webhook delivery or Slack and Telegram Messaging.

Action inputs pass through DorkOS hosting and Composio to the service. Results return through the same path. Agents receive neither the project key nor the service login token. DorkOS keeps payload-free usage receipts with the action name, reviewed revision, attempt, outcome, and payer route. Those receipts do not contain action inputs or results.

Managed availability has two separate switches:

• common readiness covers catalog, sign-in, and actions;
• event readiness covers new notification intake.

Accounts are enabled after the real-account check passed. Managed notifications stay off until their separate live delivery check passes. A configured key alone does not enable either capability.

Add notifications

Open a connected account and choose Notifications. Select an activity type, any supported filter, the receiving agent, and the destination. Action access does not grant notification access.

For a managed notification, DorkOS hosting keeps an encrypted delivery copy until your linked installation stores it or the original seven-day window ends. Your installation then keeps its protected copy until the destination outcome is known or that same deadline ends. Cleanup runs in bounded sweeps, so physical deletion can happen after the logical deadline.

Removing a notification closes its local permission immediately. DorkOS then removes the upstream subscription when it still owns that subscription and the service is available. To change a filter, agent, or destination, remove the notification and create a reviewed replacement.

Inspect approved access from the CLI

Every program command names the agent whose access it may inspect or use:

dorkos connections list --agent <agent-id> --json
dorkos connections schema <connection-id> --agent <agent-id> --json
dorkos connections usage --agent <agent-id> --limit 20 --json
dorkos connections subscriptions --agent <agent-id> --json

These commands return stable DorkOS connection IDs. They do not expose Composio account references, credentials, sign-in URLs, or notification content.

Disconnect

Disconnecting closes local action and notification authority before DorkOS asks Composio to remove the account. If that external cleanup fails, the connection stays closed and the app shows that cleanup is pending. Do not repeat an action whose outcome is unknown. Check its existing receipt first.