Skip to main content
MCP · RemoteCommand

Install RemoteCommand on a connected computer

The Node.js agent runs on Windows, macOS and Linux. You enroll and authorize each device before an AI client can use its permitted tools.

For security, install a supported Node.js LTS release (22, 24 or 26). Node.js 18 and 20 no longer receive security updates.

Install Node.js

Use a supported Node.js LTS release (22, 24 or 26) and apply security updates. The terminal needs outbound HTTPS/WSS network access.

npx -y @lhtsoft/remotecommand-agent@latest
Guide

How it works

  1. Install Node.js

    Use a supported Node.js LTS release (22, 24 or 26) and apply security updates. The terminal needs outbound HTTPS/WSS network access.

  2. Launch the agent

    Run this in PowerShell on Windows or a terminal on macOS/Linux. It starts a browser pairing flow; headless devices print a URL to open elsewhere.

    npx -y @lhtsoft/remotecommand-agent@latest
  3. Confirm pairing

    Sign in, verify the displayed pairing code within the allowed window, select accessible folders and a permission profile. Keep the agent process running for the connection.

  4. Check the connection

    Open device management to inspect status. If the agent is not online, use the local diagnostic command.

    npx -y @lhtsoft/remotecommand-agent@latest doctor

What does Standard allow?

The recommended Standard access profile allows read and write operations inside selected folders; terminal, Docker and deletion are disabled. Your actual rights depend on the saved policy and local settings.

Device lifecycle

The agent runs with the local OS account and reconnects when possible. Revoke a registered device from your account if it should no longer accept requests. An offline device cannot process live tool calls.

Frequently asked questions

Can I run the agent on a server without a browser?

Yes. The agent can print a pairing URL that you open from a separate browser to approve enrollment.

Does installing the agent give an AI full shell access?

No. Terminal access is separately controlled, and the device's local policies and approval checks continue to apply.

Next step

Read installation guide