@kody/browser-runFork

@kody/browser-run

Intent

Give agents and humans a thin, isolate-safe way to call Cloudflare Browser Run (formerly Browser Rendering): one-shot Quick Actions (screenshot, PDF, scrape, …) plus shared-session helpers that bake in session reuse and per-request createBrowserContext() isolation. Success means reliable browser automation without cold-starting a new browser for every request, and without recommending browser.close() on a shared session.

What this package does

• Quick Actions — REST POST to /accounts/{accountId}/browser-rendering/{action} for content, screenshot, pdf, markdown, scrape, links, json, snapshot, and accessibilityTree.
• Sessions — list, get, acquire, connect metadata, and guarded close.
• open-isolated (default for automation) — list → reuse (random start) → acquire; returns WS endpoint + instructions to isolate with createBrowserContext, then context.close() + browser.disconnect().
• worker-recipe — copy-paste Worker + wrangler guidance using @cloudflare/puppeteer ≥ 1.1.0 (not runnable inside Kody).

This package does not depend on Puppeteer or Playwright (those graphs blow up Worker isolates). Heavy CDP control runs in your Cloudflare Worker or Node process; Kody only orchestrates the REST/CDP metadata.

Setup

1. API token — Create a Cloudflare API token with Browser Rendering - Edit. Save it as the Kody user secret cloudflareApiToken with allowed host api.cloudflare.com:

   https://kody.codes/account/secrets/new?name=cloudflareApiToken&description=Cloudflare%20API%20token%20with%20Browser%20Rendering%20-%20Edit&allowedHosts=api.cloudflare.com&scope=user

2. Account id — Pass accountId on live calls. Find it in the dashboard URL (dash.cloudflare.com/<accountId>/…) or Workers & Pages → Overview → Account ID. Forkers bring their own account — this package does not hardcode any Cloudflare account.

3. Optional: pass apiTokenSecret with an alternate secret name only (never a raw token value).

When to use what

Docs: Cloudflare Browser Run · Reuse sessions

Pit of success

Multiple clients can share one Browser Run session (puppeteer.connect per Worker, separate browser contexts). After connect:

1. const context = await browser.createBrowserContext()
2. Do work in that context
3. await context.close()
4. await browser.disconnect()

Never call browser.close() while the session may be shared — that kills every concurrent client.

Done when

• smoke-test returns setup guidance without opaque errors when accountId/secret are missing
• With a configured token + accountId, sessions/list or smoke-test lists sessions (or a clear auth error)
• Agents pick open-isolated for shared automation and Quick Actions for one-shots