Built for development and testing

Build, test, and debug multi-user browser flows with real parallel Playwright sessions.

Octowright gives coding agents and engineers a shared control plane for Chromium, Firefox, and WebKit, with persistent personas, replayable recordings, and test-friendly artifacts.

Get Started Watch demos

Seven Mix Orchestration

Nine coordinated panes across three engines, one deterministic run, one checked-in bundle.

1920x1080 24.52s

Featured Demos

Recorded runs built for engineering workflows.

Orchestration, cross-engine comparison, and role-based verification. Each demo is a real bundle with replay artifacts you can inspect and rerun.

Seven Mix Orchestration poster

Webkit · Firefox · Chromium

Seven Mix Orchestration

Seven players claim tiles on a shared canvas while an operator watches the aggregate live. Nine browsers actually coordinating — not nine empty tabs.

Cross-Engine Trio poster

Chromium · Firefox · Webkit

Cross-Engine Trio

Three engines run the same Wikipedia search in parallel. Watch where they agree and where timing differs.

Verify Suite poster

3 panes · Webkit

Verify Suite

Three roles each run their own verify macros against the same scenario. Each asserts what its role should see.

View all demos

How Octowright Works

From first run to repeatable verification.

Use one runtime for local debugging and CI checks: coordinated browsers, recorded actions, replay exports, and verify artifacts.

  1. Launch coordinated browsers

    Start Chromium, Firefox, and WebKit in parallel with persona-aware profiles that keep login state across runs.

  2. Run scenarios and verification

    Drive role-based participants with reusable macros, then run verify flows as tests for repeatable multi-user checks.

  3. Keep CI-ready artifacts

    Each run keeps JSONL recordings, replay exports, and verification outputs you can review locally and publish in pipelines.

Get Started

Install once, then move from local smoke test to repeatable verification.

Register Octowright as an MCP server, run a short browser flow, save it as a macro, and execute scenario verification with JUnit output.

Open quickstart
git clone https://github.com/livingstaccato/octowright.git
cd octowright
uv sync
uv run playwright install chromium firefox webkit

.mcp.json (project) or ~/.claude.json (global)

{
  "mcpServers": {
    "octowright": {
      "command": "uv",
      "args": ["--directory", "/abs/path/to/octowright", "run", "octowright", "serve"]
    }
  }
}

~/.codex/config.toml

[mcp_servers.octowright]
command = "uv"
args = ["--directory", "/abs/path/to/octowright", "run", "octowright", "serve"]

Cursor, Continue, Zed, or any MCP-aware harness

{
  "mcpServers": {
    "octowright": {
      "command": "uv",
      "args": ["--directory", "/abs/path/to/octowright", "run", "octowright", "serve"]
    }
  }
}

Why It's Different

Why teams use Octowright for dev and test.

Multi-session realism

Launch coordinated participants as a scenario (players, monitor, spectator) instead of faking concurrency with one tab.

Replay and evidence

Every action is recorded so runs are explainable: re-run flows, export scripts, and inspect timeline evidence in the dashboard.

CI-friendly verification

Run verify macros as tests and emit JUnit output so Octowright fits directly into existing release gates.

CLI / Workflow

CLI path for repeatable verification.

Serve Octowright, run scenario verification, and execute macro test suites with JUnit output.

$ uv run octowright serve
$ uv run octowright scenario start verify-suite --test --out artifacts/verify-suite.xml
$ uv run octowright test --tag verify --out artifacts/macro-tests.xml

Browse bundle sources