vibelet 1.2.222 → 1.2.224

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 (6) hide show
  1. package/README.md +8 -4
  2. package/dist/index.cjs +1 -1
  3. package/dist/inventory-scan-worker.cjs +1 -1
  4. package/dist/runtime-version.cjs +1 -1
  5. package/dist/vibelet.mjs +170 -105
  6. package/package.json +1 -1
package/README.md CHANGED
@@ -47,7 +47,7 @@ prints `Web UI (other devices)` for LAN or remote browsers.
47
47
  ## Options
48
48
 
49
49
  ```bash
50
- vibelet --access=local # Skip the default Cloudflare Tunnel for this run
50
+ vibelet --access=local # Disable Tailcat and Cloudflare for this run
51
51
  vibelet --access=remote --force # Force a fresh tunnel URL
52
52
  vibelet --access=https://<your-tunnel-url> # Use your own tunnel URL
53
53
  vibelet --access=<tailscale-or-lan-host> # Use a direct private-network host
@@ -57,7 +57,7 @@ vibelet --tailcat # Enable account-free Tailcat direc
57
57
  vibelet --no-tailcat # Disable previously enabled Tailcat access
58
58
  ```
59
59
 
60
- Remote access is enabled by default for `vibelet`, `vibelet start`, `vibelet restart`, and `vibelet reset`. Use `--access=local` when you want a LAN-only QR code for that run. Legacy aliases still work: `--local`, `--relay`, `--host`, `--fallback-hosts`, `--remote`, and `--tunnel`.
60
+ Tailcat and Cloudflare remote access are enabled by default for `vibelet`, `vibelet start`, `vibelet restart`, and `vibelet reset`. Use `--access=local` when you want a LAN-only QR code for that run. This also disables Tailcat for the current run, even if it was previously enabled; the saved Tailcat choice is unchanged. Legacy aliases still work: `--local`, `--relay`, `--host`, `--fallback-hosts`, `--remote`, and `--tunnel`.
61
61
 
62
62
  Managed Cloudflare Tunnels use cloudflared's `auto` transport so QUIC is preferred
63
63
  when UDP is available and HTTP/2 remains the fallback. The CLI checks its bundled,
@@ -81,8 +81,10 @@ Then scan the newly printed QR code with a Vibelet app build that includes
81
81
  Tailcat support. The app races the eligible connection paths and uses the first
82
82
  healthy one. Tailcat bootstraps through DERP and upgrades to a direct P2P UDP
83
83
  path when NAT traversal succeeds; if it cannot become direct, DERP can remain
84
- the encrypted relay. LAN, Tailscale, and Cloudflare targets stay available as
85
- Vibelet fallbacks.
84
+ the encrypted relay. LAN and Tailscale remain available as fallbacks. Tailcat mode skips automatic
85
+ Cloudflare Tunnel startup and saved relay URLs. To also enable Cloudflare, use
86
+ `npx vibelet --tailcat --cloudflare`; for a custom relay, add
87
+ `--access=https://<url>`.
86
88
 
87
89
  The `--tailcat` choice is stored in `~/.vibelet/tailcat.json` and reused by
88
90
  later starts and restarts. Turn it off with:
@@ -139,3 +141,5 @@ the tool's own timeout. If presence can no longer be verified, the hard timeout
139
141
  also checks time since the last verified presence; a single missed check after a
140
142
  long wait does not immediately terminate the turn. The existing idle-driver
141
143
  release policy is independent and still applies after the turn finishes.
144
+
145
+ Both Tailcat and Cloudflare are enabled by default. Use `npx vibelet --tailcat` for Tailcat only, or `npx vibelet --cloudflare` for Cloudflare only. `--access=remote`, `--remote`, and `--tunnel` remain compatible aliases. `--no-tailcat` disables Tailcat while keeping Cloudflare available.