opencode-plugin-dev

OpenCode plugin development requires a canonical entry point that accepts a context and returns a hooks map, backed by a root SKILL.md file. This pattern standardizes wiring for tool, session, file, and server event hooks.

OpenCode extensions can hook into tool, session, file, and server lifecycles. This allows you to intercept and modify behavior across different stages of the OpenCode event system.

You can scaffold an OpenCode plugin by creating a root SKILL.md with name and description, then installing it in a local project to start testing within a development sandbox environment.

TypeScript is used for OpenCode plugin development to enforce standardized export patterns and hooks. It ensures type safety when defining the context and hooks map for the plugin entry point.

OpenCode plugins support optional resource directories including scripts, references, and assets. These directories allow you to organize extended guidance and supplementary files alongside the root SKILL.md.

You should use a standardized export pattern when extending OpenCode behavior to manage complexity and ensure safety. It provides a consistent structure for lifecycle management and event hook integration.