Magus Documentation

Magus is a plugin marketplace for Claude Code. It ships on three channels: magus for core development plugins, magus-marketing for content and outreach, and magus-alpha for experimental work.

Start here

bun add -g claudeup
claudeup

That is it. claudeup lists the Magus marketplaces, registers whichever you pick, and installs the plugins along with the MCP servers, binaries, skills and CLI tools they depend on.

Guides

• Installing Magus — claudeup, marketplaces, enabling plugins
• Teams and profiles — one committed manifest, one command per teammate
• Building a feature — /dev:dev, depth, and presets
• Fixing a bug — /dev:fix, reproduced first, reviewed twice
• Designing before you build — /dev:architect and plan mode
• Understanding code — /dev:investigate, read-only
• Documentation — /dev:doc and its four modes
• Isolated worktrees — /dev:worktree with database branching
• multimodel — a blind vote across models, or handing a whole task to one
• code-analysis — asking questions about code you didn't write
• bunjs — one command, and the eight skills behind it
• Advanced Usage — global and project-scoped installs, version pinning, updates, custom configuration
• Troubleshooting — plugins not loading, hooks not firing, missing marketplace, stale caches

What is available

• Plugins — three marketplaces, and what each carries. Follow a plugin's name for its commands, subagents and skills.

Release history

Each channel ships a CHANGELOG.md and RELEASES.md scoped to the plugins you can actually install from it.

---

Writing a plugin rather than using one? That is a separate tutorial and does not live here.