Busymate DevTools Docs
DocsAPI & Integrations
GitHub
Getting Started
IntroductionQuickstartNewCore conceptsNew
iOS App
OverviewInstall & pairTrust the certificateVPN vs PAC modesSet up Wi-Fi PACNewWhat gets decryptedInspect & breakpointsExternal proxyDeep linksNew
Dashboard
OverviewSign inThe feedInspect requests & HARBreakpoints & resendBlock rulesScriptsNewService groups & tagsWorkspaces & tabsTo-dosNewDevicesRemote settings & envRoles & permissionsApp Store statusNewDeveloper consoles
Proxy Server
OverviewInstall & runConnect a clientTrust the CAWhat gets decryptedBreakpoints & resendExternal proxy
CDP Connector (bmc)
OverviewInstall & sign inCapture a ChromeNamed devices & the daemonNewExternal proxy & custom ChromeBrowser profilesNewRemote controlNewCommand referenceUpdate & remove
BusyBro (AI assistant)
Overview
Using BusyBro
In the dashboardChat sessionsNewActivity traceNewOn TelegramNewOn iOS — actionsNewSpecialist agentsNewWhat it can doCustom connectorsNew
Memory
Long-term memoryNewConnect to team memoryNew
Configure
LLM providersNewEnvironment instructionsNew
API & Integrations
OverviewStats & status APITelegram linkingBusyBro ask API
MCP
OverviewConnect & authenticateTool referencePrompts & examples
REST
REST API
Realtime (WS)
Realtime channels
Federation (SSO)
Open in Busymate DevTools (one-tap)NewFederate a Supabase userbaseNew
Status Board
OverviewReading the cards
DocsapiFederation (SSO)

Federation (SSO)

  • Open in Busymate DevTools (one-tap)NewThe partner integration guide for the one-tap 'Open in Busymate DevTools' hand-off — drop your users into Busymate DevTools, signed in as themselves, in ONE tap. The confirmed same-device PKCE contract (mint verifier + S256 challenge, broker /start, open bmdev://auth/federation?code=…#fed_verifier=…, /exchange for a real-email session), how to onboard a partner with one upsert_federation_client admin action, and the BMFederationExample reference implementation.
  • Federate a Supabase userbaseNewThe partner guide for the 'supabase' federation profile — a partner whose product runs on its OWN Supabase project auto-logs (and auto-creates) its users into Busymate DevTools. The asymmetric-signing-keys (ES256/RS256 JWKS) prerequisite + the onboarding preflight, the one-admin-action registration (supabase_url / email_trusted / email_linking_trusted / capped_role / max_token_age), and the exact /start wire contract with the user's live Supabase access token as the supabase_token assertion.

Built by serebano. Source on GitHub.

v1.0 · build 218