Plugins
Write your own plugins to extend opencode.
Plugins allow you to extend opencode by hooking into various events and customizing behavior. You can create plugins to add new features, integrate with external services, or modify opencode’s default behavior.
Create a plugin
A plugin is a JavaScript/TypeScript module that exports one or more plugin functions. Each function receives a context object and returns a hooks object.
Location
Plugins are loaded from:
.opencode/plugin
directory either in your proejct- Or, globally in
~/.config/opencode/plugin
Basic structure
export const MyPlugin = async ({ app, client, $ }) => { console.log("Plugin initialized!")
return { // Hook implementations go here }}
The plugin function receives:
app
: The opencode application instance.client
: An opencode SDK client for interacting with the AI.$
: Bun’s shell API for executing commands.
TypeScript support
For TypeScript plugins, you can import types from the plugin package:
import type { Plugin } from "@opencode-ai/plugin"
export const MyPlugin: Plugin = async ({ app, client, $ }) => { return { // Type-safe hook implementations }}
Examples
Here are some examples of plugins you can use to extend opencode.
Send notifications
Send notifications when certain events occur:
export const NotificationPlugin = async ({ client, $ }) => { return { event: async ({ event }) => { // Send notification on session completion if (event.type === "session.idle") { await $`osascript -e 'display notification "Session completed!" with title "opencode"'` } }, }}
Here osascript
is a command that runs on macOS and sends notifications.
.env protection
Prevent opencode from reading .env
files:
export const EnvProtection = async ({ client, $ }) => { return { tool: { execute: { before: async (input, output) => { if (input.tool === "read" && output.args.filePath.includes(".env")) { throw new Error("Do not read .env files") } } } } }}