TourSee how it works in five short scenes

Remote access for AI agents

Run AI agents on your own machines.

Use your Claude, Codex, Grok, Cursor, or ChatGPT — no additional AI Commander app required. Run commands and long-running jobs on your servers, dev boxes and workstations, then collect the results.

Free for 10 machines No inbound ports Linux, macOS & Windows

See AI Commander in action

  1. 01How it works

    Install the agent on a machine you own. It dials out to the relay and shows a session code. Give the code to your AI, and it runs commands on that machine. Only the output travels back to the chat.

  2. 02Quick command

    Ask whether the NAS is running out of space. One remote_exec call runs df and du and answers in seconds.

See the full tour →

Get started

How to use AI Commander

No additional AI Commander app — your AI client is the UI. Install the host agent on machines you own (below).

01

Open your terminal AI

Claude Code, Codex, Grok or a similar CLI agent.

02

Attach with mcp add

Point it at https://aicommander.dev/mcp. Exact commands are below.

03

Talk to your machines

Give it the machine code from the host agent and ask in plain language.

01

Open your desktop AI

Claude Desktop, ChatGPT or Cursor.

02

Add a connector

Claude: Customize → Connectors. Cursor: MCP settings. ChatGPT: developer-mode connectors.

03

Talk to your machines

Give it the machine code from the host agent and ask in plain language.

01

Open your AI’s phone app

Claude, ChatGPT or Grok — not an AI Commander app.

02

Use the connector

Attach the AI Commander connector in that client, where it supports one.

03

Talk to your machines

Give it the machine code from the host agent and ask in plain language.

Install the host agent and connect your AI tool

  1. Install the host agent

    Install it on the machine you want your AI to control. It connects outbound and shows a private machine code.

  2. Connect your AI tool

    Add AI Commander to your own AI tool, then sign in.

    claude mcp add --transport http aicommander https://aicommander.dev/mcp
    codex mcp add aicommander --url https://aicommander.dev/mcp
    grok mcp add --transport http aicommander https://aicommander.dev/mcp
    opencode mcp add aicommander --url https://aicommander.dev/mcp
    pi install npm:@aicommander/mcp

    Use the server URL https://aicommander.dev/mcp and follow the step-by-step guide for your tool →

Verify direct downloads

SHA-256 checksums & signatures

Use the versioned GitHub Release and SHA256SUMS to verify your download. The buttons above follow the latest release.

Published version: … GitHub Release

macOS — Developer ID + notarization (not Ed25519)

Desktop PKG/DMG/ZIP installers are signed with Apple Developer ID and notarized. They do not ship detached Ed25519 signatures like the Linux agent. Download from the GitHub Release, then verify with shasum -a 256 -c SHA256SUMS after extracting the manifest alongside the artifact. Gatekeeper validates code signing when you open the installer.

Windows — Authenticode (not Ed25519)

The NSIS .exe is Authenticode-signed (Azure Trusted Signing). There is no detached Ed25519 signature. Download from the GitHub Release and verify with certutil -hashfile AICommander-Setup.exe SHA256 against the matching line in SHA256SUMS. Windows SmartScreen checks the embedded signature at install time.

Linux agent — Ed25519 + SHA-256

Use the signed installer flow in install docs: verify install.sig with the pinned public key before sudo. Direct binary downloads from /dist/latest/agent-linux-* include matching .sha256 and .sig files, but the installer pins an immutable /dist/v/<ver>/ set.

What you can do

From a quick command to an overnight run

Use the tools, projects and hardware already on your machines.

Run commands

Inspect logs, manage services and work with files on a headless server or desktop. Reach saved machines by alias from any connected client.

Explore use cases →

Leave long jobs running

Start a build, render or training run, close the chat, then return for status, logs or cancellation. Reserve an NVIDIA GPU for a job to avoid competing runs.

Jobs continue through network loss and the chat ending. Restart survival depends on the platform and setup.

Job lifecycle & restart limits →

Collect and send files Pro

Download a report or checkpoint, or upload a config or artifact. Transfer one regular file up to 100 MiB; archive a directory first.

Download links last 1 hour; blob access lasts 24 hours. Cleanup follows expiry.

File transfer guide →

Run a coding agent remotely

Start an installed Claude or Codex CLI as a detached job on the machine that holds your repository. Check its transcript and exit code later.

Coding agent walkthrough →

Keep useful machine notes

Signed-in clients can keep toolchains, project paths and build steps in a note file on the machine. Notes are scoped per account; operators of the machine can read and edit them.

Machine notes reference →
Security

Understand the access you give

Commands run with real operating-system permissions. Keep your machine code private and connect only AI clients you trust.

Outbound connection

No inbound ports or exposed SSH. Traffic is encrypted in transit through the hosted relay.

Clear data handling

The relay does not log or store commands or text results. Explicit file transfers use temporary relay storage.

Account-based access

A new code allows an account-free trial for one hour. Afterward, only approved accounts can use it, until you reset access.

This is real machine access, not a sandbox. Screenshots require the owner's time-limited grant on macOS or Windows; macOS also needs Screen Recording permission.

Read the security model & limitations →
Plans

Start free. Add capacity when you need it.

Free

$0

Up to 10 saved machines. Commands, long-running jobs, GPU reservations and machine notes.

Start with Free

Pro

$49 / month

Everything in Free, every saved machine up to the technical ceiling of 100, plus file transfer.

See Pro details

100 machines is a technical ceiling. Need more? Get in touch.

Questions

Before you connect

Do you have a mobile or desktop AI Commander app?

No, on purpose. Use Claude, Codex, Grok, Cursor, or ChatGPT as the UI; on your phone, use that client’s app. Attach the AI Commander MCP server or plugin. We only run the host agent on machines you own.

How do I let Claude, Codex or ChatGPT run commands on my own server or box?

Install the host agent on that box — a VPS, a home server or your workstation — connect your AI client and give it the private machine code. Ask for a task in plain language. Sign in to save machines by name, or use the one-hour account-free trial.

How do I run a job that keeps going after the chat ends?

Start a detached job. It returns a job ID, continues on your machine through network loss and the chat ending, and lets you check status and logs later. On Linux, surviving an agent restart requires systemd and a root agent. On Windows, a process-tree stop ends jobs; assume an unattended auto-update does this unless your installer is known otherwise.

Do I have to open a port, expose SSH, or set up a VPN?

No. The host agent connects outbound to the hosted relay and works behind firewalls and CGNAT. Commands run with real permissions on your machine, so keep the machine code private and use AI clients you trust.

How many machines can I connect for free?

Free includes up to 10 usable saved machines. Pro costs $49 per month for every saved machine up to the technical ceiling of 100, plus file transfer. If you move to Free, your saved records remain, but only the 10 oldest are usable; deleting one promotes the next.

Put your machines to work.

Install the host agent and connect your first AI client.

Install host agent