How App and CLI fit together
OriginRouter CLI and OriginRouter App are two operation surfaces for the same OriginRouter workflow. The CLI owns execution on the target device, configuration resolution, and automation. The App owns state confirmation, visual management, permission decisions, and cross-device control. Each can be used independently, or they can be combined.
This chapter is a cross-product reference for the App and CLI. It explains concepts shared by both products and does not replace product-specific App or CLI procedures.
Responsibility boundary
| Capability | CLI | App |
|---|---|---|
| Agent execution | Starts and runs Claude Code and Codex | Presents sessions and sends supported control requests |
| Workspace access | Reads and changes authorized directories on the target device | Selects a target device and authorized workspace |
| Providers and routes | Stores configuration, resolves routes, and runs the local proxy when needed | Manages providers, models, routes, and remote sharing while showing the target CLI's actual state |
| Approvals | Evaluates policy and makes the final decision on the execution device | Presents evidence and collects the user's choice |
| Remote connectivity | Provides Local API and account connectivity | Discovers devices and selects a connection path |
| Chat and account | Can use signed-in Cloud routes | Independently provides chat, account, and personal settings |
Choosing the right surface
- Use the CLI for scripts, batch changes, reproducible configuration, and launching Agents directly.
- Use the App to inspect device state, choose models, handle approvals, or control another computer.
- The same setting may be changed from either surface. The target CLI remains authoritative; the App does not create a second configuration.
Why capabilities overlap
Providers, routes, approvals, and agent sessions appear in both CLI and App because they share the target CLI's state, not because they are separate execution systems. App management and control requests are still validated and carried out by the target CLI. Choose the surface by task; do not repeat configuration merely to make it visual.
Documentation ownership
- CLI documentation explains commands, options, configuration, services, and automation.
- App documentation explains interface location, state, operation flow, and result feedback.
- Cross-product concepts are defined once and linked from each product section.