Plugins

Nexrall Code (VS Code and CLI) supports installable plugins — bundles of commands, agents, and hooks that extend the agent's behavior for a specific project or workflow.

What a plugin can contain

A plugin lives in .nexrall/plugins/<name>/ and can define:

• Commands — custom slash commands available in a session.
• Agents — named sub-agent personas with a scoped tool set (similar to the built-in /review reviewer agent).
• Hooks — scripts that run at specific points in the agent loop (for example, after every file write).

Installing a plugin

nex plugin install owner/repo
nex plugin install owner/repo#branch/subdir
nex plugin install https://github.com/owner/repo
nex plugin install ./local/path

Plugins that define hooks or MCP connections require an explicit confirmation before install — this can't be bypassed even with --yes, since hooks can run arbitrary code as part of your agent sessions.

Searching the registry

nex plugin search <name>
nex plugin info <name>

Precedence

When a command or agent name exists in more than one place, Nexrall resolves it in this order: project-level → global (user) → plugin → built-in.

Listing installed plugins

nex plugins

or the /plugins slash command inside a session.

Writing your own plugin

A minimal plugin only needs a plugin.json manifest plus a commands/ folder with one or more command files — no hooks or MCP config required unless you need them. Start from an existing plugin's structure as a template if you're building your first one.