Kick off the QR-scan + scripted-CDP Telegram bot creation flow.
Idempotent: if a non-terminal QR session already exists for this box,
returns it instead of spawning another browser. The FE keeps polling
GET /me/tg/auto/{id} until the session reaches a terminal state.
No external BU Cloud API key is needed — the orchestrator provisions the chromium VM via the cloud’s internal browser service, which auths via app_config.use_browser_api_key (already set in every env).
Documentation Index
Fetch the complete documentation index at: https://docs.browser-use.com/llms.txt
Use this file to discover all available pages before exploring further.
Successful Response
Returned by POST /me/tg/auto. The session is already running by the time this returns — frontend opens the iframe and starts polling.
Snapshot of a QR onboarding session. Returned by start, status, and cancel — same shape so the FE renders a single view component.