Open source · Apache-2.0 · API tokens are free

AutoMax — an automation platform with a reusable architecture

BDD for UI, API and hybrid flows. Multi-project, multi-environment, data-driven and self-healing, with before/after screenshot narratives, a database-backed history, an MCP server, AI agents, GitHub and Jira integration and a web UI. Runs on Playwright.

Read the docs View on GitHub

Why AutoMax

Playwright is an excellent engine. Teams still rebuild the same things around it: environment switching, tagging policy, test data, login reuse, reporting, flaky triage, CI wiring, and now AI helpers. AutoMax ships those once, with opinions.

UI, API and mixed scenarios in one language

Gherkin on top of playwright-bdd with one merged fixture set, so a scenario can seed through the API and assert in the browser.

Many apps, many environments

One YAML per project plus one per environment; strict, explainable configuration precedence; secrets only through ${VAR}.

Reusable data

CSV, JSON, YAML, database tables and faker factories per environment, plus user pools leased per worker with login-state reuse.

Confidence across browsers

Chromium, Firefox, WebKit and mobile emulation; --project-matrix runs every browser you declared, @skip:<browser> is validated by lint.

Readable results

Before/after screenshots per step by suite tag, API request/response snapshots, and a run viewer with slider, overlay and pixel diff.

Institutional memory

Cucumber NDJSON ingested into SQLite or Postgres: flakiness, locator fragility, environment stability and suite health over time.

How it works

Everything is CLI-first. The web UI, the MCP server and the scheduler spawn the same commands and stream their output, so CI needs nothing but Node and the repository.

automax CLI
Config + registry
Playwright runs
NDJSON + screenshots
SQLite / Postgres
Web UI · MCP · agents

See every step

Regression scenarios capture a screenshot before and after every UI step. The run viewer pairs them with a slider, an overlay and a pixel diff. These are real captures from the demo project.

SauceDemo login form filled in, before the login button is clicked — Before: login form, credentials filled

SauceDemo inventory page after the login step — After: inventory page, logged in

AutoMax run viewer showing the step timeline with a before/after comparison — Run viewer: step timeline with before/after comparison and API panels

What ships in the box

BDD for UI, API and hybrid

Reusable step library, page objects with decorators, module and process taxonomy.

Data and user pools

Per-environment datasets, factories, leased accounts, cached storage state.

Self-healing locators

Scored candidate probes, persisted heal history, proposals to fix page objects.

Before/after narratives

Screenshot policy by suite tag; visual baselines; API snapshots.

SQLite or Postgres

One schema, runtime toggle, verified switch in both directions.

MCP server and agents

37 tools for Claude Code, Codex, Cursor and VS Code; planner, generator, healer, upgrader.

GitHub and Jira

Check runs, PR comments, deduplicated issues, @jira:KEY links, transitions.

Schedules

Cron recipes with overlap policy; runs from the server, crontab, launchd, systemd or Actions.

Web UI with roles

Organizations, workspaces, projects, modules; run viewer, Gherkin editor, tokens.

Quickstart

git clone https://github.com/siri1410/AutoMax.git && cd AutoMax && bun install
npx playwright install --with-deps
bun run automax run -p demo-shop -e staging -l ui -b chromium -t @smoke

Prerequisites: Node 22 and Bun (or pnpm). Full walkthrough in the installation guide.

Works with Claude Code and Codex

AutoMax is an MCP server: automax mcp install claude or automax mcp install codex, then ask your assistant to run, analyze or heal tests. Agents can reuse your logged-in CLI session, so no API key is required.

MCP guide

Want a feature? Tell us.

Feature requests and feedback go straight to the maintainers as GitHub issues and discussions. No account with us, no tracking.

Send feedback