OriginRouter App
OriginRouter App is the desktop and mobile product client. It works independently for chat, account, and personal settings. When connected to OriginRouter CLI, it can also manage local providers, follow agent sessions, handle approvals, and control supported remote work. Use it for workflows that benefit from context, state confirmation, or multi-step management, and combine it with CLI commands when scripting or exact reproduction is preferable.
The App and CLI form the complete workflow entry: the App presents context, confirms state, and sends supported control requests, while local commands, tools, and workspace access remain on the target CLI. When local agent execution, provider management, or cross-device follow-up is required, start with CLI overview and install, then use the App for device and session control as needed. For device connections or sensitive data, see Devices and security, Connection modes, and Data and execution boundaries.
OriginRouter App is currently in internal beta, with capabilities, platform support, and interaction flows opening and evolving progressively during testing. Follow the release notes for the applicable build.
What works without the CLI
- Chat with account-available models using attachments, images, search, and research tasks.
- Manage conversation history, account, subscription, personal memory, notifications, and App preferences.
- Inspect trusted devices, security state, and supported account data.
What a CLI connection adds
- Inspect CLI, proxy, provider, and model-route state on the target computer.
- Add and test providers, discover models, and route Claude Code or Codex.
- Follow active and historical agent sessions, then send input, interrupt, or stop supported sessions.
- Respond to tool calls, structured input, and sensitive-operation approvals.
- Connect to a signed-in, trusted, online CLI from another device.
Platform differences
| Platform | Interface and capability differences |
|---|---|
| macOS, Windows, Linux | Use a desktop split layout and custom dialogs for devices, providers, routes, and agent detail. The CLI still runs on the computer that performs the work. |
| iPhone and Android phones | Use a compact single-column layout and platform-adapted confirmation dialogs. They are suited to remote follow-up, approvals, and QR confirmation for a new device. |
| iPad and Android tablets | Retain touch interaction while showing more context when horizontal space permits. |
| Apple and Google store builds | Subscription purchase and restore use the corresponding store. Available products, price, and restore results come from the active store account. |
Push notifications currently cover iOS, Android, and macOS. Windows and Linux support the main App and CLI workflows, but system push, store purchase, and mobile QR entry points should not be assumed to exist in every build.
Recommended path
Choose an entry point by objective instead of opening every feature page:
- Account chat and personal settings: complete the first App run, then open Chat.
- Run an agent on this computer: follow CLI quickstart, then connect the device in the App and follow its sessions.
- Manage providers, model permissions, or approvals: connect the target CLI, then use Provider Control or Approval policies.
- Run or follow work across devices: read Connect the CLI and Devices and security, enabling the account bridge only when needed.
Commands are always executed by the CLI device running the agent. The App is a control and presentation surface; it does not move local execution into the cloud.