App lifecycle commands
Four inputs describe how to bring your app up. The first three (install, build, start) run in order before verification; app_url tells the browser where to reach it:
| Input | Purpose | Example |
|---|---|---|
app_install_command | Install dependencies | npm ci |
app_build_command | Build the app | npm run build |
app_start_command | Start the server | npm run start |
app_url | Where to reach it (browser mode) | http://localhost:3000 |
All four are optional, but providing them is recommended. If you leave them out, the agent still verifies, it just has to resolve how to install, build, start, and reach your app from the repository first. Spelling the commands out skips that guesswork, so runs are faster and more reliable. Omit only the steps that don’t apply (e.g.
app_build_command when there’s no build).Monorepos
Point the action at a subdirectory withworking_directory. All commands, config, and verification run relative to it:
Focusing the agent
By default the agent decides what to verify from the diff. Steer it when you want specific coverage:| Input | Effect |
|---|---|
prompt | Extra instructions appended to the verification prompt |
max_turns | Cap on Claude Code conversation turns (default 100) |
model | Override the Claude model |
Give the job enough headroom — verification, fixes, and re-verification can take a while. Set a generous
timeout-minutes on the job (the examples use 45).What’s next?
Verification platforms
Verify through the browser, backend, and Node.js.
All configuration options
Every input and output, with defaults.