ideawave 0.0.66 → 0.0.68

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 +7 -12
  2. package/dist/index.mjs +76 -56
  3. package/package.json +1 -1
package/README.md CHANGED
@@ -11,9 +11,8 @@ 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 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.
14
+ - Google Chrome for screenshot capture. Browser cards stay inside the app
15
+ iframe and use the CLI's local browser-kit proxy.
17
16
  - At least one supported agent runtime installed and signed in:
18
17
  - Claude Code
19
18
  - Codex CLI
@@ -34,12 +33,8 @@ If a runtime appears unavailable, confirm its command is on your `PATH` and that
34
33
 
35
34
  For supported runtimes, the CLI fetches small ACP bridge packages on first use. npm caches them, so later runs are fast. If npm's cache was cleared, keep the CLI running and retry after the bridge downloads again.
36
35
 
37
- Live browser cards run in a dedicated, persistent local IdeaWave browser
38
- profile. Website sign-ins and cookies stay on the machine. Browser cards may
39
- store a sanitized latest-page snapshot with the board so the last rendered
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.
36
+ The CLI advertises the `browser-proxy-v5` capability so browser cards can route
37
+ pages and subresources through the local browser-kit proxy. The normal command
38
+ keeps screenshot capture available. `--dev` skips screenshot-engine setup and
39
+ allows Railway PR previews for browser-card development. Existing saved browser
40
+ snapshots remain readable, but browser-kit does not create new snapshots yet.