RemoteForge CLI

RemoteForge is designed for a one-command Windows first run:

npx remoteforge

The CLI installs its bundled RemoteForge Agent runtime under %LOCALAPPDATA%\RemoteForge, opens the browser only when sign-in is required, pairs the computer without copy/pasting tokens, stores the device credential with Windows DPAPI, starts the outbound agent, and verifies the relay connection.

Users do not need to clone the GitHub repository, set REMOTEFORGE_HOME, edit .env files, or configure a tunnel.

Commands

npx remoteforge
npx remoteforge start
npx remoteforge stop
npx remoteforge restart
npx remoteforge status
npx remoteforge doctor
npx remoteforge login
npx remoteforge logout
npx remoteforge open
npx remoteforge update
npx remoteforge autostart enable
npx remoteforge autostart disable
npx remoteforge pet status
npx remoteforge pet enable
npx remoteforge pet disable
npx remoteforge pet restart

remote and setup remain accepted for backward compatibility.

Desktop Pet

On Windows, RemoteForge starts a small transparent desktop companion by default. It shows connection and work state (Idle, Connected, Working, Sleeping/Offline), can be dragged anywhere on the desktop, remembers its position, and exposes Dashboard / Resume / Pause / Exit from the system tray. The Pet contains no device credential and reads only local status files. It is launched through a per-user Windows scheduled task using the current interactive user token, so it does not require administrator privileges or an open terminal.

Security

• Device connections are outbound.
• Device credentials are separate from browser/account sessions and are revocable.
• Credentials are encrypted at rest with Windows DPAPI.
• Pairing requests expire, are one-time, and never put permanent credentials in browser query strings.
• Allowed project roots and command-execution policy are enforced by the device agent.