LOCAL COMMANDER / SECURITY

Is it safe?

The most common worry: “So my computer is now open to the internet, and anyone can get in?” No. Nothing is left open. Your computer is reachable only by you, through the AI apps you signed in yourself.

Updated

At a glance

  • No open ports. Your computer calls out; nobody can call in.
  • A computer joins your account only after someone at that computer approves it.
  • Only AI apps you signed in to with your Local Commander account can send work.
  • You choose what the AI can touch. Access can be widened only at the computer itself.
  • The real keys are your accounts. Protect them like your email or your bank.

No open door on your computer

Local Commander doesn’t open a port, doesn’t change your router and doesn’t need a VPN. The small program on your computer connects out to Local Commander over an encrypted connection and waits for work on that line, the way a messenger or a remote-help app does.

Nothing on your computer listens for connections from the internet. There is no address someone could find and knock on. If a stranger scans your network, there is nothing of ours to see.

Only computers you approve join your account

To add a computer, you start Local Commander on that computer and approve it in your account. A click in a browser alone isn’t enough: each computer has its own secret key that never leaves it, and every connection is signed with that key. A copied link or a stolen screenshot can’t add a computer to anyone’s account.

Helping a relative works the same way: their computer joins only after the approval is done on it, with their permission.

Only your AI apps can send work

Work reaches your computers only from AI apps — ChatGPT, Claude or another — where you signed in with your Local Commander account and allowed access. Someone else’s ChatGPT can’t reach your computers, even if they know Local Commander exists.

Your account page lists every connected AI app and every computer. Remove any of them with one click.

You set the limits

When you set up a computer, you choose: full access to your user account, or only the folders you pick. You can also block specific commands.

These limits live on the computer. Access can be widened only by someone at that computer — not from a chat, not from the website and not by the AI itself.

See everything, stop anytime

Every task your AI ran is in your account’s activity, in plain words: which computer, what it did, what came back.

To stop a task, ask your AI to cancel it, or close Local Commander on that computer. Removing a computer from your account blocks any new work right away; a task already running finishes or stops when you close the program there.

Where the real risk is

We’d rather say it plainly than hide it in small print.

  • Your accounts are the keys. Anyone who gets into your ChatGPT, Claude or Local Commander account can do what you can do. That’s the same risk as with your email or online banking, and the same protection works: a strong password and two-step sign-in on your AI accounts.
  • The AI can make mistakes. It can misread a request or follow bad advice it found online. On a computer that isn’t yours, such as a parent’s laptop, give access to the needed folders only.
  • It isn’t a sandbox. Work runs with the permissions of the user account on that computer. For stronger separation, run Local Commander under a separate user account.
  • Results pass through our service on their way to your AI. The privacy policy says what is kept and for how long.

In short: nobody gets in by accident or from outside. The access exists only in your hands — and in the accounts you protect.

Report a concern

Email Peter at peter.mamrukov@localcmd.app with a short description. Don’t send passwords, sign-in links or keys. For sensitive vulnerability details, ask for a secure way to share them first.

What is installed and how to check it

This part is for anyone who wants to know exactly what Local Commander puts on a Windows computer, what it sends and how to check its files. The last part is a short list of sources for technical reviewers.

The complete technical list for Windows, macOS and Linux is in DISCLOSURE, the same file the agent package ships since version 0.3.66. It covers every file the agent writes, what runs, what it reads, its network use, complete removal and the antivirus history.

What the npm package puts on your computer

Setup with npx --registry=https://gitlab.com/api/v4/projects/88458751/packages/npm/ local-commander-agent@latest installs:

  • The localcommander command, added to your user PATH, and a Local Commander Monitor entry in the Start menu.
  • A folder for each version in %LOCALAPPDATA%\LocalCommander\Versions. It holds the agent (agent.mjs) and these programs:
    • node.exe runs the agent. It is the official Node.js program from nodejs.org, signed by the OpenJS Foundation, with its license file next to it.
    • LocalCommanderAgent.exe starts the agent: it runs node.exe from the same folder and nothing else.
    • JobHost.exe runs each command your AI asks for inside a Windows Job Object. When a command times out or you cancel it, the whole group stops: the command and every process it started, not only the first one.
    • OwnerBridge.exe keeps this computer’s Local Commander keys protected for your Windows user, shows the windows where you choose folders and approve access, and takes a screenshot when your AI asks for one. You can turn screenshots off with localcommander screenshot off.

The three helper programs are our own and are built from our own source code in agent/windows. The agent, node.exe and JobHost.exe run without a window: they work in the background, and a window for every command would pop up over whatever you are doing. OwnerBridge.exe shows a window only when you need to choose or approve something.

On computers with Smart App Control

Smart App Control in Windows 11 can block programs without a trusted signature, and that includes our helpers. On a computer where it is on, Local Commander runs without them. Setup notices it and uses only node.exe and programs that come with Windows:

  • Starting: node.exe runs the agent directly. The startup entry starts it through Windows’ own conhost.exe, so no window opens.
  • Commands: the agent starts each command itself and keeps track of the processes it starts. When a command times out or you cancel it, the agent stops the command and every process it has seen it start. Without a Job Object this is less strict: a process that detaches between two checks can keep running, and the number of processes a command starts is not capped. Each command also takes one to five seconds longer. If the agent stops while a command runs, that command’s result stays unknown, and it keeps its place in your limit, until Windows restarts.
  • Keys: instead of Windows data protection, they are encrypted with a key file in the agent’s folder, which only your Windows user and the system can open.
  • Choosing access: you choose Full Access or one folder in the terminal where you run setup or localcommander configure-access, not in a separate window. Access can still be widened only by someone at that computer.
  • Not available: screenshots and the folder-picker window.

localcommander status shows whether Smart App Control is on and which mode the agent uses.

How it starts and how to stop it

After setup the agent runs in the background. It also starts each time you sign in to Windows: setup adds an entry named LocalCommanderAgent to your user’s startup list in the registry (HKCU\Software\Microsoft\Windows\CurrentVersion\Run). Setup creates no scheduled task and no Windows service, and it doesn’t need administrator rights.

  • See it: localcommander status shows the installed version, whether it is running and whether the computer is paired. localcommander monitor --watch, or Local Commander Monitor in the Start menu, shows live connections and tasks. In Task Manager the agent appears as node.exe.
  • Stop it: localcommander stop. Start it again with localcommander start. Stopping doesn’t remove the startup entry, so it starts again the next time you sign in.
  • Remove it: npx --registry=https://gitlab.com/api/v4/projects/88458751/packages/npm/ local-commander-agent@latest uninstall stops the agent and removes the startup entry, the Start menu entry, the PATH entry and the program folders. It keeps this computer’s pairing so a reinstall can reuse it; add --purge-state to remove that too.

What leaves your computer

The agent sends data to the Local Commander service over the encrypted connection it opens itself.

  • Pairing and identity. When you add the computer, it sends its public key, the Local Commander version and the computer’s name so your account can recognise it. The private key stays on the computer.
  • Results of work you allowed. When your connected AI app asks for something within the access you set, the result goes back to that AI app through our service.
  • Usage records. Which tool ran, when, how it ended and how many bytes it returned, without the command, file paths or the output itself.
  • Model token counts: not from the agent. Since version 0.3.67 the agent doesn’t read Claude Code or Codex session files. If you want token statistics, you can create a key on your Statistics page and set up Claude Code or Codex to send their own usage counts to Local Commander with it. Versions up to 0.3.66 could read token counts and model names from those files when you turned this on for the computer; updating removes that reader.
  • Full logs, only if you turn them on. They are off by default.

The privacy policy lists each kind of record the service keeps and how long it keeps it.

Signatures and how to check the files

node.exe carries the OpenJS Foundation’s digital signature. Our three helpers — JobHost.exe, LocalCommanderAgent.exe and OwnerBridge.exe — are not signed with an Authenticode certificate: we decided not to buy one, and a signature would not stop behaviour-based antivirus checks anyway. The decision is written down in our decision records.

Instead, each file is identified by its SHA-256 fingerprint. Since version 0.3.64, every version carries a list of the fingerprints of all six runtime files (runtime-manifest.json), written when the release is built. The build uses only an exact, pinned Node.js (signed by the OpenJS Foundation) and an exact, pinned Microsoft C# compiler (signed by Microsoft), and it stops if either one differs. With the same source and compiler, the build gives the same helper files byte for byte. Install and update refuse a missing or modified file. Versions 0.3.63 and earlier were built before this check existed and have no such list.

There is no separate check command yet. To check an installed version yourself, run localcommander status to see the version, then run this in PowerShell with that version number:

$dir = Join-Path $env:LOCALAPPDATA "LocalCommander\Versions\<version>"
$list = Get-Content "$dir\runtime-manifest.json" -Raw | ConvertFrom-Json
foreach ($f in $list.files) {
  $hash = (Get-FileHash -Algorithm SHA256 (Join-Path $dir $f.name)).Hash.ToLower()
  "{0}  {1}" -f $(if ($hash -eq $f.sha256) { "same" } else { "DIFFERENT" }), $f.name
}

Every line should say same. To compare the installed list with the published one, download the package with npm pack --registry=https://gitlab.com/api/v4/projects/88458751/packages/npm/ local-commander-agent@<version>, unpack it with tar -xf local-commander-agent-<version>.tgz and compare package\runtime\runtime-manifest.json with the installed file.

Antivirus incident: findings and current status

As of 17 November 2026: behaviour-based protection in Kaspersky products still blocks or removes the command helper JobHost.exe on some computers, after which Local Commander stays connected but commands stop running. Kaspersky could not reproduce the detection on its side, has not called it false, and has declined our application to its Allowlist Program without giving reasons. Replies from other vendors cover only specific files. We have not found a change that makes this detection stop, so we do not call it fixed.

How every release is checked now

  • Two antivirus scans before every Windows release. Since 15 November our publishing tool refuses to publish a Windows package unless that exact file, identified by its SHA-256 fingerprint, has passed Microsoft Defender with real-time protection on and ClamAV with current databases, both as an archive and file by file. A missing scan or a fingerprint that does not match stops the whole release before anything is uploaded. Version 0.3.74, published on 17 November, is the first to go out through this check; the scan record is kept in our repository.
  • Kaspersky is checked every six hours. A test computer with Kaspersky Endpoint Security runs a real command through JobHost.exe every six hours while our checking computer is on. We get an alert for any new Kaspersky event about Local Commander, any new quarantine entry or any change to the helper file, and each database update is recorded. This is how we learned about a 14 November detection on our own computer from our own alert, not from a customer.
  • No "fixed" without proof. We say a detection is fixed only after the installed release has run real commands on that antivirus product across at least one database update. Until then we write "not detected so far", with the date.
  • The helper file stays the same. JobHost.exe has not changed by a single byte since version 0.3.64 (SHA-256 below), so a vendor's decision about that file keeps applying to every newer version. We change it only to fix a defect, and then the checks above start again for that file.
  • You learn about it straight away. Since version 0.3.68, if the helper disappears, for example into quarantine, the dashboard shows that computer as online with commands unavailable and the account owner gets one email. File tools keep working.
  • Smart App Control. Since version 0.3.68, on Windows computers with Smart App Control on, Local Commander runs without its three helpers, on node.exe and Windows' own tools.

What the scans do not show: Defender and ClamAV check the files themselves. Kaspersky's detection is behavioural: it reacts while a command is running, and so far it has appeared days after installation, following a database update. A clean scan before release cannot rule that out, which is why the watch on a Kaspersky computer exists.

What happened, and when

  • 23 October and 3 November 2026: users reported Kaspersky quarantining JobHost.exe in versions 0.3.41 and 0.3.58 as PDM:Trojan. Local Commander could remain connected while commands stopped working.
  • 4 November: we verified that the reported 0.3.58 JobHost.exe matched our original release file by size and SHA-256, reviewed its source and sent the detection details to Kaspersky. We released 0.3.64 with reproducible helper builds, pinned build inputs and per-file integrity checks. JobHost no longer starts commands suspended and then resumes them; batch files no longer use an encoded PowerShell command. These changes strengthen the build and execution path; they do not establish the exact cause of the detection.
  • 5 November: Kaspersky replied: Sorry, it was a false detection. It was fixed. That reply concerned the reported 0.3.58 JobHost.exe only.
  • 5 and 6 November: AVG confirmed that the three helpers submitted from 0.3.63 and 0.3.64 had been whitelisted.
  • 6 and 7 November: the unchanged 0.3.64 JobHost.exe was detected again by behaviour analysis, after database updates: moved to quarantine on our Kaspersky Endpoint Security test computer and removed on a customer's Kaspersky 21.26. We sent both cases to Kaspersky.
  • 11 November: 0.3.68 added the "commands unavailable" report and email, and the Smart App Control mode.
  • 14 November: our Kaspersky check recorded another detection of the same file on the test computer, with that day's databases, and alerted us on 16 November. A VirusTotal check of the current JobHost.exe showed 3 of 75 engines flagging it (Bkav, McAfeeD and APEX); Kaspersky and Microsoft did not. We reported the file to Bkav, McAfee and SecureAge as a false positive.
  • 15 November: a customer's Kaspersky Premium 21.26 blocked the same file twice under a new verdict, PDM:Exploit.Win32.Generic (blocked, not deleted). The same day the two-engine scan became a required step for every Windows release. McAfee replied that a file named "7.zip" from our submissions had been whitelisted, without saying which file it contained; we have asked.
  • 16 November: Kaspersky replied that it could not reproduce the detection, asked us to update the antivirus databases and, if it persists, to send screenshots and a product trace log. In the same reply it said its malware experts had rejected our Allowlist Program application and cannot give the criteria, and pointed us to its virus lab for false detections. We sent the case to the lab on 17 November.
  • 17 November: Kaspersky confirmed that its test used JobHost.exe with the SHA-256 below and said it does not disclose the product build or database date used. We published 0.3.74 after it passed the two-engine scan; JobHost.exe in it is the same file.

Exactly what the vendor replies cover

JobHost.exe in every version from 0.3.64 to 0.3.74 is this one file (17,920 bytes):

de3e6a4e8a561431c7e696f5267d79625635138482e02c91b9db4936e013b201

Kaspersky: the 5 November correction covers the older 0.3.58 file (26e5dac7…02fc67) only. For the current file, Kaspersky could not reproduce the detection in its own test; that is not a confirmation that the detection was false, and it says nothing about the behaviour that customers still see. The Allowlist Program application was rejected on 16 November.

AVG: the 6 November report classifies the following 0.3.64 helper files as Clean and confirms their whitelisting. JobHost.exe is the file above; all three match the helpers in every version from 0.3.64 to 0.3.74:

LocalCommanderAgent.exe
375222627daca099b12d9bb888f159570fbb07cecd3d5a1d36940ebd26a0c0a8

OwnerBridge.exe
98959a63c6f3cfcdaba0b7de146ceb7699caef82392a227df6644d2c502b9127

JobHost.exe
de3e6a4e8a561431c7e696f5267d79625635138482e02c91b9db4936e013b201

Neither AVG report lists agent.mjs or node.exe, and neither is a blanket approval of the complete package, other operating systems or future builds. We do not extend AVG's reply into separate approvals from Avast, Norton or Avira.

McAfee: "7.zip" was whitelisted, but until McAfee tells us which file that was, we do not count it for any specific Local Commander file.

Waiting for an answer: Bkav, SecureAge (SecureAPlus), Xcitium, Trend Micro and ESET have our files or applications; we have automatic acknowledgements or requests for the file, not results. A Bitdefender clean-file reply concerns the Nulio connector, not Local Commander.

Checks and risks that remain open

  • Kaspersky's behaviour detection of JobHost.exe is not resolved. A separate test computer with Kaspersky 21.26 is prepared (Kaspersky Plus: the free trial we could get activated Plus rather than Premium); the ordinary command, timeout and cancellation tests before and after a database update have not been run yet. When they have, the result will be here.
  • The three helpers remain unsigned with Authenticode. Hash matching verifies file identity; it does not certify that software is harmless. Local Commander executes work with the operating-system permissions of its user account, as explained above.
  • The GitHub advisory for npm version 0.3.52 is a separate registry record. The vendor replies above do not establish that it has been withdrawn, and changing the distribution registry does not resolve it.

Evidence and privacy: this chronology is our summary of the vendor replies, versioned release manifests, scan records and recorded tests. We keep the original correspondence and the investigation record, and can arrange a redacted evidence review: write to peter.mamrukov@localcmd.app. We do not publish private email threads, customer logs or account details. For file checks, use the version-specific package and manifest instructions above. Vendor background: Kaspersky Allowlist Program and AVG Whitelisting Program.

If your antivirus still flags a file

  • Keep protection enabled. Do not restore the file from quarantine or add broad antivirus exclusions for Local Commander.
  • Check the version and fingerprints using the instructions above. If protection blocks a file, report it before attempting repeated reinstalls.
  • Send us the detection: the Local Commander version, file SHA-256, antivirus product and database version, exact detection text and time. Remove personal data from any screenshot or log. Email peter.mamrukov@localcmd.app.
  • Kaspersky users: Kaspersky has asked for a screenshot that shows both the file name and the verdict, and a product trace log (how to collect one). A trace log can contain personal data: send it to Kaspersky support directly, not to us, and tell us the case number.

Notes for reviewers

The source repository is not public. We share the files below with reviewers on request: write to peter.mamrukov@localcmd.app.

  • Helper source: agent/windows/JobHost.cs, agent/windows/AgentLauncher.cs, agent/windows/OwnerBridge.cs. JobHost assigns the Job Object at CreateProcess (PROC_THREAD_ATTRIBUTE_JOB_LIST, CREATE_NO_WINDOW) and never starts a child suspended.
  • Installer, startup entry and integrity check: packages/agent-cli/bin/localcommander.mjs, packages/agent-cli/bin/runtime-manifest.mjs.
  • Build and pinned toolchain: scripts/build-agent-package.mjs, scripts/toolchain-provenance.json.
  • Model token counts: the receiver for the counts Claude Code and Codex send themselves is apps/control-plane/src/otlp.ts. The agent’s session-file reader was removed in version 0.3.67.
  • Decisions: ADR-RUNTIME-INTEGRITY-743-20261104 and ADR-NO-CODE-SIGNING-20261104 in planning/ARCHITECTURE_DECISIONS.md.
  • Release hold: new versions are not published while the hold in scripts/release-hold.json is active.