Extend Wuu

Choose an extension mechanism for the behavior you need. A reusable task procedure can be a skill; an existing tool service can connect through MCP. Use a plugin when you need managed code, host services, or desktop UI.

Goal	Start here
Reuse a task workflow	Skills and skill authoring
Connect a local or remote tool server	MCP
Run checks around lifecycle events	Hooks
Install packaged agent or desktop behavior	Wuu plugins
Choose a theme or configure a plugin	Themes and settings
Keep durable information	Memory and optional Dream
Predict an optional next message	Next-message suggestions

Skills add instructions and resources. MCP exposes tools from another process or service. Hooks run commands or model checks at supported events. A plugin can combine these contributions with agent code, desktop code, themes, and settings under one package lifecycle.

Build an extension

Start with the agent plugin quickstart for model-visible tools or runtime behavior, or the desktop plugin quickstart for interface contributions. The desktop extension guide explains the available UI boundaries, with practical examples in recipes.

Use the plugin development practices for guidance on composing, operating, and checking plugins. The authoring reference covers package fields and APIs, and the system architecture explains loading, lifecycle, and compatibility boundaries. You do not need to read the architecture reference before writing a local extension.

Understand the trust involved

A skill can influence tool use even though it is text. MCP services and hooks can execute code or send data elsewhere. Agent plugins run in managed processes, and desktop plugins run trusted code in the renderer. Wuu does not sandbox or certify installed extensions.

Agent permission modes apply to supported tool execution paths, not to all arbitrary code you install. Review the source and data access of an extension before using it; see the security model.