Skip to content

v5.10.2 — OpenCode-aware: runs on OpenCode's own config, not ~/.claude

Latest
Latest

Choose a tag to compare

View all tags
@alexgreensh alexgreensh released this 07 Jun 18:05
v5.10.2
fc5929e

OpenCode parity

Running on a host with both Claude Code and OpenCode? OpenCode loads ~/.claude/skills by default, so it can invoke the Token Optimizer skill while you are working in OpenCode. Token Optimizer now recognizes the OpenCode runtime and operates on OpenCode's own directories instead of ~/.claude.

  • Runtime-aware detection — OpenCode is detected automatically (env signals, process context, and a marker the OpenCode plugin injects into every shell). Claude Code, Codex, and Hermes detection are unchanged.
  • Right home, every time — Token Optimizer's data resolves to ~/.local/share/opencode, never ~/.claude.
  • Clear handoff — under OpenCode, the audit points you to the native OpenCode plugin (live quality, savings, and continuity tracking via the token_dashboard / token_status tools).
  • OpenCode plugin bumped to 1.0.8 with the runtime marker hook.

Set TOKEN_OPTIMIZER_RUNTIME=claude to force a Claude Code audit from anywhere.

Closes #57.

Assets 3
Loading