vibelet 1.2.224 → 1.2.226

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/README.md CHANGED
@@ -47,17 +47,17 @@ prints `Web UI (other devices)` for LAN or remote browsers.
47
47
  ## Options
48
48
 
49
49
  ```bash
50
- vibelet --access=local # Disable Tailcat and Cloudflare for this run
50
+ vibelet --access=local # Disable Remote Direct 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
54
54
  vibelet --access=<host>,<fallback1> # Add fallback private-network hosts
55
55
  vibelet --access= # Clear saved relay URL
56
- vibelet --tailcat # Enable account-free Tailcat direct access
57
- vibelet --no-tailcat # Disable previously enabled Tailcat access
56
+ vibelet --remote-direct # Enable account-free Remote Direct
57
+ vibelet --no-remote-direct # Disable previously enabled Remote Direct access
58
58
  ```
59
59
 
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`.
60
+ Remote Direct is enabled by default; Cloudflare is opt-in 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 Remote Direct for the current run, even if it was previously enabled; the saved Remote Direct 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,
@@ -67,39 +67,11 @@ modified. Versions older than 2026.5.2 temporarily stay on HTTP/2 because their
67
67
  automatic QUIC fallback can delay tunnel readiness for minutes. Update metadata
68
68
  is stored in `~/.vibelet/cloudflared-update.json`.
69
69
 
70
- ## Tailcat direct access
70
+ ## Remote Direct
71
71
 
72
- Tailcat gives Vibelet a userspace, end-to-end WireGuard-encrypted connection
73
- without requiring a Tailscale account, root/admin access, an inbound port, or
74
- changes to the computer's VPN, DNS, and routes. Enable it on the computer:
72
+ Run `npx vibelet` and scan the new QR with the current app. Remote Direct is enabled by default and requires no separate networking app or account. Vibelet attempts an encrypted direct path and falls back to an encrypted relay when needed.
75
73
 
76
- ```bash
77
- npx vibelet --tailcat
78
- ```
79
-
80
- Then scan the newly printed QR code with a Vibelet app build that includes
81
- Tailcat support. The app races the eligible connection paths and uses the first
82
- healthy one. Tailcat bootstraps through DERP and upgrades to a direct P2P UDP
83
- path when NAT traversal succeeds; if it cannot become direct, DERP can remain
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>`.
88
-
89
- The `--tailcat` choice is stored in `~/.vibelet/tailcat.json` and reused by
90
- later starts and restarts. Turn it off with:
91
-
92
- ```bash
93
- npx vibelet --no-tailcat
94
- ```
95
-
96
- Seeing `127.0.0.1:39876` in the mobile app is expected: it is the app-local
97
- loopback forwarder, not the remote computer's address. Its upstream connection
98
- is the encrypted Tailcat path. Use `npx vibelet status` to check whether the
99
- Tailcat sidecar is enabled and running, and `npx vibelet logs` if startup fails.
100
- Make sure both devices can make outbound HTTPS connections; direct P2P also
101
- benefits from outbound UDP. Never share a pairing QR code or a raw `tc...`
102
- connection token publicly.
74
+ Cloudflare is off by default. Add `--cloudflare` for an additional path, or use `--access=local` for LAN-only pairing. Internal forwarding addresses are managed automatically and are hidden from ordinary connection displays. Use `status` and `logs` for diagnostics; do not share connection credentials.
103
75
 
104
76
  ## Release
105
77
 
@@ -142,4 +114,4 @@ also checks time since the last verified presence; a single missed check after a
142
114
  long wait does not immediately terminate the turn. The existing idle-driver
143
115
  release policy is independent and still applies after the turn finishes.
144
116
 
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.
117
+ Remote Direct is enabled by default. Cloudflare is off unless explicitly requested with `npx vibelet --cloudflare`. Use `--access=local` for LAN-only pairing.