Desktop

The desktop app is the no-code way in — and everything it makes is a plain .flow.yaml file an engineer can open in any editor.

• Projects are folders. New Project asks one thing: a name. Under the hood every project is a git repository (embedded — no git install needed).
• Record. Click through your app in the device mirror; each click becomes a step. The first recording asks what you’re testing — that URL becomes the project’s Staging address.
• Run. Pick a device on your machine (browsers, Android, iOS simulators), watch steps go green live, with a per-step network drawer.
• Steps ⇄ YAML. Two views of the same file; comments and formatting survive edits.
• Save version & Publish. Save version = a local checkpoint with a comment, works offline. Connect any git remote over HTTPS + token and the same button becomes Publish — commit + push in human words. Conflicts are resolved whole-file: theirs / mine / compare.
• Variables. A project panel lists every ${VAR} a flow uses, where it gets its value (flow env:, config.yaml, .env, run overrides) and which are still undefined. Run dialogs prompt for a flow’s declared params:.
• Secrets stay out of chat. When the AI chat needs a real credential it opens a dialog instead of asking in the conversation — the value lands in the project’s .env and the flow references ${NAME}; the model never sees it.
• Report a problem. Settings zips the app logs and version info — inspect it locally, or send it to the team with one click; the reply is a report id you can quote, and Settings shows the report’s triage status.
• Devices. A graphical tapstep doctor: detect → fix, one-click managed Chromium, simulator boot, SDK locate.

Updates install themselves — a quiet “Update ready · Relaunch” chip appears in the status bar when a new version is downloaded.