fastpilot

io.github.autobot-lab由 GitHub 账号 autobot-lab 发布v0.5.1更新于 Nov 22, 2026

AI-driven QA for web, Android and iOS: drive Chrome, emulators and simulators.

已验证STDIO仅桌面浏览器自动化开发者工具

概览

AI 生成的概览

面向 QA 的自动化工具,可驱动 Chrome、Android 模拟器和 iOS 模拟器:开启会话、运行 YAML 测试流程、断言并生成报告。

可以做什么
  • 启动、停止和列出浏览器或设备会话,也可附加到自己已打开的 Chrome
  • 运行跨会话和并行块的 YAML 测试流程,自动等待并返回每步耗时
  • 在不运行的情况下检查流程语法与规则,并断言可见性、文本或启用状态
  • 截取会话的 JPEG 截图和紧凑文本快照
  • 保存、加载和删除登录状态,让测试跳过登录
  • 结束一次运行并生成 Markdown 与 HTML 报告、步骤日志和断言结果,并查阅内置参考文档
适用场景
适合让助手端到端地测试 Web、Android 或 iOS 应用并汇报通过或失败的情况,例如回归测试、发布前检查,或把描述的场景变成可重复执行的测试。
运行要求
通过 npx 在本地运行(需要 Node.js)。需要 Mac 或 Linux 以及 Google Chrome;Android 模拟器和 iOS 模拟器需额外配置,iPhone 测试需要 Xcode。可选环境变量包括用于加密登录状态的 FASTPILOT_STATE_KEY 和 FASTPILOT_STATE_EXPIRE_DAYS;测试密码以名称引用并通过环境变量提供。
安装前请注意
它会操作真实的浏览器和设备,可以点击、输入和上传,对线上站点会产生实际影响。支付和删除账号类按钮默认被拦截,普通删除操作需要确认,但这些限制可由你自行放宽。保存的登录状态包含 cookie 和 localStorage,仅在设置 FASTPILOT_STATE_KEY 时加密。防护规则存放在本地配置文件中,任何以你的身份运行的程序都能修改。

安装

在 SourceWeft 中

  1. 打开 控制台中的 fastpilot,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

fastpilot

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.]

Start in 3 steps

You need a Mac (or Linux), Google Chrome, and Claude Code signed in.

1. Install (once)

bash
npm install -g fastpilot

2. Set up your project (once per project)

bash
cd ~/your-projectfastpilot init

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 or fastpilot init in a project, not both: both together start two fastpilot servers. With the plugin, a secret such as DEMO_PASS works like this: add its name in fastpilot 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 demo instead. It makes a demo folder with demo pages and example tests, and opens the dashboard on it.

3. Open the dashboard (every time)

bash
fastpilot ui

Your browser opens the dashboard. Keep the Terminal open while you use it; Ctrl-C closes it.

  • The link works once, for 10 minutes. If it expired, press Ctrl-C and run fastpilot ui again.
  • The dashboard only works on this computer.
  • Open it yourself; do not ask the AI to open it for you.

Everything else happens in the dashboard.

Guide: your first test in the dashboard

1. Check your devices: Device

Shows whether Chrome, Android, and iOS are ready, with a ✓ or the reason why not.

  • Install Chrome and Set up an emulator are one-click Fix buttons. Each asks you first, showing the size and the time it takes.
  • iPhone testing needs a one-time setup with your Xcode (about 5 minutes).
  • Only web? Chrome is enough.
[fastpilot's Device page: two Android emulators installed on this computer, each with a Start button, and the iPhone simulators tests can use.]

2. Pick the AI and store passwords: Settings

  • AI model: pick the provider, then the model. Claude Code is the default. Other providers (OpenAI, OpenRouter, Groq, Ollama) also work, and are marked "not tested yet".
  • Secret: add the names of passwords your tests need, for example TEST_PASS. Tests write them as ${TEST_PASS}, and they always show as ***. Never type a password in Chat.
  • Limits & permissions: see the next section, "Safe from the start".

3. Make an agent: Agents › New agent

An agent is a tester with its own job, devices, instructions, and skills.

  • Fill in three things: what it tests, where (Web, Android emulator, iPhone simulator…), and its instructions. Click a suggested instruction to add it.
  • Skills are ready-made test know-how, grouped by technique: boundary values, decision tables, regression, safe checkout, and more. Suggested skills are already ticked, each with a reason. With Atlassian's MCP server in Claude Code, three Jira skills turn tickets into tests, log a failed run as a bug and post results; each write to Jira waits for your OK (setup).
  • Or simply describe the agent in one sentence in Chat and click Create.

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.

4. Ask for a test: Chat

Write what you want in plain words:

You want toType in Chat
Check something nowCheck that login on https://yourapp.com goes to the Dashboard
Save a testCreate a test for the checkout flow and save it
Test a field properlyTest the quantity field properly (it picks the technique and shows what it covered)
Run everythingRun a regression (newly failing tests come first)
Before a releaseIs staging ready to ship? (one verdict: SHIP, SHIP WITH FIXES, DO NOT SHIP)
Understand a failureWhy did the checkout test fail?

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.

5. Watch it run: Live

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.]

6. Run it automatically: Schedules

  • Every N hours (with active hours, for example 08:00–20:00), every day, or every week.
  • Run now for any schedule.
  • Release watch: after a release, re-check every few minutes for a few hours and only tell you about new problems.
  • Get notified by Slack webhook, Mac notification, or GitHub issue when something fails.
  • Or just ask in Chat: "run the checkout tests every 2 hours".
[The Schedules page: a test that runs every 2 hours from 08:00 to 20:00 and a release watch that checks every 10 minutes, each with its next run, a passed last run and a Mac notification on failure.]

7. See results: History and Memory

  • History: every run and every Chat conversation, with report, screenshots, and video. Delete one, several, or all, or let them be deleted after 7, 30, or 90 days.
  • Memory: how each test is doing (Reliable, Unstable, Failing, Set aside), plus project notes every agent reads, for example "Staging is https://staging.yourapp.com" or "Login uses a code".

Dashboard map

MenuWhat it's for
AgentsYour testers: Chat, Live, Schedules, Instructions, Skills, History, Agent settings. Also the skill Library
LiveEvery running test, from all agents
SchedulesAll schedules and release watches
MemoryTest health and project notes
HistoryPast runs and conversations
DeviceChrome, Android, iOS readiness and Fix buttons
SettingsAI model, Limits & permissions, Secret

Safe from the start

  • Buttons like pay, buy, checkout, transfer, delete account are always blocked.
  • Plain delete/remove buttons must be confirmed first.
  • The AI can make the rules stricter, never looser. To loosen one, you approve it: Chat shows a red card that quotes what you asked, and allowing Pay also needs you to type "Pay". Text on a tested page can never ask for a change.
  • Every change is kept in ~/.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.

Prefer the terminal?

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.

If you get stuck

Open Device in the dashboard, or run:

bash
fastpilot doctor
ProblemTry
The dashboard link doesn't workIt works once, for 10 minutes. Press Ctrl-C, then run fastpilot ui again
Chrome or Android isn't readyDevice › Fix buttons, or fastpilot setup web / fastpilot setup android
iPhone isn't readyfastpilot setup ios (once, with Xcode)
fastpilot doesn't show up in ClaudeRun fastpilot init again
A test stops with "Blocked by limits"That's on purpose. See Settings › Limits & permissions
A saved test can't find its password in fastpilot runExport it first, e.g. export FASTPILOT_VARS=TEST_PASS TEST_PASS=...

Learn more

License: Apache-2.0

来源:README.md,提交 71421b9

工具

10

assert

Deterministic assertion with auto-retry: visible | not_visible | text_equals | contains | enabled. Returns pass, or fail with reason and snapshot.

输入参数kind必填textsessiontest_idtimeoutselector必填

check_flow

Validate a flow without running it: syntax, unsupported steps, unknown sessions, parallel rules, missing ${VAR}s. Errors carry line numbers.

输入参数flow必填

config

fastpilot 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.

输入参数keyvalueaction

docs

fastpilot 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).

输入参数topic

report

Close 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.

输入参数notesstatus必填test_id必填quarantine

run_flow

Run 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`.

输入参数flow必填sessiontest_idstop_on_fail

screenshot

JPEG screenshot of a session, for visual fallback and evidence.

输入参数sessionannotate

session

Session 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).

输入参数idmodeaction必填devicetargettest_idendpointplatform

snapshot

Compact text snapshot of a session (one node per line, stable refs eN). Rarely needed: run_flow already returns state.

输入参数filefullcoordsfilterformatsessioninteractive

state

Saved 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.

输入参数nameaction必填session

版本历史

1
  1. v0.5.1最新Nov 21, 2026

评分

已满足适用检查项的 90%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分
  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分