plugin-logging

Replace ad-hoc console.log calls with the client.app.log interface to emit structured logs in OpenCode plugins. This routing standardizes logging by capturing initialization, operation, and error events with consistent metadata fields.

The client.app.log interface supports structured logging fields including service, level, message, and extra. These fields ensure consistent reporting and enable filterable observability across different plugin events.

Use structured logs during plugin development and debugging workflows when initialization, operation, and error events must be captured with metadata. This standardized approach provides better filtering and observability than direct console output for production diagnostics.

OpenCode plugin logging requires access to the client.app.log interface within the plugin runtime. No additional dependencies are needed, as the skill standardizes logging by leveraging this built-in client application pathway.

Yes, you can filter OpenCode plugin logs by service and level. The client.app.log interface emits structured fields for each event, enabling consistent, filterable observability across your plugin's initialization and error handling workflows.

The best way to standardize logging across OpenCode plugins is routing all log events through the client.app.log interface. This unified pathway replaces ad-hoc console output, ensuring consistent instrumentation and structured metadata for production diagnostics.