OpenCode SDK Development

Create a custom OpenCode tool by defining it with the tool(...) pattern, specifying parameters via Zod-based tool.schema validation, and implementing the tool logic. Place your tool definition in `.opencode/tool/` or `~/.config/opencode/tool/`, then initialize it using createOpencode for local or global discovery.

The OpenCode SDK plugin system provides hooks for extending functionality: tool (define tools), event, config, chat.message, chat.params, permission.ask, and tool.execute.before/after hooks. Use these hooks in your plugin to intercept and customize tool behavior, validation, and execution within your OpenCode workflow.

Yes. The OpenCode SDK supports client/server initialization via createOpencode and createOpencodeClient, enabling you to wire interactions for sessions, files, and tool execution. This allows your custom tools to work across distributed OpenCode environments with full session and file management.

Yes, argument validation is built into OpenCode tools via tool.schema using Zod-based schema definitions. Define your tool's expected parameters as a Zod schema within tool.schema to automatically validate inputs before execution, ensuring type safety and consistent tool behavior.

Use @opencode-ai/sdk for the core SDK client/server functionality and @opencode-ai/plugin for building plugin hooks and custom tool definitions. Both packages provide the APIs needed to create, validate, and integrate custom tools into your OpenCode environment.

Yes, OpenCode SDK supports both local and global tool development workflows. Configure your tool definitions in `.opencode/tool/` for local scope or `~/.config/opencode/tool/` for global scope, then use createOpencode or createOpencodeClient for discovery based on your deployment target.