@dosu/cli 0.43.0 → 0.45.0

package/README.md

@@ -96,12 +96,16 @@ Or right-click the binary, select "Open", and click "Open" in the dialog.
 | `dosu login` | Authenticate with Dosu via browser OAuth |
 | `dosu logout` | Clear saved credentials |
 | `dosu status [--json]` | Show current authentication and MCP status |
+| `dosu upgrade` | Update Dosu through the package manager that installed it |
 | `dosu mcp list` | List supported AI tools |
 | `dosu mcp add <tool>` | Add the Dosu MCP server to a specific tool |
 | `dosu logs` | View or manage debug logs (`--tail`, `--clear`) |
+| `dosu telemetry` | Manage usage analytics and error diagnostics (`status`, `enable`, `disable`, `reset`) |
 
 `dosu mcp add` takes `-g, --global` to install for all projects instead of project-local, and `--show-secret` to print the full manual config.
 
+`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.
+
 ### Platform commands
 
 Once authenticated against a deployment, you can drive the Dosu platform without leaving the terminal:
@@ -160,6 +164,30 @@ dosu setup --agent --tool claude
 
 Combine with `dosu login --request` / `--check <ticket>` for human-in-the-loop authentication, and `--mode oss|cloud` to skip the mode prompt.
 
+### Telemetry and privacy
+
+Dosu collects privacy-preserving usage analytics and error diagnostics by default. One global switch
+controls both; setup does not show a telemetry prompt.
+
+```bash
+dosu telemetry status [--json]
+dosu telemetry enable
+dosu telemetry disable
+dosu telemetry reset
+```
+
+`reset` rotates the local pseudonymous telemetry ID; it does not delete already retained events.
+Signed-out command analytics uses that ID. Signed-in command analytics and minimal error diagnostics
+use the same Dosu user ID as the web app; Sentry may also receive the account email. Prior
+installation history is never aliased to an account. Setup-funnel events are linked after sign-in
+and may include documented coarse setup choices. `DO_NOT_TRACK=1` and
+`DOSU_TELEMETRY_DISABLED=1` disable all telemetry for the process. Dosu never collects
+prompts, raw command lines, free-form argument or option values, user source code, file contents,
+local paths, raw environment-variable names or values, credentials, raw error messages, or
+`debug.log`. See
+[Telemetry and privacy](docs/telemetry.md) for the exact event fields, destinations, retention, and
+controls.
+
 ## Configuration
 
 Credentials and the selected deployment live in `~/.config/dosu-cli/config.json`. Set `DOSU_DEV=true` to isolate config under `~/.config/dosu-cli-dev/`.
@@ -171,6 +199,16 @@ To repoint a published build at a different backend without rebuilding, set any
 - `SUPABASE_URL_OVERRIDE`
 - `SUPABASE_ANON_KEY_OVERRIDE`
 
+Telemetry destination settings are:
+
+- Build time: `DOSU_POSTHOG_PROJECT_TOKEN`, `DOSU_CLI_SENTRY_DSN`
+- Runtime overrides: `DOSU_POSTHOG_PROJECT_TOKEN_OVERRIDE`, `DOSU_CLI_SENTRY_DSN_OVERRIDE`
+- Privacy controls: `DO_NOT_TRACK=1`, `DOSU_TELEMETRY_DISABLED=1`,
+  `DOSU_TELEMETRY_DEBUG=1` (print the exact payload to stderr without sending it)
+
+PostHog project tokens and Sentry DSNs are public client-side ingestion credentials. Never put a
+PostHog personal API key, Sentry auth token, or admin/management credential in these variables.
+
 ## Development
 
 ```bash