venice-video-harness 2.14.0 → 2.14.1

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.
Files changed (3) hide show
  1. package/CHANGELOG.md +14 -0
  2. package/README.md +46 -0
  3. package/package.json +1 -1
package/CHANGELOG.md CHANGED
@@ -1,5 +1,19 @@
1
1
  # Changelog
2
2
 
3
+ ## 2.14.1 — 2026-08-05
4
+
5
+ ### Changed
6
+
7
+ - **README: added a human-facing "Installing the CLI" section.** Installation
8
+ was documented only inside the agent-runner quick start; a person at a
9
+ terminal had no plain install path. The new section covers prerequisites
10
+ (Node 20+, ffmpeg/ffprobe), the global npm install with `setup` (interactive
11
+ or `--api-key`/`--workspace`/`--skip-validation`) and `doctor`, the three
12
+ bins on PATH (`venice-video`, `video-harness`, `storyboard`), the
13
+ from-source path (clone, `npm install`, `npm run build`, `npm run dev --` /
14
+ `node dist/mini-drama/cli.js`, `.env` for the API key), and pointers to
15
+ `pipeline` and `shell`. Docs only.
16
+
3
17
  ## 2.14.0 — 2026-08-05
4
18
 
5
19
  ### Changed
package/README.md CHANGED
@@ -27,6 +27,52 @@ Most Venice integrations are thin wrappers around API calls. This package is the
27
27
  - **Comprehensive model registry** covering Venice video, image, audio, and music models
28
28
  - **Optional agent orchestration** in `AGENTS.md` and `.agents/` for users who want natural-language operation
29
29
 
30
+ ## Installing the CLI
31
+
32
+ For a human at a terminal. (Driving it from an agent instead? See the next section.)
33
+
34
+ **Prerequisites:** Node 20+, and `ffmpeg` + `ffprobe` on PATH (used for video/audio processing; `venice-video doctor` checks all three).
35
+
36
+ ### Global install (recommended)
37
+
38
+ ```bash
39
+ npm install -g venice-video-harness
40
+
41
+ venice-video setup # prompts for your Venice API key + default project workspace
42
+ venice-video doctor # verifies API key, ffmpeg, ffprobe
43
+ ```
44
+
45
+ `setup` prompts interactively (the API key prompt is hidden); for non-interactive use pass `--api-key <key>` and `--workspace <dir>`, or set `VENICE_API_KEY` in the environment. `--skip-validation` stores the key without contacting Venice.
46
+
47
+ The install puts three commands on PATH:
48
+
49
+ - `venice-video` — the primary CLI
50
+ - `video-harness` — alias for the same CLI
51
+ - `storyboard` — the legacy screenplay-ingestion CLI
52
+
53
+ From there:
54
+
55
+ ```bash
56
+ venice-video pipeline # the ordered stages, their gates, and the command that advances each
57
+ venice-video shell # persistent interactive session: select a project once, background renders, /jobs
58
+ venice-video --help # everything else
59
+ ```
60
+
61
+ ### From source (development)
62
+
63
+ ```bash
64
+ git clone https://github.com/jordanurbs/venice-video-harness.git
65
+ cd venice-video-harness
66
+ npm install
67
+ npm run build
68
+
69
+ # Run via tsx during development, or the compiled CLI:
70
+ npm run dev -- pipeline
71
+ node dist/mini-drama/cli.js pipeline
72
+ ```
73
+
74
+ Put the API key in `.env` at the repo root (`VENICE_API_KEY=...`) — many scripts source it from there — or run `setup` as above.
75
+
30
76
  ## Driving this from an agent
31
77
 
32
78
  Instructions for a coding agent operating the harness — Claude Code, Cursor,
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "venice-video-harness",
3
- "version": "2.14.0",
3
+ "version": "2.14.1",
4
4
  "description": "Standalone consistency-first video production CLI powered by the Venice API",
5
5
  "homepage": "https://github.com/jordanurbs/venice-video-harness",
6
6
  "repository": {