Repository navigation
Plugin console.log/warn/error output corrupts TUI display #19108
Description
Bug
Plugins loaded via opencode.json "plugin" array run in the same Bun process as OpenCode. When plugins (or their dependencies) call console.log, console.warn, or console.error, the output goes directly to stdout/stderr, corrupting the TUI display.
The logLevel config option only controls OpenCode's own slog-based logging — it has no effect on plugin console output.
Affected plugins (examples)
@rehydra/opencode— its dependencyrehydracallsconsole.warn("Validation warnings:", ...)on every anonymization pass (upstream issue)- Custom
.opencode/plugins/*.js— any plugin usingconsole.logfor debugging spams the TUI
Screenshot
Raw { c, Validation warnings:, and [memorix] hook fired: lines mixed into the TUI output, making it unreadable.
Expected behavior
Plugin console.* output should either:
- Be intercepted and routed through OpenCode's structured
Logsystem (respectinglogLevel) - Be suppressed by default with an opt-in
pluginLogLevelconfig - Be redirected to a log file rather than stdout
Root cause
In packages/opencode/src/plugin/index.ts, plugins are loaded via import(plugin) and their init functions are called directly. There's no console interception — plugins share the global console object with the TUI process.
Suggested fix
Wrap plugin initialization and hook execution with a console override that routes through the Log system:
function withPluginConsole<T>(pluginName: string, fn: () => T): T {
const original = { ...console }
const pluginLog = Log.create({ service: `plugin:${pluginName}` })
console.log = (...args) => pluginLog.info(args.map(String).join(" "))
console.warn = (...args) => pluginLog.warn(args.map(String).join(" "))
console.error = (...args) => pluginLog.error(args.map(String).join(" "))
try {
return fn()
} finally {
Object.assign(console, original)
}
}This keeps plugin logging visible in OpenCode's log system while preventing stdout corruption.
Environment
- OpenCode 1.3.0
- macOS 15.5
- Bun 1.2.x
Activity
github-actions commentedon Mar 25, 2026
This issue might be a duplicate of existing issues. Please check:
packages/opencode/src/plugin/index.ts), and overlapping proposed fixes (proper logging for plugins). Please review whether your issue is already covered there or if this is a distinct case worth keeping separate.If you believe this is a distinct issue, please clarify the difference in a comment.
RaviTharuma commentedon Mar 25, 2026
This is related to #12931 but distinct in scope:
#12931 covers:
eventhandler errors not being caught (missingawait+ try-catch)logproperty onPluginInputThis issue (#19108) covers:
console.log/warn/errorcalls from normal plugin operation (not errors) corrupting the TUIconsole.*(e.g.rehydra's anonymizer callingconsole.warnon every pass)logLevelconfig having no effect on plugin console outputThe root cause is the same (plugins share the global
consolewith the TUI process), but the fix in #12931 (adding error handling +logtoPluginInput) wouldn't solve this issue — even if plugins themselves use structured logging, their dependencies (npm packages) will still useconsole.*and corrupt the display.The fix in PR #19109 addresses both issues by intercepting
consoleglobally before plugins load, routing everything through theLogsystem. This catches both plugin code and their transitive dependencies.Happy to coordinate with @rekram1-node on merging both fixes if needed.
github-actions commentedon Jul 5, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.