← ClaudeAtlas

browser-runlisted

Use a real headless browser (Cloudflare Browser Run) as a fallback when the built-in web fetch is blocked by bot protection, login walls, redirects, or JavaScript-only rendering. Pi-native tools browser_markdown / browser_content / browser_scrape.
nikolanovoselec/codeflare · ★ 24 · Web & Frontend · score 68
Install: claude install-skill nikolanovoselec/codeflare
# Browser Run (Pi) A real-browser fallback for fetching public web pages that the built-in web fetch can't read — bot-protected pages, JS-only / single-page apps, redirect chains, and pages that need a real engine to render. Backed by Cloudflare Browser Run (headless Chrome), exposed as **native Pi tools** (no MCP). Only available in Pro (advanced) sessions when a Cloudflare API token with the **Browser Rendering – Edit** scope is configured. If the tools below are not present, Browser Run is not enabled for this session. ## When to use 1. Try the built-in web fetch first. 2. If it returns an error, a CAPTCHA/anti-bot page, an empty body, or obviously unrendered HTML, **fall back to Browser Run**. 3. Public URLs only. Do not point Browser Run at internal hosts, `localhost`, private IPs, or anything requiring the user's session/credentials. ## Tools | Tool | Use it for | |---|---| | `browser_markdown` | The default. Returns the page as clean Markdown — best for reading article/doc content. | | `browser_content` | Returns the fully-rendered HTML (after JS). Use when you need raw DOM/structure that Markdown drops. | | `browser_scrape` | Returns text + HTML + attributes for specific CSS selectors. Use to pull structured bits (links, headings, prices, table cells) without ingesting the whole page. | All three take `url` and an optional `wait_until`. For JavaScript-heavy pages or SPAs that render content after load, pass `wait_until: "networkidle0"` so the content has render