@genex-ai/cli-demo 0.37.0 → 0.39.0

package/README.md

@@ -16,6 +16,7 @@ genex texture "<prompt>"   # generate a texture   → prints an asset URL
 genex image "<prompt>"     # generate an image    → prints an asset URL
 genex video "<prompt>"     # generate a video     → prints an asset URL
 genex controller <type>    # install a tuned character|car|drone controller → src/controllers/
+genex controller anims <sel…>  # download extra character animation clips (by tag or name) → public/assets/anims/
 ```
 
 > **Invoking it.** First-time setup runs via `npx @genex-ai/cli-demo@latest init`.
@@ -183,6 +184,27 @@ GENEX_BROWSER="open -a Safari" genex init
 GENEX_BROWSER="'/Applications/My Browser.app/Contents/MacOS/My Browser'" genex init
 ```
 
+## Crash reporting
+
+When a command hits an **unexpected** error, the CLI reports the crash to Sentry
+so we can fix it. Expected failures (missing token, a rejected API request, bad
+input) are just printed — they're not sent. Before anything leaves your machine
+it's scrubbed: your `GENEX_TOKEN` and any credentials, credential-bearing URLs
+(e.g. the per-push git URL), your home-directory paths and hostname, and
+stack-frame locals are all stripped ([`src/lib/sentry-scrub.ts`](src/lib/sentry-scrub.ts)).
+No IP address or account identity is attached. Only the crash, the command name,
+and your CLI/Node/OS versions are sent.
+
+Opt out any time:
+
+```bash
+export GENEX_TELEMETRY=0     # our switch (on by default)
+export DO_NOT_TRACK=1        # the cross-tool standard — any value disables it
+```
+
+Reporting is also off whenever no DSN is baked into the build (the default in
+local/source runs), so nothing is sent during development.
+
 ## How authorization works
 
 The CLI uses a loopback-redirect flow (the same pattern as `gh auth login` and