Skip to content

v5.11.23 — OpenCode runtime detection

Latest
Latest

Choose a tag to compare

View all tags
@alexgreensh alexgreensh released this 26 Jun 14:50
v5.11.23
f114cd1

OpenCode reliability fix (#57)

When the Token Optimizer skill was invoked from inside OpenCode on a machine that also has Claude Code installed, it could target ~/.claude instead of OpenCode's own home. This release makes the skill recognize an OpenCode session reliably and bail to the native OpenCode plugin instead of touching ~/.claude.

What changed

  • Runtime detection now reads full process command lines, so OpenCode launched through node/bun is recognized — not just a bare opencode binary. The OpenCode signal is also evaluated ahead of the Claude-environment heuristic, so a coexisting Claude Code install no longer shadows it.
  • The skill resolves its tooling path before the runtime gate runs, so the gate fires as the first step and stops cleanly under OpenCode.
  • Detection is tightened so a Claude Code project merely named opencode is never misdetected.
  • OpenCode install/configure docs corrected: the plugin array takes package-name strings (the previous tuple example could prevent OpenCode from starting). Tuning is via environment variables.

Versions: core 5.11.23; OpenCode plugin token-optimizer-opencode@1.0.14.

Thanks to the community report that surfaced this.

Assets 3
Loading