magus-cli 7.14.1 → 7.14.2

package/README.md

@@ -46,9 +46,10 @@ install [profile]           Install a profile's plugins, binaries, skills and
 update [profile]            Bring the ACTIVE profile up to date: install what it
                             declares but this machine lacks, and advance every
                             "latest" pin to the newest published version.
+                            Applies without asking; it only moves forward.
+  --dry-run                 Show the plan and stop; writes nothing, exits 0
   --check                   Report only, write nothing (exits 1 if anything is
                             missing or known to be behind)
-  --yes, -y                 Skip the confirmation prompt
 profile list                Show every profile; ● marks the active one
 profile show <name>         Print a profile's fully resolved closure
 profile switch <name>       Make <name> active: render its settings.json,
@@ -56,8 +57,6 @@ profile switch <name>       Make <name> active: render its settings.json,
 profile init                Write .claude/profiles.json from this project's setup
 doctor [--fix]              Check binary deps, the active profile, conventions
 
-claude [args...]            Check for plugin updates (1h cache), then run claude
-  --force, -f               Force the update check
 upgrade                     Update magus itself
 --version, -v               Version + update check
 --help, -h                  This list
@@ -171,15 +170,16 @@ walks through it end to end, including conflicts and protected branches.
 
 | Screen | What it manages |
 |---|---|
-| Plugins | Install, enable, disable; shows version changes and newly installed plugins |
+| Plugins | Install, uninstall and update at USER, PROJECT or LOCAL scope; shows version changes and newly installed plugins |
 | Skills | Browse and install skills from configured skill repos |
 | MCP | Add MCP servers from a curated catalog |
 | Settings | Claude Code settings, from a catalog of known keys |
-| Profiles | Saved plugin sets (the TUI's own, older profile concept) |
+| Profiles | Switch between this project's profiles, apply a built-in one, rename, delete, copy or import |
 | CLI Tools | Install and update CLI tools via the right package manager; a tool a plugin installs from a release shows as managed by that plugin |
 | Git State | Gitignore conventions and repo hygiene |
 | Alias | Shell alias + flag management for launching `claude` |
 | Styles | Communication style presets, composed into one native output style |
+| Models | Per-subagent model routing presets (`magus models`) |
 
 Navigate with `↑/↓` or `j/k`, `Enter` to select, `r` to refresh, `?` for help,
 `q`/`Escape` to go back. Number keys `1`–`9` jump straight to a screen.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "magus-cli",
-  "version": "7.14.1",
+  "version": "7.14.2",
   "description": "TUI tool for managing Claude Code plugins, MCPs, and configuration",
   "type": "module",
   "main": "src/main.tsx",
@@ -65,8 +65,8 @@
     "typescript": "^5.6.3"
   },
   "optionalDependencies": {
-    "magus-cli-darwin-arm64": "7.14.1",
-    "magus-cli-darwin-x64": "7.14.1",
-    "magus-cli-linux-x64": "7.14.1"
+    "magus-cli-darwin-arm64": "7.14.2",
+    "magus-cli-darwin-x64": "7.14.2",
+    "magus-cli-linux-x64": "7.14.2"
   }
 }

package/src/cli/router.ts

@@ -305,7 +305,8 @@ Usage: magus                    Open the interactive TUI
 Options:
   -v, --version  Show version and check for updates
   -h, --help     Show this help message
-  --no-refresh   Skip auto-refresh of marketplaces on startup
+  --no-refresh   Skip adding, at startup, marketplaces this project uses
+                 but this machine lacks
   --theme light|dark   Force the palette. Otherwise: MAGUS_THEME, then
                        TERM_THEME, then a 250 ms terminal query, then COLORFGBG,
                        then dark. Only the exact words "light"/"dark" count.
@@ -373,9 +374,9 @@ Other commands:
   upgrade            Update magus ITSELF to the latest version
 
 Navigation (TUI):
-  [1] Plugins    [4] Settings   [7] Git State
+  [1] Plugins    [4] Settings   [7] Git State   [0] Models
   [2] Skills     [5] Profiles   [8] Alias
-  [3] MCP        [6] CLI Tools
+  [3] MCP        [6] CLI Tools  [9] Styles
 
 Keys:
   ↑/↓ or j/k     Navigate

package/src/ui/screens/PluginsScreen.tsx

@@ -789,28 +789,15 @@ export function PluginsScreen() {
 
 	const handleShowTeamConfigHelp = async () => {
 		const helpText =
-			"TEAM CONFIGURATION FOR MARKETPLACES\n\n" +
-			"To configure marketplaces for your entire team:\n\n" +
-			"1. Add to .claude/settings.json (committed to git):\n\n" +
-			"   {\n" +
-			'     "extraKnownMarketplaces": {\n' +
-			'       "company-tools": {\n' +
-			'         "source": {\n' +
-			'           "source": "github",\n' +
-			'           "repo": "your-org/claude-plugins"\n' +
-			"         }\n" +
-			"       }\n" +
-			"     },\n" +
-			'     "enabledPlugins": {\n' +
-			'       "code-formatter@company-tools": true\n' +
-			"     }\n" +
-			"   }\n\n" +
-			"2. Team members get prompted to install when they trust the folder\n\n" +
-			"3. Marketplaces are GLOBAL ONLY (managed by Claude Code)\n" +
-			"   - Not project-specific\n" +
-			"   - All team members share the same marketplace cache\n\n" +
-			"NOTE: Individual plugin enablement is still project-specific.\n" +
-			'Use "Project" scope in magus to enable for the team.';
+			"TEAM CONFIGURATION\n\n" +
+			"To give your whole team the same plugins:\n\n" +
+			"1. Install each plugin at PROJECT scope (p).\n" +
+			"   magus records it in this project's profile, together with\n" +
+			"   where its marketplace lives.\n\n" +
+			"2. Commit .claude/profiles.json.\n\n" +
+			"3. Teammates run magus install (a fresh clone) or magus update.\n" +
+			"   magus adds the marketplaces and installs the plugins.\n\n" +
+			"Your company's own marketplace: magus edit.";
 
 		await modal.message("Team Configuration", helpText);
 	};