dodopayments-cli 3.0.2 → 3.1.0

package/README.md

@@ -37,7 +37,7 @@ Manage your [Dodo Payments](https://dodopayments.com/) resources, test webhooks,
 
 - **Interactive TUI** — launch `dodo` with no arguments to open the full interactive interface with command palette, history, and live notifications.
 - **AI assistant built in** — ask questions or take actions in plain English with `/ai`. No extra setup, runs `dodopayments-mcp` locally.
-- **Secure by default** — API keys are stored in your OS secret store (macOS Keychain, Windows Credential Vault, Linux libsecret). No plaintext config on disk.
+- **Encrypted at rest** — API keys are stored in `~/.dodopayments/config.json`, AES-256-GCM encrypted with a machine-derived key. No plaintext credentials on disk.
 - **Auto update** — the CLI checks for new versions and notifies you in-app. Run `/update` to upgrade in place.
 - **Webhook tooling** — listen for live webhooks or trigger payloads offline for local development.
 
@@ -103,9 +103,9 @@ The login flow will:
 1. Open your browser to the Dodo Payments API Keys page.
 2. Prompt you to paste your API Key.
 3. Ask you to select an environment — **Test Mode** or **Live Mode**.
-4. Store the credentials in your OS secret store (Keychain on macOS, Credential Vault on Windows, libsecret on Linux).
+4. Store the credentials encrypted at `~/.dodopayments/config.json` (AES-256-GCM, machine-bound key).
 
-> **Heads up:** Because we use the OS secret store, you may be prompted for your **device password** the first time the CLI reads or writes credentials. If you're upgrading from an older version, any existing plaintext API key will be **migrated to the secret store and the legacy file deleted** automatically.
+> **Upgrading from v3.0.x?** Your previous keychain-stored credentials won't carry over — just run `dodo login` once to re-authenticate.
 
 ### Switching modes / logging out
 
@@ -151,11 +151,11 @@ For example:
 
 ```bash
 dodo payments list 1
-dodo customers create
-dodo wh trigger
+dodo customers list
+dodo wh trigger payment.success http://localhost:3000/webhook
 ```
 
-The reference tables below show every command. In the TUI, prefix them with `/`; in direct mode, drop the `/`.
+The reference tables below show every command. In the TUI, prefix them with `/`; in direct mode, drop the `/`. Commands marked `(TUI only)` are interactive wizards and only work inside the TUI.
 
 ---
 
@@ -198,16 +198,16 @@ The assistant respects your active environment (Test / Live).
 | Command | Description |
 | --- | --- |
 | `/customers list <page>` | List customers |
-| `/customers create` | Create a new customer |
-| `/customers update <id>` | Update an existing customer |
+| `/customers create` | Create a new customer (TUI only) |
+| `/customers update <id>` | Update an existing customer (TUI only) |
 
 ### Discounts
 
 | Command | Description |
 | --- | --- |
 | `/discounts list <page>` | List discounts |
-| `/discounts create` | Create a new percentage-based discount |
-| `/discounts delete <id>` | Remove a discount by ID |
+| `/discounts create` | Create a new percentage-based discount (TUI only) |
+| `/discounts delete <id>` | Remove a discount by ID (TUI only) |
 
 ### Licenses
 
@@ -234,7 +234,7 @@ The assistant respects your active environment (Test / Live).
 
 | Command | Description |
 | --- | --- |
-| `/checkout new` | Interactively create a hosted checkout session and get a payment link |
+| `/checkout new` | Interactively create a hosted checkout session and get a payment link (TUI only) |
 
 ### Webhooks
 
@@ -242,10 +242,12 @@ Manage and test webhooks directly from the CLI.
 
 | Command | Description |
 | --- | --- |
-| `/wh listen` | Listen for webhooks in real time and forward them to your local dev server |
-| `/wh trigger` | Trigger a test webhook event interactively — even while logged out |
+| `/wh listen <url>` | Listen for webhooks in real time and forward them to `<url>` |
+| `/wh trigger <event> <url>` | Trigger a test webhook event offline — even while logged out |
 
-The `/wh trigger` flow guides you through:
+In the TUI, omitting the args (`/wh listen` or `/wh trigger`) opens an interactive wizard. In direct mode (`dodo wh …`), both arguments are required.
+
+The interactive `/wh trigger` flow guides you through:
 
 1. Setting a destination **endpoint URL**
 2. Selecting a specific **event** to trigger