assert
Deterministic assertion with auto-retry: visible | not_visible | text_equals | contains | enabled. Returns pass, or fail with reason and snapshot.
kindrequiredtextsessiontest_idtimeoutselectorrequired
io.github.autobot-labPublished by GitHub account autobot-labv0.5.1Updated Nov 22, 2026
AI-driven QA for web, Android and iOS: drive Chrome, emulators and simulators.
Drives Chrome, Android emulators and iOS simulators for QA: start sessions, run YAML test flows, assert, and write reports.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Follow the launch instructions in the repository.
Test your web, Android, and iOS apps in plain language, from one dashboard. You say what to check; AI runs it on your own computer, shows you every step live, and tells you what passed and what failed. Free, open source, no cloud. Payment and delete-account buttons are blocked from the start.
[The fastpilot dashboard: an agent called QA Checkout gets one sentence in Chat and answers with a Save test and schedule card that lists the test steps, a schedule every 2 hours, and the buttons Save and schedule, Save test only and Edit.]You need a Mac (or Linux), Google Chrome, and Claude Code signed in.
1. Install (once)
2. Set up your project (once per project)
init asks before each change; answer y. At the end it asks "Open the dashboard now?":
press Enter.
Using Claude Code? You can also install fastpilot as a plugin (the MCP server and its 24 skills in one step):
/plugin marketplace add autobot-lab/fastpilot, then/plugin install fastpilot@fastpilot. Use either the plugin orfastpilot initin a project, not both: both together start two fastpilot servers. With the plugin, a secret such asDEMO_PASSworks like this: add its name infastpilot ui› Settings › Secret, and set its value in the environment you start Claude Code from (export DEMO_PASS=…). The value is never typed into the dashboard or the chat.
Just want to look around first? Run
fastpilot demoinstead. It makes a demo folder with demo pages and example tests, and opens the dashboard on it.
3. Open the dashboard (every time)
Your browser opens the dashboard. Keep the Terminal open while you use it; Ctrl-C closes it.
Ctrl-C and run fastpilot ui again.Everything else happens in the dashboard.
Shows whether Chrome, Android, and iOS are ready, with a ✓ or the reason why not.
TEST_PASS. Tests write them as
${TEST_PASS}, and they always show as ***. Never type a password in Chat.An agent is a tester with its own job, devices, instructions, and skills.
You can have several agents, for example "Checkout" on web and "Login" on Android. Each has its own Chat, Live, Schedules, Instructions, Skills, History and Agent settings.
Write what you want in plain words:
When a test is ready, a card shows its steps: Save & schedule or Save test only. Nothing is saved before you click. The picture at the top of this page shows such a card.
Watch every test step by step, on web, Android, and iOS. Take over if you need to tap something yourself, then hand it back to the AI. Several agents can run at the same time; a phone runs one test at a time and the others wait their turn.
[The Live page: the QA Checkout agent is testing the event tickets page in Chrome; four steps are done and the fifth, waiting for the reservation message, is running, with Enlarge and Take over buttons.]~/.fastpilot/audit.jsonl.Want to test a checkout for real? Ask in Chat: "Allow the Pay button for this project", or open Settings › Limits & permissions.
These limits protect you from what a tested page tells the AI. They are not a lock against programs
on your own computer: anything that runs as you can edit ~/.fastpilot/config.toml.
Everything also works from Claude Code. Open Claude in your project folder (claude) and say it in
plain words, for example "fastpilot, run a regression" or "fastpilot, test the login page".
Results, schedules, and history show up in the dashboard too.
In GitHub Actions, use autobot-lab/fastpilot-action@v1:
it runs your tests on every pull request and adds the JUnit and HTML reports.
Open Device in the dashboard, or run:
License: Apache-2.0
Source: README.md at commit 71421b9
Deterministic assertion with auto-retry: visible | not_visible | text_equals | contains | enabled. Returns pass, or fail with reason and snapshot.
kindrequiredtextsessiontest_idtimeoutselectorrequiredValidate a flow without running it: syntax, unsupported steps, unknown sessions, parallel rules, missing ${VAR}s. Errors carry line numbers.
flowrequiredfastpilot settings (~/.fastpilot/config.toml; environment variables win): list, get, set, unset. Changes apply to the next action, no restart. Guard rails (allowed_domains, confirm_actions, block_actions, vars, state_expire_days, allow_* permissions, upload_dirs, max_steps, test_timeout) can only be made stricter here (a running fastpilot also ignores a looser value written to the file until it restarts); program paths and locations (chrome, claude, dir, ios_runner) only by the user with `fastpilot config set` or the file.
keyvalueactionfastpilot reference docs. Topics: dsl, selectors, parallel, examples, errors, memory, devices, skills (the testing skills: regression, bug-report, test techniques, ...), skill/<name> (one skill to follow).
topicClose a test run: writes .fastpilot/runs/<ts>-<test_id>/report.md and a self-contained report.html (steps, timings, diffs, screenshots, recordings) plus steps.jsonl and assertions.json, and, when status is pass, saves the flow as path memory for the next run.
notesstatusrequiredtest_idrequiredquarantineRun a YAML flow (batch of steps, may span sessions and `parallel:` blocks). Auto-waits, stops at the first failure, and returns per-step timing plus a diff (or full snapshot) per touched session. Pass test_id to record evidence for `report`.
flowrequiredsessiontest_idstop_on_failJPEG screenshot of a session, for visual fallback and evidence.
sessionannotateSession lifecycle: start (returns the first snapshot, and the path-memory hint when test_id is given), stop, list, devices, start_device. Web sessions launch their own Chrome or attach to yours (mode: attach).
idmodeactionrequireddevicetargettest_idendpointplatformCompact text snapshot of a session (one node per line, stable refs eN). Rarely needed: run_flow already returns state.
filefullcoordsfilterformatsessioninteractiveSaved login state (web: cookies + localStorage), so a test can skip the login: save | load | list | delete. Files are owner-only, expire after FASTPILOT_STATE_EXPIRE_DAYS (30) and are encrypted when FASTPILOT_STATE_KEY is set. Same as the saveState / loadState steps.
nameactionrequiredsession90% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
npm install -g fastpilotcd ~/your-projectfastpilot initfastpilot uifastpilot doctor