← ClaudeAtlas

opencode-server-runtimelisted

Use when an opencode job hangs, the broker will not start, a port is stuck, or job state looks wrong.
rivaldofwijaya/opencode-plugin-cc · ★ 0 · Code & Development · score 65
Install: claude install-skill rivaldofwijaya/opencode-plugin-cc
The plugin uses a small broker around `opencode serve`. It spawns one broker per shared endpoint using the lockfile `lock` and records the endpoint in the portfile `port.json` under `${XDG_STATE_HOME:-$HOME/.local/state}/opencode-plugin-cc/broker/`. References are tracked for Claude Code sessions and job workers. The broker is shut down when the last live reference releases it. A job you cannot see is not the same as a job that has died. Job records are namespaced by Claude Code session ID, so answer the session question before anything else: - **Wrong session.** Another Claude Code window's jobs are invisible here by design. Run `status`, `result`, or `cancel` from the session that started the job. Repair does not make a live job in another session visible, and must not be used to try. - **Right session, job still running.** `status` reports it, and a dropped SSE stream is not the end of it — the worker keeps persisting events and the result to disk. Wait, or fetch the result. - **Right session, owner probably gone.** `status` cannot tell this case apart from the one above by itself — it prints the job's last-known state, not a live pid check, so a job with a dead owner still shows `running` until something re-verifies it — that re-check also runs automatically on the next Claude Code session start in any window, so a job may already show `stale` by the time you look, but you cannot assume it has. Suspect this case by circumstance instead: the session (or m