opencode

Diagnose and operate the OpenCode CLI coding agent across local vLLM backends.

6|1|Updated May 11, 2026
One-click install
npx skills add https://github.com/yakeworld/Synthos --skill opencode-yakeworld
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: opencode
Source: https://github.com/yakeworld/Synthos/tree/main/skills/extended/external-automation/automation-skills/autonomous-ai-agents/opencode
Command: npx skills add https://github.com/yakeworld/Synthos --skill opencode-yakeworld

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires opencode-ai, and includes references (resource) components.

What problem does it solve? It prevents misdiagnosis of the OpenCode CLI by codifying its non-daemon behavior, installation layout, configuration structure, and backend connectivity checks into a repeatable diagnostic workflow. ## Core Features & Use Cases - Five-Step Diagnostics: Sequentially checks process state, installation, config file, backend node connectivity, and usage history. - Fault Localization: Distinguishes OpenCode installation issues from backend failures (Tailscale drops, stopped vLLM containers) with concrete fix steps. - Use Case: When a user reports OpenCode is broken, run the diagnostic flow to confirm that no running process is normal, verify opencode --version, validate ~/.config/opencode/opencode.json, and probe all three vLLM nodes with nc -zv. ## Quick Start Ask the agent to run the OpenCode diagnostic to verify installation, configuration, and backend node connectivity.

Frequently Asked Questions about opencode

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose OpenCode CLI when it seems broken?

Run the five-step diagnostic: check processes with ps aux, verify installation with opencode --version, validate ~/.config/opencode/opencode.json, test backend nodes with nc -zv, and review prompt-history.jsonl. No running process is normal since OpenCode is not a daemon.

What is the difference between OpenCode and Codex CLI?

OpenCode uses the OpenAI-compatible chat/completions API and suits lightweight one-off scripts, while Codex CLI uses the Responses API and is the primary agent for complex coding tasks. Their APIs are not interchangeable.

Why does opencode doctor or opencode health fail?

OpenCode has no doctor, health, or version subcommands. Unknown subcommands are interpreted as directory paths, producing a 'Failed to change directory' error. Use valid subcommands like models, providers, run, or resume.

How do I check or upgrade the OpenCode version?

Run opencode --version to check the installed version and npm update -g opencode-ai to upgrade. The package is not in the public npm index, so npm search will not find it; no update output means you are on the latest version.

Why is an OpenCode backend node unreachable?

Backend unreachability usually means the Tailscale connection dropped or the vLLM container on that node stopped. Check tailscale status and verify the vLLM container with docker ps on the affected node; this is an infrastructure issue, not an OpenCode fault.