An app's account can belong to the team

[mxmzb]

An app's account can belong to the team

An administrator can make a Composio app Shared: one account, connected once, that every Bot granted the app acts as. Until now every brokered app was personal — each person connected their own mailbox or tracker, and a Bot acting for the team had no account of its own to use.

What this adds

• A Personal or Shared choice per app. An administrator switches an app on its admin page. The switch previews what it would end before it does anything, and nothing changes unless every account on the old side is withdrawn at the vendor first — a half-finished switch would leave people's mailboxes attached to an app that no longer reaches them.
• Who may use it, approved per Bot. Owner only, named people and groups, or everyone, and separately whether email, Slack or webhook input may steer a run that uses the account. Checked on every call, against the app's answering row rather than whichever duplicate row was dialled.
• Requests when it is too narrow. Publishing a Bot, assigning it a responsibility or adding a trigger tells the owner what an administrator still has to approve, and files the request. Administrators answer them in the Approvals inbox.
• Writes ask first. Making an app Shared adds an ask-before-write rule over its tools, and removing the app or switching it back to Personal revokes that rule rather than leaving it standing over an account nobody holds.
• A new brokered_connections table that records an account's holder — a person or the deployment — rather than assuming a person.

Before upgrading

• Migration 0052_shared_brokered_accounts copies every Composio connection into brokered_connections and leaves composio_connections in place, unwritten. Rolling back to 0.1.2 works, but accounts connected after the upgrade are invisible to it.
• A handoff now records what started the run it came from. Older remote Bots' signed runs carry no such record for up to ten minutes after the upgrade, and calls they make to a Shared app in that window are refused.

main is merged in as of bb29c63. It carried the AG-UI 1.0 upgrade, so a checkout of this branch needs bun install before it typechecks.

Verification

Check	Result
bun run format	clean
bun run lint	clean
bun run typecheck	0 errors
Tests	6,357 pass, 0 fail

The suite was run in batches rather than as a single bun test. A whole-suite run exhausts PostgreSQL's 100-connection limit locally (sorry, too many clients already), because the suite now has 91 test files that each open a 2-connection pool, up from 62 on main. Every file passes; worth watching whether CI hits the same ceiling.

Still open

• The live Composio check (bun run test:live-composio) has not been run. The test is written and gated behind describe.skipIf(!live), so it is inert without a key.
• The admin flow has not been clicked through in a browser yet.

🤖 Generated with Claude Code