@dosu/cli 0.60.0 → 0.60.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/README.md +2 -2
  2. package/bin/dosu.js +650 -621
  3. package/package.json +1 -1
package/README.md CHANGED
@@ -96,7 +96,7 @@ Or right-click the binary, select "Open", and click "Open" in the dialog.
96
96
  | `dosu login` | Authenticate with Dosu via browser OAuth |
97
97
  | `dosu logout` | Clear saved credentials |
98
98
  | `dosu status [--json]` | Show current authentication and MCP status |
99
- | `dosu upgrade` | Update Dosu through the package manager that installed it, then re-run `dosu setup` on the new version |
99
+ | `dosu upgrade` | Update Dosu through the package manager that installed it, re-running `dosu setup` when the update changes agent config |
100
100
  | `dosu mcp list` | List supported AI tools |
101
101
  | `dosu mcp add <tool>` | Add the Dosu MCP server to a specific tool |
102
102
  | `dosu mcp refresh` | Rewrite the Dosu MCP entry in every already-configured tool from the current setup |
@@ -105,7 +105,7 @@ Or right-click the binary, select "Open", and click "Open" in the dialog.
105
105
 
106
106
  `dosu mcp add` takes `-g, --global` to install for all projects instead of project-local, and `--show-secret` to print the full manual config.
107
107
 
108
- `dosu upgrade` delegates to npm, pnpm, Yarn Classic, or Homebrew only after confirming which manager owns the current installation. Temporary package-runner invocations stay ephemeral, ambiguous or local installs are left unchanged, and standalone binaries receive the latest safe manual download path. After a successful update it re-invokes the new version to run `dosu setup`, so every configured tool gets the current MCP entry, hooks, status line, rules, and skill; without a TTY it runs the non-interactive `dosu mcp refresh` instead. Upgrades done outside `dosu upgrade` (npm, brew, `npx @dosu/cli@latest`) get a safety net: when the new version changed the shape of the MCP entry, the first command on it silently rewrites configured tools' MCP entries and prompts you to run `dosu setup` for the rest; the bundled agent skills are always re-applied on the first command after any version change.
108
+ `dosu upgrade` delegates to npm, pnpm, Yarn Classic, or Homebrew only after confirming which manager owns the current installation. Temporary package-runner invocations stay ephemeral, ambiguous or local installs are left unchanged, and standalone binaries receive the latest safe manual download path. After a successful update it hands off to the new version, which re-applies the bundled skills and, only if the update crossed a release that changed the agent config format, runs `dosu setup` (or the non-interactive `dosu mcp refresh` without a TTY). Upgrades done outside `dosu upgrade` (npm, brew, `npx @dosu/cli@latest`) get a safety net: when the new version changed the shape of the MCP entry, the first command on it silently rewrites configured tools' MCP entries and prompts you to run `dosu setup` for the rest; the bundled agent skills are always re-applied on the first command after any version change.
109
109
 
110
110
  ### Platform commands
111
111