AutoMax
Getting started

The web UI

What the AutoMax web application offers and how it relates to the CLI.

What you'll learn

What each page of the web application does, which role can do what, and why the UI never does anything the CLI cannot.

Start it

bun run automax users create --admin
bun run automax serve                 # http://127.0.0.1:4444

The server is a Fastify application. It spawns the same automax commands you run by hand and streams their logs over Server-Sent Events, so a run started from a browser looks exactly like one started from a terminal.

Dashboard: pass-rate and duration trends, suite health per process, flaky scenarios, latest runs
Dashboard
Workspaces of the organization with each member's effective role
Organization → workspaces with roles. Owners and admins create workspaces and manage members.

Pages

PageWhat it does
Dashboardpass-rate, duration and flaky trends; most-failing locators; latest runs; proposals inbox
Projectsthe project YAML as a form: layers, browsers, tag policy, screenshot policy, integrations, MCP servers
Environmentsbase URLs and non-secret settings; secret names shown with a presence indicator
Datasetsupload CSV, JSON or YAML, preview the first rows, choose file or database storage
Runsfilterable list, live log, scenario tree, step timeline with before/after comparison and API panels
Feature editorGherkin editing with step completion from your project, lint diagnostics, run this scenario
Recorderlaunch Playwright codegen with a pool user, save the spec, convert it with an agent
Agentsstart a role, watch it work, review the diff, accept or reject
IntegrationsGitHub and Jira settings, connection tests, MCP servers the project consumes
Schedulescron builder with the next fire times, history, pause and resume
Users, Settingsroles, free scoped API tokens, MCP client install snippets
Run detail: scenario tree grouped by module with badges and live log
Run detail
Feature editor with Gherkin highlighting, step completions and diagnostics
Feature editor
Schedules page with cron builder and next fire times
Schedules

Roles

RoleCan
viewerread everything, download artifacts
editorstart and stop runs, edit features and datasets, run agents, accept proposals
adminmanage users, integrations, projects, tokens

Roles are per workspace: a user's effective role is the stronger of the explicit workspace membership and the one implied by the organization membership (member → viewer, admin and owner → admin). Platform admins are admin everywhere.

Next steps

On this page