YuriHandbook

Help

When the interface loads but work cannot start

Separate OpenCode startup failures from model authentication and an incorrect upstream address.

A visible Yuri window proves that the interface loaded. It does not prove that the OpenCode service or selected model is ready.

Read the startup decision

Follow any runtime-installation or compatibility message. For a CLI-managed host, inspect yuri logs; for desktop, use the startup error and retry action. yuri status reports Yuri instances, so do not treat it as proof that OpenCode is healthy.

The default local connection uses a shared background service. Restarting the interface is not the same as upgrading or repairing that service.

Check explicit overrides next

If you set OPENCODE_HOST, confirm its scheme, explicit port and absence of a path, query or fragment. Verify that the service is actually reachable from the Yuri host. Check OPENCODE_SKIP_START and the startup log for rejected configuration before assuming Yuri used your intended endpoint.

If the service is ready

Check the selected provider and model in the session. An expired provider login or a model error is a different problem from service startup. Retry the small read-only request from first use to separate project access from a larger failing task.