See what is ready
Check runtime and application prerequisites, discover available tools, and inspect the status of owned hidden desktop sessions.
Your Windows PC, connected
Stealth Commander connects a Windows computer you own or administer to a compatible MCP client. Check readiness, inspect hidden sessions, run authorized commands, and view supported observations on the PC you select.

The installed Windows client determines which tools are available. The connection acts on the paired device selected during consent.
Check runtime and application prerequisites, discover available tools, and inspect the status of owned hidden desktop sessions.
Run bounded commands with the selected Windows account’s permissions. Supported launch tools create separate, owned application sessions.
Review session status and cached window images. Images include their capture time and session identity.
The current Windows x64 client runs on your PC. The chat plugin connects to that client; it does not install the runtime.
Mac, Linux, and more stealth tools coming soon.
Preview 1.1.3-private.7. An npm package archive is also available.
Create an account, sign in, and copy your account key from Account settings. Extract the ZIP and open PowerShell in the folder containing package.json. Run node ./bin/stealth-commander.js setup --enable-remote and enter the key at the hidden prompt. This installs the client, pairs this PC, and explicitly enables remote access. Keep the client running and confirm this PC appears in your account.
Open the existing Stealth Commander connection in your host, sign in through OAuth with the same account, and choose the paired PC you want to authorize. The connection must already be available to your host or account.
Ask for a readiness report and inspect the tools the connected PC actually exposes. Additional browser or IDE workflows have their own prerequisites.
Owned hidden sessions keep their GUI input separate from your normal desktop. They do not sandbox the Windows account’s filesystem or network access. Commands still use that account’s permissions.
The supported workflow preserves your physical mouse, keyboard, personal browser profile, and existing IDE sessions. Cached observations are already-published frames; they are not a full-desktop video or system-audio recording.
Some browser and native-desktop capture workflows remain under testing. A successful connection or readiness check does not establish that every application can be controlled or captured.