zellij-plugin-dev

Build Zellij plugins by writing Rust code compiled to WASM/WASI targets. Implement core hooks—load, update, and render—to handle plugin initialization, state changes, and UI rendering. Use Zellij's plugin API to subscribe to events, execute commands, and manage permissions within the plugin ecosystem.

A Zellij plugin requires three essential hooks: load (initialization), update (event handling and state), and render (UI output). Plugins also need permission declarations, event subscriptions, and integration points for external tools like Docker and Git. The complete structure ensures proper lifecycle management and secure operation.

Yes. Zellij plugins support external integrations through command execution within the plugin lifecycle. You can invoke Docker, Git, and other command-line tools from your plugin's update hook, then process results in the render phase to display integrated workflows.

You need Rust proficiency, knowledge of WebAssembly compilation to WASM/WASI targets, and understanding of the Zellij plugin API. Familiarity with event-driven architecture, permission models, and plugin lifecycle hooks (load, update, render) is essential for building functional plugins.

Build your Rust plugin to a WASM binary, then load it into Zellij using the plugin configuration. Test plugin behavior by triggering events, verifying state updates in the render phase, and confirming external command execution. Iterate on your implementation using Zellij's plugin reload functionality.

Plugin event subscriptions are scoped by the permission model you declare. Plugins can only subscribe to events and execute commands their permissions allow. WASM/WASI sandboxing restricts direct filesystem and network access; communicate with external systems through Zellij's command-execution API instead.