OriginRouter AppConnect the CLI

Connect OriginRouter CLI

The App connects to the CLI through local direct, LAN or custom direct, and account bridge paths. Multiple paths may coexist; the App merges paths that report the same stable device ID.

All three paths require device-identity verification. The account bridge authenticates and delivers ciphertext; it does not grant additional workspace or command permissions. See Connection modes and Devices and security for connection and encryption boundaries.

Local direct

Use this path when the desktop App controls the same computer. An account sign-in is not required.

First installation

If the CLI is not installed, complete the installation and originrouter setup in CLI overview and install.

Existing installation

For an existing installation, verify that the service is running.

originrouter service status
originrouter local config show
originrouter local key show

The desktop App tries 127.0.0.1:7437 by default. If the service is online but the App cannot connect, verify the Local API port and device key.

Run these checks in order: confirm the service is running, inspect the Local API address and port, then inspect the local device key.

LAN or custom address

After confirming that the target network is trusted, enable LAN access on the target CLI:

originrouter local config set --bind 0.0.0.0 --allow-lan on
originrouter service restart

Run these commands in order: enable LAN access, then restart the service to apply the setting.

Then add the target IP or domain and port in the App. The App connects and verifies the stable device ID. An unverified address is never silently merged into an existing device.

Account bridge

Use this from a phone, across networks, or when the target has no directly reachable address:

originrouter login
originrouter remote setup
originrouter service status

Run these commands in order: sign in, register remote capability, then confirm the service status.

Target CLI

The target CLI should already have completed originrouter setup from CLI overview and install.

Before connecting

The App and CLI use the same account.
The target CLI is online and present in the trusted-device directory.
The models to share are enabled for remote use in Provider Control before remote setup.

Bridge responsibilities

The bridge authenticates, routes, and delivers ciphertext. It does not execute commands or evaluate approval policy for the CLI.

Success checks

The App presents one merged target device instead of duplicate local and account devices.
Device details show the CLI version and at least one usable connection path.
Provider Control can load a snapshot from the target device.
Agent Control can load active or historical sessions for the device.