Support

Application: Agent Commander

Contact: agentcmd@sframework.com

Agent Commander lets you drive the coding agent on your computer from your phone. You type a request on your device; a server you run yourself executes the assistant against your own project directory and streams the result back.

There is no account to create and no publisher-operated server holding your work. That shapes every answer below.

Install the server on your own machine

The server is a Go binary and a SQLite file that run on the very computer you already code on — we operate no server. It runs on macOS (Apple Silicon and Intel), Linux (amd64 and arm64), Windows 11 (x64) and WSL.

You need first: the Claude Code CLI or the Codex CLI, installed and signed in — either one is enough. Without both the installer stops before downloading anything and prints how to install them. Antigravity is an experimental option: install and sign in to its CLI on the same computer. For Claude Code on Windows it must be the native claude.exe — the npm claude.cmd shim cannot be used, because the server starts the CLI directly rather than through a shell.

• Step 1 — Run one command. On macOS, Linux or WSL, open a terminal and paste: curl -fsSL https://github.com/phidinhtho/agentcmd-release/releases/latest/download/install.sh | bash — on Windows 11, open PowerShell and paste: irm https://github.com/phidinhtho/agentcmd-release/releases/latest/download/install.ps1 | iex instead. Either script detects the right package for your machine, verifies the release checksum, puts agentcmd where your account can run it (~/.local/bin on macOS and Linux, %LOCALAPPDATA%\Programs\agentcmd on Windows), installs the companion desktop app — menu bar on macOS, system tray on Windows — and hands over to setup. No administrator rights, nothing written outside your own user folder.
• Step 2 — Let setup finish. It writes an environment file only you can read, creates the data directory and a migrated database, generates the TLS key and certificate the app will pin, installs and starts the background service, and ends with a pairing QR code valid for ten minutes.
• Step 3 — Scan it with your phone. Open Agent Commander, tap Connect, and scan that QR code. The app records your server's certificate fingerprint at that moment and refuses to talk to anything that does not match it later.
• Linux and WSL only. On Linux, setup prints sudo loginctl enable-linger for you to run yourself — without it the service stops when you log out. On WSL, enable systemd before installing.
• Windows only. Two things the installer cannot do for you. The background service is a Task Scheduler task that starts when you sign in, so it runs while you are signed in and stops when you sign out. And because a windowless service never triggers the usual firewall prompt, setup prints one netsh advfirewall line to run once in a PowerShell window opened with Run as administrator — skip it and phones on your local network simply cannot reach the server. Installing Git for Windows is also worth doing: the CLI's Bash tool needs it.
• QR code expired? Run agentcmd auth show on the server: it prints the suggested address, the pairing code, the TLS fingerprint, and a fresh QR code.

Afterwards, agentcmd status tells you whether the service is alive, agentcmd doctor re-checks the install, and agentcmd update fetches a new build, verifies its checksum and restarts the service in place. If the target machine has no network, download the package for it and manifest.json from the releases page, copy them over, and run ./install.sh --from with the package name — on Windows, the package is a .zip and the command is .\install.ps1 -From with the package name.

Frequently asked questions

• Pairing fails, or the app says the server certificate does not match. Your server is presenting a different certificate than the one the app pinned when you first paired — normally because the server was reinstalled or its certificate was rotated. Open Settings, unpair, then pair again with a fresh code.
• I am not receiving notifications. Three things must all be true: notifications are turned on in the app's Settings, your operating system has granted the app notification permission, and your server has the notification relay address configured. On iOS also check Settings, then Notifications, then Agent Commander. Notifications are only sent while the app has no live connection to your server — if the app is open and connected, results appear in it directly instead.
• Where is my data? On the machine running the server, inside its data directory (by default a folder named agentcmd-engine in your home directory). Nothing is stored on a publisher server. See how to delete your data.
• Can I use the web version instead of the app? No. This website serves these public pages only. A browser cannot pin a self-signed server certificate the way the mobile app does, so the web build cannot pair with your server.

Contact

Write to agentcmd@sframework.com. This is a small project with no ticket system and no web form to fill in — the server runs on your own machine, so there is nobody on the other end holding your data.

It helps to include your app version (Settings, then About), your phone's operating system version, and what you were doing when the problem appeared. Please do not send your server address, your pairing code, or conversation content.

See also: Privacy Policy and Terms of Service.