@whop/cli 0.18.0 → 0.18.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@whop/cli",
-  "version": "0.18.0",
+  "version": "0.18.2",
   "description": "The Whop CLI — build and manage Whop apps from your terminal. Human and agent friendly.",
   "keywords": [
     "agent",

package/skills/whop/references/websites.md

@@ -46,6 +46,23 @@ The app must use the `whop()` Vite plugin (`@whop/cli/vite`). Missing it fails w
 
 Preview output is a build id. The production URL exists only after promote. `hosted_url` on `whop apps get` is the live app URL — display it; do not treat it as a "complete this step" action link.
 
+## Experimentation
+
+Split traffic between the live production build and one next build of the same app. Whop hosting assigns visitors, serves the bound build, and records exposures. Always this flow — never a client-side test, never `whop experiments exposures`, never promote the treatment. One active experiment per app.
+
+```sh
+whop experiments list --account_id biz_xxx --related_resource '{"object":"app","id":"app_xxx"}' --status active
+whop apps deploy --preview
+whop experiments create --account_id biz_xxx --flag_key xxxxxxxx --bucket_by anonymous \
+  --hypothesis "If we xxxxxxxx for xxxxxxxx, then xxxxxxxx will xxxxxxxx, resulting in xxxxxxxx, because xxxxxxxx. Created by xxxxxxxx." \
+  --related_resource '{"object":"app","id":"app_xxx"}' \
+  --control '{"related_resource":{"object":"app_build","id":"apbu_xxxxxxxx"}}' \
+  --variants '[{"name":"xxxxxxxx","weight":50,"related_resource":{"object":"app_build","id":"apbu_yyyyyyyy"}}]'
+whop experiments activate expt_xxx
+```
+
+`--preview` is the next version. Control is `production_web_build.id` from `whop apps get`. Related resource is the app. Each arm must bind a different build. If the list is non-empty, pause or end that experiment first — do not start a second. Then activate. Hosting does the rest. Flags: `whop experiments create --help`.
+
 ## Dev, secrets, logs
 
 ```sh