cdpfleet / Launch interactive
Try it live
Try it live, then automate it.
In the dashboard's code generator, pick a browser, proxy and options, enter a start page and click Launch interactive: the browser opens in your dashboard with full mouse and keyboard control. The code next to it launches exactly the same browser.
- 0lines of code to start
- start_urlover the API
- 10 minlongest idle on shared plans
From the dashboard
- Open the code generator on the dashboard overview and choose the browser, version, proxy and options.
- Under Try it live, enter a start page and press Launch interactive.
- The browser opens on that page in a live view in control mode — your mouse and keyboard reach it. Headless sessions get an address bar with back, forward and reload.
- When it behaves the way you want, copy the code next to it: same browser, same options.
Over the API: start_url
Add start_url to a launch and the server opens the page itself — no client has to connect. Ask the session's router for a control live link and drive it from any page with noVNC or the screencast protocol.
POST https://starter.cdpfleet.com/chrome/session
{ "proxy": "…", "headless": "new", "live_view": true, "start_url": "https://example.com" }
POST https://router01.cdpfleet.com/admin/session/live // the host of wsUrl
{ "session_id": "…", "mode": "control" }In control mode the screencast socket also takes navigate, back, forward and reload messages. Your code can still connect later: browser.contexts()[0].pages() holds the start page.
How long it stays open
- Mouse and keyboard input count as activity, and so does an open viewer: a session stays up while someone watches.
- With no input and no one watching, the session ends after
inactivity_timeout— 120 s by default, at most 10 minutes on shared plans and 5 on Community; dedicated threads can set up to 24 hours. - The dashboard ends the session when you close the viewer, unless you launched with
keep_alive. - It is a normal session for billing: threads and minutes while it runs, on every plan.
Which browsers
Any browser headful, or headless Chromium-based browsers with "live_view": true (otherwise 400 start_url_not_viewable). Not on Rebrowser. start_url must be http or https, at most 2,048 characters.