Connected apps

Brainwrite connects to Gmail, GitHub, Slack, Notion, and 1,000+ other apps through Composio, using your own Composio project. You create a free Composio project once, paste its API key into Brainwrite, and every connection you authorize belongs to you — Brainwrite never routes your app traffic through a shared service.

The clean Brainwrite connected-app marketplace

Set up your Composio project

1. Open the Composio Dashboard and sign up or sign in.
2. Select Platform, select or create a project, then open Settings → API Keys.
3. Copy a project key beginning with ak_.
4. In Brainwrite, open App Settings → Connections and save it under Composio project key.

The key is validated before saving and stored with Electron's operating-system-backed secure storage. See Composio for self-hosters for scoped-key permissions and headless setups.

Connect an app

1. Open Connected apps.
2. Search for Gmail, GitHub, Slack, Notion, or another toolkit.
3. Select Connect.
4. Finish OAuth in the browser window that opens.
5. Return to the app and ask a bot to use the service.

Provider OAuth tokens remain with Composio and are not written into bot prompts or the renderer.

Connect X (Twitter)

Composio does not provide managed credentials for its twitter toolkit, so connecting X takes one extra step the first time:

1. Create an app in the X Developer Portal and note its client ID and client secret.
2. In Brainwrite, open Connected apps and select Connect on X (Twitter).
3. When prompted, paste the client ID and client secret from step 1. Brainwrite creates the auth config in your Composio project and finishes authorization from there.

Older references to the connector as x continue to work — Brainwrite translates that alias to Composio's twitter toolkit automatically.

Multiple accounts

Connect more than one account for the same toolkit and give each a clear alias such as work, personal, or client-acme. When several accounts could perform an action, Brainwrite requires explicit selection instead of silently replacing the first connection.

Disconnecting

Disconnecting an account revokes the upstream grant. It does not only hide the account in the local UI. Other accounts for the same toolkit remain connected.