creating-opencode-plugins

Event-driven plugins intercept and respond to 25+ OpenCode events like file edits, command execution, and LSP diagnostics. Export an async function from a JavaScript/TypeScript module that receives a context object and returns an event handler routing on event.type, paired with a manifest describing supported hooks and events.

Yes. Build a plugin that hooks into file.edited and read/share operations to monitor and block access to sensitive files, then emit warnings when .env or credential files are modified, enforcing security policies at the event layer.

Plugins can intercept file operations, command executions, LSP diagnostics, permission requests, session lifecycle events, tool registrations, and TUI interactions. Each event type (file.edited, permission.replied, command.executed, lsp.client.diagnostics, tool.execute.before/after) routes through the handler for validation, logging, or custom policy enforcement.

No. Plugins are JavaScript/TypeScript modules exporting an async function; you can write in either language. TypeScript provides type safety for the context object and event handler, but plain JavaScript works equally well.

Plugins hook into command, file, and permission events to validate, log, and enforce policies before execution. Use event handlers to detect risky operations, prevent credential leaks, and send warnings, creating a validation layer across the development lifecycle.

Plugins require only a manifest file describing hooks and supported events, plus a JavaScript/TypeScript module. No external dependencies are mandated; the plugin receives a context object providing project, client, directory, and worktree access for event handling.