Skip to main content
BrowserWire requires Node.js 22+ and runs on macOS or Linux. Chromium is installed automatically by Playwright during npm install.
Yes — recordings (DOM events and interactions) are uploaded to BrowserWire’s cloud for AI training. However, the execution server (bw run) runs entirely on your machine. API calls are served locally through a real browser instance.See the Privacy page for full details.
Views read structured data from a page — product lists, user profiles, order summaries. They’re exposed as GET endpoints.Actions perform interactions — clicking buttons, filling forms, submitting data. They’re exposed as POST endpoints and can accept input parameters.
Yes. BrowserWire works with any website you can open in a browser. The quality of the generated API depends on how thoroughly you interact with the site during recording — the more pages you visit and features you use, the more views and actions the AI discovers.
Record the same site again with bw record. Each recording triggers a new training run that replaces the previous manifest. You can focus on flows you missed in earlier recordings.
Training typically takes 1–2 minutes. You can monitor progress on the dashboard — look for the training status badge next to your recording.
Run bw login to authenticate, then try bw run again. Your session token may have expired (tokens are valid for 30 days).For CI environments, set the BW_TOKEN environment variable instead.
The execution server limits concurrent requests (default: 3). Each request opens a browser page, so too many parallel requests exhaust the pool.Increase the limit:
bw run --max-concurrent 5
Yes:
bw run --headless
This runs the Playwright browser without a visible window. Useful for servers or CI environments.
Use a different port:
bw run --port 3000
BrowserWire is currently in Early Access and everything is free. You’ll be notified before any pricing changes.