@wavespeed/cli 0.4.19 → 0.4.20
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.
- package/package.json +1 -1
- package/skills/SKILL.md +2 -1
package/package.json
CHANGED
package/skills/SKILL.md
CHANGED
|
@@ -77,4 +77,5 @@ The CLI never modifies the user's prompt or inputs. The single exception is expl
|
|
|
77
77
|
- Don't invent model IDs. Always confirm via `wavespeed models` or `wavespeed schema <id>` before running.
|
|
78
78
|
- Use `--json` on every `run` so you can read `outputs[0]` programmatically.
|
|
79
79
|
- `wavespeed delete` requires `--yes` when run non-interactively (that includes you).
|
|
80
|
-
-
|
|
80
|
+
- Cost and spend: `wavespeed price <id> -i k=v --json` estimates a run without generating or charging; `wavespeed balance` shows remaining credit; `wavespeed usage` (totals, per-model) and `wavespeed billings` (per-charge records) show what was spent.
|
|
81
|
+
- A `run` that fails with a gateway or network error (502/503/504, connection reset, timeout) does NOT mean the task failed, and the submit request is never retried automatically, so re-running can create a duplicate paid task. Do not re-run immediately. If the error contains a task id (`task_id` / prediction id), keep checking it with `wavespeed show <id> --json` until its status is terminal (`completed`, `failed`, `cancelled`, `timeout`, `deleted`). If no id was returned, check recent predictions with `wavespeed history --json` (add `--model <id>`; default window is the last 24h) and re-run once only if none matches. A client-side wait timeout or an interrupted `run` does not mean the task failed: tasks can run for a long time, so do not give up after a fixed time.
|