docs(browser): leave timeout recovery to agent

Author: MagMueller

packages/bcode-browser/skills/browser-execute/SKILL.md

@@ -110,7 +110,7 @@ If a target-scoped command throws `CdpError` code `-32001` (`Session with given
 
 Every explicit reconnect or browser switch retires the previous socket and clears its active target attachment. Re-list targets, call `session.use(...)`, and rediscover DOM nodes and Runtime objects before continuing.
 
-New tabs and windows are separate targets with `type: "page"`; opening one does not move the current attachment, so `Page`/`Runtime` commands still go to the old tab and waiting for a page event does not switch to the new one. If the task continues in the new tab, re-list targets, identify the intended page by URL, title, or `targetId` rather than list position or an iframe/OOPIF target, then call `session.use(targetId)`.
+Opening a tab creates a new `page` target but does not switch the active attachment. Call `Target.getTargets` again and `session.use(targetId)` when continuing there.
 
 ## Driving a page
 Domain methods follow `session.<Domain>.<method>(params)` and return Promises. 
@@ -202,7 +202,7 @@ console.log(JSON.stringify(titles))
 ## Guardrails
 - Top-level `import` statements inside the snippet body are not allowed. Use `await import(...)` instead.
 - No CPU-bound infinite loops without `await` — they ignore the timeout. Insert `await new Promise(r => setTimeout(r, 0))` to yield.
-- `browser_execute` defaults to 60s (max 600s); inner CDP timeouts do not extend it. Keep calls small and do not increase the timeout after a page command stalls. A timeout preserves the connection and target, and the last command may still run: probe with browser-level `Target.getTargets`; if that works but page commands hang, attach a fresh page target. Reconnect only if the socket closed.
+- `browser_execute` defaults to 60s; longer timeouts delay your next turn. A timeout returns control without closing CDP, though the last command may still run. Use browser-level `Target.getTargets` to inspect the connection, then continue, switch targets, or reconnect as appropriate.
 
 ## Console
 - `console.log`, `console.error`, `console.warn`, `console.info`, `console.debug` are all captured and streamed to the user. Treat them as your stdout. Other `console.*` methods write to bcode's stderr without being captured into the tool result.

packages/bcode-browser/src/browser-execute.ts

@@ -262,7 +262,7 @@ export const make = Effect.fn("BrowserExecute.make")(function* (dataDir: string)
             const output = timeoutOutput(captured.output)
             const error = new Error(
               [
-                `browser_execute timed out after ${timeout} ms; the browser session remains connected`,
+                `browser_execute timed out after ${timeout} ms; the timeout did not close the CDP session`,
                 output.trim() ? `Partial console output before timeout:\n${output.trimEnd()}` : "",
               ]
                 .filter(Boolean)