Connected apps

Open Connected apps from the sidebar, choose a service, and complete its authorization in your normal browser. Brainwrite turns the resulting connection into tools that supported agent engines can use.

Official packaged app

The signed desktop app registers its own installation with Brainwrite's managed connected-apps service. You do not need to find or paste a Composio key.

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.

The installation identity is stored using Electron's operating-system-backed secure storage. Provider OAuth tokens remain with Composio and are not written into bot prompts or the renderer.

Brainwrite Cloud

Connected apps come with a Brainwrite Cloud plan. My Cloud registers its own installation with the same managed service when it starts, so there is no key to add: open Connected apps on My Cloud and connect an app as above. The installation stays with My Cloud across restarts and is never copied into a backup.

When an app is signed out

An app counts as connected only while one of its accounts works. When every account of an app has stopped working, for example after you changed your password or revoked access at the service, the app says Signed out. Reconnect to keep using it. and its button reads Reconnect. Reconnect removes the account that stopped working and opens a fresh sign-in under the same label. An account that stopped working beside one that still works has its own Reconnect.

When a bot's call fails because an app is signed out, the bot is told so and asked to show you a card that reconnects the app, rather than retry the call. If a connection card in a chat needs a label, because the app already has a working account or the label is taken, the card asks for one.

Sending on your behalf

At Full access, a bot sends emails, messages, posts, invites and payments through connected apps without asking. Below Full access, each send asks first or counts against the bot's daily allowance. See Sending on your behalf.

X (Twitter)

To let bots search and read X, you don't need an X account or a connected app. Add your own treg key under Settings → API keys, or use a paid Brainwrite Cloud plan (My Cloud has it already). Every bot then gets Research (treg): read-only tools to search posts, read an account's posts, read a post with its replies and look up a profile, plus research tools for companies, people, funding, news and more. Turn it off for a bot in its settings. With your own key, calls are billed to your treg balance; with a Cloud plan, they count against the plan's monthly allowance.

X (Twitter) is not available through Brainwrite's connected apps yet: X does not offer the shared sign-in that the other services use.

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.

Limit which tools a bot may use

Connecting a service makes its tools available to the workspace; it does not hand every bot every tool. Open a bot's settings on the desktop and, under Connected apps, choose per service whether that bot gets all tools, an exact list of tools, or no tools.

By default every bot keeps all tools on the apps it can see — nothing changes when you upgrade or connect a new app until you assign a grant. Once a bot has any grant, services missing from its list grant it nothing. Imported bots and shareable packages always land with no grants.

Phones show each bot's grants read-only in its profile under App tools. Editing happens on the computer; a paired phone can never change grants.

Disconnecting

Disconnecting an account revokes that account's access at the service. It does not only hide the account in the local UI. Other accounts for the same toolkit remain connected.