← All use cases

QA your app with Computer Use

Walk through real product flows by clicking, and record whatever fails.

Computer Use walks through the main flows of your app, finds problems, and wraps up with a written bug report.

Intermediate
30m

Related links

Starter prompt

Test our staging app at the staging URL as a brand-new user. Walk through signup, creating a first project, and upgrading to the paid plan using the test card I've given you. Watch for broken buttons, layout glitches, confusing copy, and slow screens. Write a bug report with numbered repro steps, expected versus actual result, and a severity for each, then rank what to fix first. If a blocker stops a flow, note it and move on to the next one.

Introduction

Computer Use sees the app window, clicks, types, and records failures, catching functional and visual bugs. It is a desktop feature: it works on the macOS desktop app, and it is not available on the web, on iOS or Android, or on Linux. Tell ZeroTwo the environment, key flows, and report format. For a web app you can also try the built-in browser first.

How to use

Turn on Any App under Settings > Computer use in the desktop app (see Computer Use for the macOS permissions it needs), name the target and flows, and ask for a structured report. Type @ and pick the Computer Use plugin, or just describe the task:

  • @Computer Use Check my app in staging, covering signup and the billing upgrade. Log every bug with repro steps and severity.

ZeroTwo asks before risky steps such as submitting forms or confirming a payment, and it may hand a final step back to you. Use the test card from your payment provider's test mode, never a real card.

Practical tips

Be explicit about setup

State account state, test data, flags, and environment.

Name the issue types you care about

Bugs, layout, copy, or visual regressions.

Decide whether to stop or continue

Say if a blocker ends the run.

Good follow-ups

Fix a bug, draft tickets, or retest one flow in the same chat.

Suggested prompt

A structured QA pass over listed flows with a closing triage.

Related use cases