Skip to main content
The BrowserWire dashboard at app.browserwire.io is where you manage your recordings, monitor training progress, explore generated APIs, and manage your account.

​
Creating an account

Visit app.browserwire.io/sign-up to create an account. You can sign up with email or use an OAuth provider (Google, GitHub, etc.). The same account is used for both the dashboard and the CLI. If you’ve already run bw login, you have an account — sign in at app.browserwire.io/sign-in with the same credentials. After signing in, you’re redirected to the dashboard.

​
Dashboard layout

The dashboard has a sidebar on the left with four sections: Your email and a sign out option are in the sidebar footer.

​
Overview

The main dashboard page shows a high-level summary:
  • Manifests discovered — large counter showing total generated APIs
  • Recordings — total browser sessions captured
  • Active training — number of training runs currently in progress (with a live animated dot when > 0)
  • Recent Manifests — quick-access list of your 5 most recently updated APIs, with domain, slug, and date. Click any row to jump to its endpoint explorer.
  • Recent Recordings — quick-access list of your 5 most recent recordings, with domain, event count, and date. Click any row to jump to its detail page.
If you’re a new user, you’ll see empty states with a helpful prompt:
No manifests yet. Record a browser session to discover your first state machine. bw record <url>

​
Recordings

Navigate to Recordings in the sidebar to see all captured browser sessions in a paginated table (20 per page).

​
Recordings table

​
Training status badges

​
Recording detail page

Click any recording to open its detail page, which shows:
  • Domain, event count, and timestamp at the top
  • Training Runs section listing every training run for this recording:
    • Status badge and timestamp (or “Running…” / “Failed”)
    • If complete: a link to the generated manifest (e.g., → example-com) — click to jump to the Endpoint Explorer
    • If error: an error message: “Training was unable to complete. Please try recording again.”
  • Recording Replay — an interactive rrweb player that replays your recorded session in the browser. Use the playback controls to scrub through the recording and see exactly what was captured.

​
APIs

Navigate to APIs in the sidebar to see all your generated manifests.

​
Manifests table

​
Endpoint Explorer

Click a domain to open the Endpoint Explorer for that manifest. Every discovered endpoint is listed with:
  • Method badge — green GET for views, blue POST for actions
  • Endpoint name — the semantic name assigned by the AI (e.g., product_list, submit_login)
  • URL path — the full local API path (shown in grey, e.g., /api/sites/example-com/views/HomePage/product_list)
Click any endpoint row to expand it and see:
  • Full URL with a copy button — the complete http://127.0.0.1:8787/... URL
  • curl command with a copy button — a ready-to-paste command for testing
The header shows the total endpoint count and the base URL (http://127.0.0.1:8787).
Copy curl commands directly from the Endpoint Explorer and paste them into your terminal while bw run is active to test endpoints immediately.

​
Plan

Navigate to Plan in the sidebar to view your current subscription status. BrowserWire is currently in Early Access — all features are included for free. You’ll be notified before any pricing changes.

​
End-to-end workflow

Here’s how the dashboard fits into the full BrowserWire workflow:
1

Record

Run bw record https://example.com in your terminal. This creates a recording and opens the dashboard to the recording detail page.
2

Monitor training

Watch the training status badge on the recording detail page. It starts as running with an animated indicator.
3

Review the recording

While waiting, use the Recording Replay player to verify the session captured what you intended.
4

Navigate to your API

Once training shows complete, click the manifest link (e.g., → example-com) to jump to the Endpoint Explorer.
5

Copy curl commands

Expand any endpoint in the Endpoint Explorer and copy the curl command.
6

Execute locally

Run bw run in your terminal, then paste the curl command to test the endpoint.