Address review feedback on Live View and HITL docs

- Remove Full viewing mode row (not yet tested)
- Change Inspector URL to mode=devtools
- Remove "Get the Live View URL programmatically" section (not yet shipped)
- Condense Native Chrome DevTools pros/cons into single paragraph
- Replace Cloudflare.getLiveView with includeTargets=true in HITL example
- Add timeout and Slack/chat notes to HITL code comments
- Add bot detection note to HITL page

Author: kathayl

src/content/docs/browser-rendering/features/human-in-the-loop.mdx

@@ -14,7 +14,7 @@ Some browser automation workflows require manual intervention. A login page may
 Human in the Loop works with any [Browser Session](/browser-rendering/#integration-methods) and uses [Live View](/browser-rendering/features/live-view/) to give humans access:
 
 1. Your automation script navigates to a page that needs human input.
-2. The script retrieves the Live View URL via `Cloudflare.getLiveView` and shares it with a human operator (for example, by logging it, sending it via Slack, or displaying it in a UI).
+2. The script retrieves the [Live View](/browser-rendering/features/live-view/) URL from the session's target list and shares it with a human operator (for example, by sending it via Slack, email, or displaying it in a UI).
 3. The human operator opens the Live View URL and completes the required action (logging in, solving a CAPTCHA, entering sensitive data, etc.).
 4. The automation script detects that the human is done (for example, by waiting for a navigation event or polling for a page element) and resumes.
 
@@ -32,13 +32,14 @@ const API_TOKEN = "your-api-token";
 
 // Create a browser session via CDP
 const response = await fetch(
-  `https://api.cloudflare.com/client/v4/accounts/${ACCOUNT_ID}/browser-rendering/devtools/browser?keep_alive=600000`,
+  `https://api.cloudflare.com/client/v4/accounts/${ACCOUNT_ID}/browser-rendering/devtools/browser?keep_alive=600000&includeTargets=true`,
   {
     method: "POST",
     headers: { Authorization: `Bearer ${API_TOKEN}` },
   }
 );
-const { webSocketDebuggerUrl } = await response.json();
+const { webSocketDebuggerUrl, targets } = await response.json();
+const liveUrl = targets[0].devtoolsFrontendUrl;
 
 // Connect Puppeteer to the session
 const browser = await puppeteer.connect({
@@ -49,16 +50,10 @@ const browser = await puppeteer.connect({
 const page = await browser.newPage();
 await page.goto("https://example.com/login");
 
-// Get the Live View URL so a human can interact with the session
-const cdp = await page.createCDPSession();
-const { devtoolsFrontendUrl: liveUrl } = await cdp.send(
-  "Cloudflare.getLiveView"
-);
-
-// Share the Live View URL with the human operator
+// Share the Live View URL with the human operator (for example, send it via Slack, email, or display it in a UI)
 console.log(`Human input needed. Open this URL: ${liveUrl}`);
 
-// Wait for the human to complete login
+// Wait for the human to complete login (5 minute timeout — the script will continue after this period)
 await page.waitForNavigation({ waitUntil: "networkidle0", timeout: 300000 });
 
 // Login complete, continue automation
@@ -77,3 +72,7 @@ browser.disconnect();
 - **Sensitive data entry**: Forms requiring credentials or personal information you do not want to pass to an automation script
 - **Complex interactions**: One-off tasks that are too difficult or not worth fully automating, such as configuring a dashboard or approving a workflow
 - **Verification steps**: Confirming an order, reviewing generated content, or approving an action before the script proceeds
+
+:::note[Bot detection]
+Browser Rendering requests are [always identified as bot traffic](/browser-rendering/faq/#will-browser-rendering-be-detected-by-bot-management). Even with a human controlling the session, some third-party services may still block the request.
+:::

src/content/docs/browser-rendering/features/live-view.mdx

@@ -7,7 +7,7 @@ sidebar:
   badge: Beta
 ---
 
-import { CURL, DashButton, Tabs, TabItem } from "~/components";
+import { CURL, DashButton } from "~/components";
 
 Live View lets you see and interact with a remote Browser Run session in real time. This is useful for debugging automation scripts, monitoring what a browser is doing, or manually stepping in when a task requires human intervention (see [Human in the Loop](/browser-rendering/features/human-in-the-loop/)).
 
@@ -27,13 +27,12 @@ In the Cloudflare dashboard, go to the **Browser Run** page and select the **Liv
 
 When you create a session or list targets through the [CDP](/browser-rendering/cdp/) endpoints, the API response includes a `devtoolsFrontendUrl` for each target (tab). Open this URL in any browser to load the DevTools UI hosted at `live.browser.run`, which streams the remote session to your browser.
 
-The hosted UI supports three viewing modes, controlled by the `mode` parameter in the URL:
+The hosted UI supports two viewing modes, controlled by the `mode` parameter in the URL:
 
 | Mode | URL pattern | Description |
 | --- | --- | --- |
 | Tab | `https://live.browser.run/ui/view?mode=tab&wss=...` | DevTools inspector panel (Elements, Console, Network, etc.) |
-| Full | `https://live.browser.run/ui/view?mode=full&wss=...` | Full browser chrome with address bar and tab strip |
-| Inspector | `https://live.browser.run/ui/inspector?wss=...` | Standalone inspector view |
+| Inspector | `https://live.browser.run/ui/view?mode=devtools&wss=...` | Standalone inspector view |
 
 ### Native Chrome DevTools (Chrome only)
 
@@ -43,15 +42,7 @@ Because Browser Run speaks standard CDP, you can connect Chrome's built-in DevTo
 devtools://devtools/bundled/inspector.html?wss=live.browser.run/api/devtools/browser/SESSION_ID/page/TARGET_ID?jwt=...
 ```
 
-Paste this URL into Chrome's address bar to open native DevTools connected to the remote browser session.
-
-**Pros:**
-- Familiar UI: the exact same DevTools you use daily for local development, rather than a hosted version wrapped inside a webpage
-- Slightly faster to load: DevTools assets (HTML, JS, CSS) are already bundled locally in Chrome
-
-**Cons:**
-- Chrome only: the `devtools://` protocol URL only works in Chrome. The hosted `live.browser.run` version works in other browsers, though the DevTools UI has not been heavily tested outside Chrome.
-- Inspector tab only: does not work for the full or tab viewing modes
+Paste this URL into Chrome's address bar to open native DevTools connected to the remote browser session. This gives you the familiar local DevTools UI and loads slightly faster since the assets are already bundled in Chrome. However, the `devtools://` protocol only works in Chrome and only supports the inspector viewing mode.
 
 :::caution[URL validity]
 The `devtoolsFrontendUrl` is valid for five minutes from when it was generated. If you do not open the URL within this timeframe, list the targets again to get a fresh URL. Once the DevTools connection is established, it remains active as long as the browser session is alive.
@@ -132,29 +123,3 @@ If you have a running session and want to connect to it:
 ```
 
 3. Copy the `devtoolsFrontendUrl` and open it in your browser.
-
-## Get the Live View URL programmatically
-
-You can retrieve the Live View URL from within a Puppeteer or Playwright script using a CDP command. This is useful when you need to share the URL with someone, for example sending it via email, Slack, or displaying it in a UI.
-
-<Tabs> <TabItem label="Puppeteer">
-
-```js
-const cdp = await page.createCDPSession();
-const { devtoolsFrontendUrl } = await cdp.send("Cloudflare.getLiveView");
-
-console.log(`Live View: ${devtoolsFrontendUrl}`);
-```
-
-</TabItem> <TabItem label="Playwright">
-
-```js
-const cdp = await page.context().newCDPSession(page);
-const { devtoolsFrontendUrl } = await cdp.send("Cloudflare.getLiveView");
-
-console.log(`Live View: ${devtoolsFrontendUrl}`);
-```
-
-</TabItem> </Tabs>
-
-You can also get the Live View URL from the HTTP API by listing targets for a session, as shown in [View an existing session](#view-an-existing-session). Each target in the response includes a `devtoolsFrontendUrl`.