Files, with context
Find a file, read its contents, and make a precise edit. Work inside the directories you’ve allowed.
read_file · edit_block · start_searchConnect ChatGPT, Claude, Cursor and other remote MCP-enabled AI apps to your PCs and servers. Find files, run code and review results. AI Efficient Mode helps reduce unnecessary tool output and AI input tokens.
ChatGPT · Claude · Cursor · other remote MCP apps
$ python -m pytestcollected 12 items12 passed · exit code 0
Illustrative demo · Runs with your permissions.
AI directs each device through RemoteCommand, interprets its results, and uses them to guide work on another device.
For example, inspect code on a PC, then ask a server to run the relevant tests. AI coordinates the steps; devices do not collaborate autonomously.
Keep your tools and files where they are. Bring the work into the conversation.
Find a file, read its contents, and make a precise edit. Work inside the directories you’ve allowed.
read_file · edit_block · start_searchStart a process, follow its output, and return to the result. Long-running work stays visible in sessions.
start_process · read_process_outputInspect Git changes and work with Docker containers using the tools on your PCs and servers.
git_status · git_diff · docker_logsRemoteCommand's AI Efficient Mode reduces repetitive command output, keeps requested files accessible, and lets AI continue reading long results in ranges.
Repeated progress messages make it harder to spot what matters.
Get to useful signals faster when logs are noisy.
Read exact code and documents when the task needs them.
Explore more output in ranges instead of losing context.
Reducing tool output can save AI input tokens. Your dashboard measures output data reduction in bytes and, for supported agent runs, estimates saved input tokens from actual text. These metrics do not directly measure your AI bill; results vary by task.
Create your RemoteCommand account.
Install the agent on each PC or server and set its file and command permissions.
Connect MCP, review permissions, and start your first task.
https://api.remotecommand.app/mcpStart with a monthly allowance. Move to Pro when your projects grow.
Your own AI-to-computer workspace, ready to explore.
For bigger workloads that should not stop at a monthly quota.
Works with ChatGPT, Claude, and other MCP-compatible apps. Local taxes and final pricing are shown before payment.
Allowed folders · Command approval · Activity logs · Revoke access
AI chooses a device for each task through RemoteCommand, reviews the returned output, and directs the next task to the appropriate device. Devices do not independently communicate or delegate tasks to one another. Each task follows the target device's permissions and approval policies.
RemoteCommand connects AI tools to files, terminal commands, Git, Docker, and processes. It does not currently stream your screen or operate your mouse.
Your working files remain on each device. Requested file content and command output travel through the RemoteCommand relay to the AI service you connect. Review that AI service’s data policies too.
RemoteCommand provides a remote MCP endpoint with OAuth. Connect it from an AI client that supports remote MCP. Available connector settings depend on your AI client and account; this is not an official OpenAI or Anthropic product.
RemoteCommand connects Windows, macOS and Linux computers with one Node.js agent. Install Node.js LTS, then run npx -y @lhtsoft/remotecommand-agent@latest in a terminal. No separate agent installer is needed.
Stop the running agent with Ctrl+C, then run npx -y @lhtsoft/remotecommand-agent@latest run as the same OS user. If npx is missing, install Node.js LTS from nodejs.org and reopen your terminal. Background services are updated separately by their administrator.
Allowed directories constrain file tools. Approved terminal commands run automatically with the agent user's operating system permissions and may affect files outside those folders. Enable only the capabilities you need.
ChatGPT and Claude use separate safety checks and tool permission controls, so their warning messages and decisions may differ. A request may be blocked before it reaches RemoteCommand; this does not necessarily mean a RemoteCommand outage or a monthly usage limit. Check the requested action and permissions granted to your AI client. For file or Git inspection, prefer read-only tools such as read_file or git_status instead of execute_code. Do not try to bypass a block on an unsafe action. If a legitimate request is repeatedly blocked, contact support with the AI client name, tool name, approximate time, and exact error message. RemoteCommand cannot disable either provider's safeguards.