BrainwriteDocs
Connected apps

Composio for self-hosters

Configure project-key access, scoped permissions, and headless development.

Every Brainwrite installation uses its owner's Composio project: create a project, paste that project's ak_ key into Brainwrite, and usage stays attached to your own Composio account. This page covers the advanced details — scoped key permissions and headless/source runs.

Least-privilege scoped key

If you use a scoped Composio project key, grant:

  • Sessions: read and write
  • Toolkits: read
  • Connected accounts: read and write

Connected-account write access is required for upstream revocation during disconnect.

Source and headless runs

Set the key on the harness process:

COMPOSIO_API_KEY=ak_your_project_key pnpm dev:server

Brainwrite creates a stable random Composio user identifier and reuses the returned Session. It does not store raw Gmail, Slack, GitHub, or other provider tokens.

On this page