opencode-plugin-compliance

OpenCode plugin compliance is enforced by validating that plugins export a Plugin function, adhere to predefined extension points, and avoid direct core state mutation. This SDK-driven approach ensures predictable behavior across the full plugin lifecycle.

OpenCode plugin permission handling requires plugins to use the official SDK for interactions and automate permission decisions without directly manipulating file system storage. Plugins must observe read-only event access and respect strict storage boundaries to maintain platform security.

Event subscriptions and tool interception in OpenCode plugins let you observe and influence lifecycle events at predefined hooks. Plugins must export a Plugin function wiring these hooks, ensuring read-only event access without directly mutating core state.

OpenCode plugin validation fails when plugins lack explicit export shapes, attempt direct storage manipulation, or bypass SDK-driven logging. Compliance requires adhering to hook definitions, avoiding direct file system manipulation, and following official interaction patterns across the lifecycle.

Yes, OpenCode plugin compliance requires using the official SDK for logging and interactions. Plugins must adhere to SDK-driven patterns and storage access rules to prevent direct file system manipulation and ensure safe, predictable platform behavior.