OpenCode adapter for the shared polycli companion.
opencode plugin @bbingz/polycli-opencodeThis host ships as:
- npm package:
@bbingz/polycli-opencode - plugin entrypoint:
index.mjs - bundled companion:
scripts/polycli-companion.bundle.mjs
In this repository there is also a local project entrypoint at .opencode/plugins/polycli.mjs for repo-local development.
polycli_runpolycli_timing
Both tools execute the bundled companion. polycli_run is the general entrypoint; polycli_timing is a narrow convenience wrapper.
Run polycli_run with:
{"argv":["health","--json"]}Then either:
- call
polycli_timingwith{"provider":"qwen","history":1,"json":true} - or call
polycli_runwith{"argv":["timing","--provider","qwen","--history","1","--json"]}
polycli_run accepts the same subcommands as the other hosts:
agent-contextsetuphealthaskrescuereviewadversarial-reviewstatusresultcanceltimingdebugsessions
Operational commands retain legacy --json as the host default and offer opt-in --json-v2 envelopes. Job commands accept --job id:<id>|prefix:<prefix>|latest|latest-active|latest-terminal; status --wait --for <state> is typed. Incremental redacted observation uses polycli_run({"argv":["debug","tail","--after","evt_abc","--limit","100","--wait","--json-v2"]}).
--provideris still required on prompt-bearing commands.healthis the canonical end-to-end provider check after install, login, or provider config changes. With no provider it probes every integrated provider and reportshealthyProviders; use--provideronly for single-provider diagnosis. Do not runsetuporhealthbefore every normal provider call.setupseparates package/plugin problems from provider CLI problems with install and status-only auth checks. It skips model-based auth probes unless itsargvexplicitly includes--probe-auth.minimaxandcmdare currently the integrated providers without session resume support.cmduses documented Command Code headless mode, where each invocation is a standalone session.