This is the CLI path. Desktop manages its own Yuri host; a phone connects to one. If your goal is simply to use another computer's workspace, start with pairing or SSH.
Identify which process you are managing
| Command | What to inspect |
|---|---|
yuri status | Registered Yuri instances and their ports. |
yuri logs | Startup and runtime messages for the host. |
yuri restart | Restart the CLI-managed Yuri instance. |
yuri stop | Stop that Yuri instance. |
Use --foreground when you want startup output attached to the terminal. The default local OpenCode connection uses a shared service; stopping Yuri does not imply that this shared service was stopped too.
Point at an existing OpenCode service
For an explicitly managed upstream, configure the environment before launch:
OPENCODE_HOST=http://localhost:4096 OPENCODE_SKIP_START=true yuri
The address needs an explicit port and cannot include a path, query or fragment. This chooses the execution service behind the Yuri host—it is not a connection to another Yuri UI. Check startup warnings if the supplied value is rejected.
Arrange unattended startup
Use yuri startup enable, inspect it with yuri startup status, and remove it with yuri startup disable. The startup service can capture the current environment; configure the values you need before enabling it and review --help for the environment-snapshot option.
Use environment settings for targeted overrides. A running host still needs working model credentials and an accessible project directory.