Skip to content

Desktop app — QAMind Terminal

The tests run
on your machine.

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

Some apps cannot be tested from the cloud.

1

Your app under test never has to face the internet

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.

2

Scheduled suites can run on your machine

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.

3

Credentials live in the OS keychain

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.

4

The agent's history stays on the device

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

Four panes, one window.

Agent

Draft a plan, approve the actions, then run. The same agent contract the web app and the mobile app use.

Terminal

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.

Results

Cloud run evidence, a side-by-side script diff, and Open in QAMind.ai to jump back to the full workspace.

Local Runner

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

Running in four moves.

1

Download and install

Windows installer, around 90 MB. Windows 10 and 11.

2

Sign in

The same QAMind account you use on the web. The session is handed to the OS keychain, not written to disk in the clear.

3

Start the Local Runner

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.

4

Set a suite to Auto

From then on, schedules run on your machine while the app is open and fall through to the cloud worker when it is not.

Keep the browser on your own machine.

Install it once, leave it open, and your schedules stop queueing for a cloud worker.