How it works
Device is missing or offline
Confirm the agent process is running, your computer has outbound network access, and you are signed in to the same RemoteCommand account.
npx -y @lhtsoft/remotecommand-agent@latest doctorPairing code expired or failed
Restart the enrollment process, compare the one-time code, and approve the matching request in the browser. Device pairing is not the same as MCP client authorization.
npx -y @lhtsoft/remotecommand-agent@latestMCP OAuth or setup failure
Check that the AI client supports remote Streamable HTTP MCP and OAuth, and use the published endpoint. Dedicated ChatGPT and Claude buttons are still marked Coming soon.
https://api.remotecommand.app/mcpPermission denied or approval required
Check the chosen device, allowed folders, operation policy and approvals queue. Do not bypass blocked commands by repeatedly changing arguments.
When terminal requests fail
Standard access does not enable terminal execution. Explicit local opt-in, operation policies and OS account permissions govern terminal commands.
When to contact support
Capture the time, agent version and non-sensitive error message. Do not send device credentials, OAuth tokens or sensitive command output. Use the public Support page.
Frequently asked questions
Does reconnecting an agent reset all permissions?
A normal agent restart with saved registration is intended to retain the device identity and its saved permissions.
Can an MCP OAuth login repair an offline computer?
No. The device agent must separately connect to the RemoteCommand service.