ideawave 0.0.63 → 0.0.65

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/README.md +9 -3
  2. package/dist/index.mjs +811 -23
  3. package/package.json +1 -1
package/README.md CHANGED
@@ -11,9 +11,9 @@ Then open [ideawave.app](https://ideawave.app), choose a board, and start an age
11
11
  ## Requirements
12
12
 
13
13
  - Node.js 18 or newer
14
- - Google Chrome for live browser cards (recommended). If Chrome is unavailable,
15
- IdeaWave downloads its pinned Chromium engine on first browser-card use and
16
- reuses it on later runs.
14
+ - Google Chrome for the existing live-browser and screenshot runtimes. The
15
+ `--dev` browser-kit preview stays inside the app iframe and does not launch a
16
+ second browser process.
17
17
  - At least one supported agent runtime installed and signed in:
18
18
  - Claude Code
19
19
  - Codex CLI
@@ -23,6 +23,7 @@ Then open [ideawave.app](https://ideawave.app), choose a board, and start an age
23
23
  ## Commands
24
24
 
25
25
  ```bash
26
+ npx ideawave --dev
26
27
  npx ideawave --help
27
28
  npx ideawave --version
28
29
  ```
@@ -37,3 +38,8 @@ Live browser cards run in a dedicated, persistent local IdeaWave browser
37
38
  profile. Website sign-ins and cookies stay on the machine. Browser cards may
38
39
  store a sanitized latest-page snapshot with the board so the last rendered
39
40
  state remains visible when the CLI disconnects.
41
+
42
+ When started with `--dev`, the CLI advertises the preview-only
43
+ `browser-proxy-v4` capability instead. Browser cards remain in the app iframe
44
+ and route pages and subresources through the local browser-kit proxy. This
45
+ mode is intended for testing the browser-component preview before it merges.