faq
Frequently asked questions
Everything you might want to know before you install BrowserBash — what it costs, which AI models and browsers it runs, where your data goes, and how it fits into CI. Still stuck? We’re one email away.
Is BrowserBash really free?
Yes. BrowserBash is free and open-source under the Apache-2.0 license. Install it with npm install -g browserbash-cliand run unlimited automations locally at no cost. There’s an optional cloud dashboard (free with an account) and an optional paid data-retention add-on if you want cloud runs kept beyond the free 15-day window — but the CLI itself is free forever.
Do I need an API key or a credit card?
No. BrowserBash runs on free local models through Ollama or on free OpenRouter modelswith zero API keys and no credit card. If you prefer, you can optionally bring your own Anthropic or OpenRouter key for a different model — but it’s never required to get started.
Which AI models can I use?
You choose the model. BrowserBash works with free local models via Ollama (nothing leaves your machine), free models on OpenRouter, or — if you want — paid models from Anthropic or OpenRouter using your own key. The natural-language agent turns your plain-English objective into real browser actions no matter which model you pick.
Does my data leave my machine?
By default, no. The CLI is local-first: your objectives, the pages it visits, screenshots, recordings, variables, and credentials stay on your computer. The only outbound calls are the prompts sent directly to the AI model you choose, and those go straight to that provider — we’re never in the path. Data only reaches our servers if you create a free account and explicitly link the CLI (browserbash connect) or upload a run (--upload). We do not sell data and do not train models on your runs.
Is it open source? What license?
Yes. BrowserBash is open source under the Apache-2.0license, so anyone can read the code, audit exactly what the CLI does, and contribute. It’s built by The Testing Academy.
Which browsers and cloud providers does it support?
BrowserBash drives a real local Chrome out of the box, and can connect to any CDP (Chrome DevTools Protocol) endpoint. For cloud and cross-browser grids it also supports Browserbase, LambdaTest, and BrowserStack.
Do I need to know how to code?
No. BrowserBash is natural-language automation — you describe your objective in plain English and the AI agent performs the browser actions. There’s no code to write and no CSS or XPath selectors to maintain. When you want to save and version flows, you can write simple Markdown _test.md files, but writing real code is never required.
How is this different from Playwright or Selenium?
Playwright and Selenium make you write code and brittle selectors that break when the UI changes. BrowserBash takes a plain-English objective and lets an AI agent figure out the actions on a real browser — no selectors, no code. You still get developer-grade controls: Markdown test files with @import composition, variable templating with secret masking, an NDJSON agent mode, CI exit codes, and session recording.
Can I run it in CI/CD?
Yes. BrowserBash is built for automation pipelines. It emits structured NDJSON in agent mode and returns standard CI exit codes (0/1/2/3) so your pipeline can pass or fail on the result. Markdown _test.md files with @import composition let you organize and reuse flows across a suite.
Is there a dashboard?
Yes — two options. The free local web dashboard runs entirely on your machine via the dashboard command. There’s also an optional cloud dashboard, free with an account (sign-in via Clerk), that adds run history, video recordings, and per-run replay. Link the CLI with browserbash connect and push a run up with --upload.
How do session recordings work?
Add the --record flag to capture video and screenshots of a run. Recordings are saved locally by default. If you choose to upload a run to the cloud dashboard, the recordings are stored in Vercel Blob so you can watch the per-run replay from anywhere.
How long are my cloud runs kept?
Free cloud runs are retained for 15 days and then automatically deleted. If you need them kept longer, an optional paid data-retention add-on (billed via Stripe) extends retention. Runs you never upload stay only on your own machine for as long as you keep them.
Is it production-ready and stable?
BrowserBash is at version v1.3.1and is actively maintained by The Testing Academy. It ships the pieces you need for real automation work: CI exit codes, NDJSON agent output, secret masking, and session recording. Because it’s open source under Apache-2.0, you can inspect the code, pin versions, and follow development directly.
How do I get help or report a bug?
Email thetestingacademy@gmail.com or visit our contact page. Because BrowserBash is open source, you can also browse the code and follow the project. New here? Start with the Learn pages for guides on installing, writing test files, and running in CI.
Try it in two minutes
Free, open-source, no API key, no credit card. Install and describe your first objective.
npm install -g browserbash-cli