Generate a Maestro test
Describe what the test should prove and Peach writes the flow:
The CLI inspects the app currently open in Peach, generates a short Maestro flow from your goal (taps, inputs, waits, and a final assertion that proves the goal), and runs it immediately. Successful generation uploads the recording as a preview. Failed generation keeps its partial flow and any captured recording locally. Both register the result in your dashboard. The output prints the result and run id, plus a preview link on success.
Two things make this different from an agent poking at your app:
- +The output is deterministic. You pay for authoring once; what runs is a plain flow with real assertions. Keep it in
.maestro/and it replays forever without another model call, exactly like a hand-written flow. - +The result is hosted. Pass/fail lands alongside your team’s other runs. Successful generation includes a preview recording and per-step trace; failed generation prints the path to its local partial flow.
Requirements
Maestro generation calls a model through Peach cloud, so it needs a
signed-in CLI (peach login) or a PEACH_API_KEY with the preview_upload and llm scopes,
and it charges the account’s available grants or prepaid balance. The preview upload rides the
same run.
Attribute runs to your account
Pass the repo so the run indexes under your account’s dashboard rather than your personal account: