Installation

Autowright has two halves: a package in your script and a service stack that turns failures into pull requests. You can install the package alone — capture and diagnostics work locally without the stack.

1. The browser package

The package is distributed from its public GitHub repo, nawaaz-korvol/autowright-browser. It installs under the name @autowright/browser, so imports look the same as they will when it reaches npm.

npm

npm install github:nawaaz-korvol/autowright-browser playwright

pnpm

pnpm add github:nawaaz-korvol/autowright-browser playwright

yarn

yarn add nawaaz-korvol/autowright-browser playwright

Note

The package ships TypeScript source. Run your scripts with tsx (as this documentation does), ts-node, or a bundler.

Install a browser binary if you haven’t already:

npx playwright install chromium

@autowright/browser re-exports all Playwright types, so it can be your only browser import.

2. The healing stack

The service, fixer, and artifact storage run as containers:

git clone https://github.com/nawaaz-korvol/autowright-v3
cd autowright-v3
cp .env.example .env   # fill in your keys
docker compose up service fixer minio minio-init

For fixes to become pull requests, the fixer needs three credentials in .env:

Variable	Purpose
ANTHROPIC_API_KEY	Powers the fixing agent (Claude Agent SDK)
GITHUB_TOKEN	Lets the fixer clone your repo and open PRs
SLACK_WEBHOOK_URL	Optional — fix notifications with cost breakdowns

See Environment Variables for the full list and Self-Hosting for the complete stack — including the dashboard and Tilt-based local development.

3. Verify

With the stack up, the service answers on port 4400:

curl http://localhost:4400/api/stats

Now wire up your first script in the Quick Start.