Use the OpenCode logger instead of the console

[JCHacking]

What problem are you trying to solve?

To improve log filtering and centralize the logs, it would be better to switch to the logger provided by OpenCode instead of writing to the console.

Proposed solution

Use the OpenCode logger instead of the console logger

Alternatives considered

No response

Scope check

• My request is related to LiteLLM model discovery, configuration, or routing

[dluhhbiu]

This isn't just about logging quality — console logging breaks the TUI. The plugin logs straight to stdout, and the TUI renders in the same terminal. When a new session is created, a background cache refresh kicks in and prints this over the interface:
[opencode-litellm] Discovered 19 models for provider "litellm" from ...
[opencode-litellm] Background-refreshed model cache for ...
The UI gets messed up after that. Reproduces almost always when the cache is older than 5 min. So I'd suggest switching to client.app.log() — the client is already available in PluginInput.

[yuseferi]

Agreed — and the TUI corruption you describe makes this a bug, not just a nicety. Fixed in #26: all plugin logging now goes through client.app.log() (service opencode-litellm) so entries land in OpenCode's log files instead of being printed into the TUI's terminal. Falls back to the console only when no client is wired up (unit tests / unusual embedders).

[yuseferi]

Shipped in v1.0.1 via #26 — thanks for reporting the TUI corruption, @dluhhbiu, and for pointing us at client.app.log(). All plugin output now lands in OpenCode's log files; the TUI should stay clean even with frequent background refreshes.