Install plugins

Add reusable resources to your CLIO Coder installation.

Install a bundle of resources

Plugins keep related skills, prompts, agents, playbooks, and supporting files together. Browse the shipped catalog and preview an installation before writing it:

clio-coder library list --kind plugin
clio-coder library install plugin:materio --dry-run
clio-coder library install plugin:materio

The catalog ships with CLIO Coder, but its content is not installed automatically. Add --project to keep a package in the current workspace; otherwise installation uses user scope.

Project packages load only in a workspace you have approved. Your own first project install approves it. After that, a change to the project's package set, including one that arrives with a clone or a pull, stays listed but unloaded until you review it with clio-coder config trust plugins and run the approval command it prints.

A local bundle uses the same review flow:

clio-coder library install ./my-plugin --project

Keep the installed copy under control

clio-coder library inspect materio --json
clio-coder library drift materio
clio-coder library disable materio
clio-coder library enable materio

Installation records a verified pin covering the complete package tree. Drifted content is blocked from loading; pin verifies the recorded pin rather than approving edits. Review an update before replacing a modified copy.

In the terminal, open Library → Plugins to browse members and review lifecycle actions. Run /reload library after changing recipes externally.

Choose the right kind of extension

A plugin carries content. An extension is code that runs in its own process, declares everything it may do, and loads only after you approve those capabilities; manage it with clio-coder extensions. The runtime is sandboxed where the host has a backend. Project extensions also need clio-coder config trust extensions. See the extension tutorial. Adding tool schemas requires a new session; recipe reload does not change those schemas.

See skills and resources for everyday Library controls. The full plugin guide covers private catalogs and package authoring.

Related tutorials