Skip to content

Install ​

Muster has two parts that install together: a deterministic CLI (an npm package) and a Claude Code plugin. The CLI does the routing math; the plugin teaches Claude Code how to drive a run.

Requirements ​

Model work uses the account or subscription of the active Claude Code session. Muster's CLI makes no model calls, so there is no separate model API, hosted runtime, or key to manage.

1. Run the installer ​

sh
npx -y @adnova-group/muster@0.7.1 install

install mutates nothing in your ~/.claude. It only prints the steps it cannot do for you, because registering a plugin is a Claude Code action, not a shell command.

2. Register the plugin ​

Run these inside Claude Code:

sh
/plugin marketplace add Adnova-Group/muster   # register the marketplace
/plugin install muster@muster                 # install the plugin

Muster's glass-box output style ships inside the plugin but is not forced: a session keeps your own style unless you choose otherwise. To use it, open /config, select Output style, and pick Muster. (The old /output-style <name> command was removed from Claude Code in v2.1.91.)

Restart to activate

Plugin install is a Claude Code action, so the running session only picks Muster up after you (re)install it through /plugin. The plugin's agents, its two run-scoped hooks, and the selectable output style become available in your next fresh session (restart or /clear).

Using another runtime?

Codex and Cowork have their own install and enforcement paths. Start with Harness support.

3. Verify ​

Start a new Claude Code session and run:

sh
/muster:plan Add rate limiting to the public API with tests

Muster runs one preflight, writes and checks a plan through the muster:make-plan workflow (Claude Code asks for Workflow consent unless you allow Workflow(muster:make-plan)), then shows the plan and stops for your approval. If you see the plan, you are set.

You can also exercise the CLI directly in a terminal. Every verb is plain Node and prints JSON:

sh
npx -y @adnova-group/muster detect
npx -y @adnova-group/muster capabilities

If the plan does not appear, or /muster:* commands are missing, run npx -y @adnova-group/muster doctor and see Troubleshooting.

What the plugin adds ​

Claude Code exposes all seven modes, including Design and Init.

  • Seven slash-command modes: /muster:plan, /muster:go, /muster:diagnose, /muster:audit, /muster:design, /muster:capture, and /muster:init. Plan and Go call the plugin's Workflow scripts (muster:make-plan, muster:build, muster:backlog); Claude Code asks for Workflow consent per run in manual and accept-edits modes, so add the allow rules Workflow(muster:make-plan), Workflow(muster:build) and Workflow(muster:backlog) to skip the prompt.
  • One run-scoped hook, declared in plugin/hooks/hooks.json and active only while Muster is enabled. It never fires on session start or on a prompt, and nothing nudges you toward a verb: Muster costs nothing in a session that never invokes it. Enforcement follows the run's EXTERNAL effects, not the orchestrator's own in-repo edits.
    • PreToolUse (exec-form node hook, fail-open, matcher ^(Bash|PowerShell|mcp__(?!ccd_turn__(?:update_plan|wrap_up)$).*)$, which skips exactly the two chatty Claude Desktop turn tools mcp__ccd_turn__update_plan and mcp__ccd_turn__wrap_up) enforces the action-class fence: while a run is active and .muster/forbidden-actions lists a class, every payload is classified and a tool call that would perform a run-forbidden send/sign/submit/publish/purchase/delete-remote action is denied, controlled by MUSTER_ACTION_GUARD (deny / warn / off). /muster:go writes .muster/run-active and .muster/forbidden-actions before it builds and removes both at the merge decision; if an interrupted run leaves them behind, the next run overwrites them, or delete them by hand.
  • Built-in agents and skills, vendored from MIT-licensed upstreams plus Muster's own clean-room specialists.

Uninstall ​

Because everything Muster adds lives inside the plugin, removal is mostly a matter of removing the plugin. Muster never writes to your ~/.claude/CLAUDE.md or settings.json, so there is nothing tangled to unpick.

sh
npx -y @adnova-group/muster@0.7.1 uninstall

uninstall prints the steps it cannot do for you, because removing a plugin is a Claude Code action:

sh
/plugin uninstall muster@muster    # remove the plugin (and its style + hooks)
/plugin marketplace remove muster  # remove the marketplace

It also cleans up after older Muster versions: if an older install left a copied style at ~/.claude/output-styles/muster.md, uninstall removes it (and restores the original it had displaced, if there is a .bak). On a current install there is nothing there to remove.

Everything leaves with the plugin

The output style and both hooks are plugin-native, so uninstalling the plugin removes them automatically. If you had picked the Muster style, pick another under /config. There is no global file or CLAUDE.md block to clean up by hand.

Next: the Quickstart.

Released under the Apache-2.0 License.