Stealth Commander support

Help for your
connected PC.

Setup and troubleshooting for Stealth Commander. Check the connection and the tools available on your paired Windows PC.

Start here.

How do I create an account?

Open Create account and complete the sign-up form. Once signed in, you can view your account and paired PCs. Follow the Windows preview setup guide to install and pair the client.

How do I install and pair the Windows client?

Use Windows x64 with Node.js 18 or newer and regular CPython 3.13 x64 (recommended). Regular CPython 3.11 through 3.14 x64 is supported. The pinned dependencies do not support Python 3.15, free-threaded builds, or ARM builds.

Download the Windows ZIP and SHA-256 checksums. Extract the ZIP, then open PowerShell in the folder containing package.json. Run node ./bin/stealth-commander.js setup --enable-remote and enter your account key at the hidden prompt. Leave the client running and confirm this PC appears in your account. An npm package archive is also available.

I cannot connect or see my PC.

Confirm that you are signed in, the Windows client is running, and local pairing and remote setup are complete. Use your host's connection flow to sign in through OAuth and select the intended paired PC. The device must stay online.

If access has expired or was revoked, reconnect through the supported sign-in flow. Do not share account keys or substitute a direct tunnel URL.

If setup reports a heartbeat or account update failure, keep the client running, check your connection, and retry the same setup command. A failed heartbeat does not mean setup completed.

A tool or application workflow is unavailable.

Ask for a readiness report and check the tools exposed by the connected PC. The installed client determines available capabilities; updating the chat plugin does not update that client. Browser and IDE workflows also need their own application dependencies.

Report the actual missing capability or returned error. Do not assume a launch tool provides arbitrary clicking or typing in every application.

An observation is missing or stale.

Check the owned session's observation status and capture timestamp. Cached-image export reads an already-published frame; it does not start an observer or request a new screenshot. An unavailable, expired, protected, or mismatched frame should remain an explicit error.

A command or session operation timed out.

A timeout may leave the result uncertain. Inspect the exact owned session or task state before retrying an operation that could change something. Keep the original session identity and stop only that session when its task is complete.

Can it operate my current desktop or record audio?

The supported workflow uses owned hidden sessions and preserves shared foreground input. It does not provide arbitrary full-desktop video or system-audio recording. See the operating scope before starting a task.

Check access before retrying.

An offline PC, missing dependency or expired sign-in needs to be resolved before a task can continue. Repeatedly retrying a command does not fix those conditions.

These pages provide product information and troubleshooting guidance. Connecting a PC requires local pairing and device consent after account sign-in.