Install and detect OpenCode
- Open Settings → Code Harnesses → OpenCode.
- If missing, choose Install OpenCode, inspect the command and host, then Download and run it.
- Wait for installation and the detection refresh. For failure, read the error and choose Try again after fixing the cause.
- Use Open install docs or the official OpenCode installation guide for manual recovery. Rudr’s Windows install plan uses global npm; upstream WSL guidance does not prove a WSL-only executable is usable by native Rudr.
- Verify
opencode --versionin a new terminal, fully quit and reopen Rudr, and return to OpenCode settings. The app searches PATH and known locations, rather than arbitrary directories.
Reuse OpenCode-owned access
- Open OpenCode outside Rudr and configure the desired provider using its
/connectflow. Follow the official provider instructions for the exact account or key choices. - Return to Code Harnesses → OpenCode and choose OpenCode as the access route.
- Use Refresh status if offered and inspect the route’s available models.
- Choose Save settings, then select an offered model in a new Code session.
There is no universal Sign in to OpenCode button in Rudr. Provider access can vary by account, organization, and upstream integration.
Use a Rudr-managed route
Configure the matching connection under Settings → Models, save it, then select OpenAI API, Anthropic API, or Foundry in OpenCode access. The interface distinguishes these routes from OpenCode’s ordinary provider configuration. Confirm the route before starting work so the intended account is used.
An empty model list differs from an unverified catalog or a missing CLI. Preserve the displayed error and follow authentication and readiness recovery; repeatedly reinstalling does not repair an account or deployment mismatch.