Agent
Draft a plan, approve the actions, then run. The same agent contract the web app and the mobile app use.
Desktop app — QAMind Terminal
Agent, a real terminal, and a managed Local Runner in one app — so the thing you are testing never has to be reachable from the internet.
Windows 10 and 11. A macOS build is not published yet.
Why it matters
Exploration and execution run through the Local Runner on 127.0.0.1:3199, on your machine — not on our servers. That is what makes localhost, a staging box behind a VPN, and an internal tool nobody can reach from outside testable at all.
A schedule set to Auto resolves at the moment it fires: if a Local Runner is connected it runs locally, headless; if your machine is off, it falls through to the cloud worker. Keeping the desktop app open is how a tester contributes their own execution capacity.
The main process stores your session with the operating system's own secure storage, plus a per-install runner secret. Not a token sitting in a config file next to the project.
Chat history is kept locally, per workspace. Messages are sent to QAMind to be answered, and plans are drafted for you to approve before anything runs.
What is in it
Draft a plan, approve the actions, then run. The same agent contract the web app and the mobile app use.
A real shell — a PTY, with a pipe fallback — and the bundled qamind CLI already on PATH. Nothing to install to run qamind test run.
Cloud run evidence, a side-by-side script diff, and Open in QAMind.ai to jump back to the full workspace.
Managed for you. It attaches to a healthy listener on 3199 rather than starting a second one, so there is no port to juggle and no duplicate runner racing the first.
Setup
Windows installer, around 90 MB. Windows 10 and 11.
The same QAMind account you use on the web. The session is handed to the OS keychain, not written to disk in the clear.
One button in the Terminal pane. If Node is already on your machine it is used; if not, the app falls back to its own bundled Node, so there is nothing else to install.
From then on, schedules run on your machine while the app is open and fall through to the cloud worker when it is not.
Install it once, leave it open, and your schedules stop queueing for a cloud worker.