vibelet 1.2.222 → 1.2.226

package/README.md

@@ -47,17 +47,17 @@ prints `Web UI (other devices)` for LAN or remote browsers.
 ## Options
 
 ```bash
-vibelet --access=local                       # Skip the default Cloudflare Tunnel for this run
+vibelet --access=local                       # Disable Remote Direct and Cloudflare for this run
 vibelet --access=remote --force              # Force a fresh tunnel URL
 vibelet --access=https://<your-tunnel-url>   # Use your own tunnel URL
 vibelet --access=<tailscale-or-lan-host>     # Use a direct private-network host
 vibelet --access=<host>,<fallback1>          # Add fallback private-network hosts
 vibelet --access=                            # Clear saved relay URL
-vibelet --tailcat                            # Enable account-free Tailcat direct access
-vibelet --no-tailcat                         # Disable previously enabled Tailcat access
+vibelet --remote-direct                            # Enable account-free Remote Direct
+vibelet --no-remote-direct                         # Disable previously enabled Remote Direct access
 ```
 
-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`.
+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`.
 
 Managed Cloudflare Tunnels use cloudflared's `auto` transport so QUIC is preferred
 when UDP is available and HTTP/2 remains the fallback. The CLI checks its bundled,
@@ -67,37 +67,11 @@ modified. Versions older than 2026.5.2 temporarily stay on HTTP/2 because their
 automatic QUIC fallback can delay tunnel readiness for minutes. Update metadata
 is stored in `~/.vibelet/cloudflared-update.json`.
 
-## Tailcat direct access
+## Remote Direct
 
-Tailcat gives Vibelet a userspace, end-to-end WireGuard-encrypted connection
-without requiring a Tailscale account, root/admin access, an inbound port, or
-changes to the computer's VPN, DNS, and routes. Enable it on the computer:
+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.
 
-```bash
-npx vibelet --tailcat
-```
-
-Then scan the newly printed QR code with a Vibelet app build that includes
-Tailcat support. The app races the eligible connection paths and uses the first
-healthy one. Tailcat bootstraps through DERP and upgrades to a direct P2P UDP
-path when NAT traversal succeeds; if it cannot become direct, DERP can remain
-the encrypted relay. LAN, Tailscale, and Cloudflare targets stay available as
-Vibelet fallbacks.
-
-The `--tailcat` choice is stored in `~/.vibelet/tailcat.json` and reused by
-later starts and restarts. Turn it off with:
-
-```bash
-npx vibelet --no-tailcat
-```
-
-Seeing `127.0.0.1:39876` in the mobile app is expected: it is the app-local
-loopback forwarder, not the remote computer's address. Its upstream connection
-is the encrypted Tailcat path. Use `npx vibelet status` to check whether the
-Tailcat sidecar is enabled and running, and `npx vibelet logs` if startup fails.
-Make sure both devices can make outbound HTTPS connections; direct P2P also
-benefits from outbound UDP. Never share a pairing QR code or a raw `tc...`
-connection token publicly.
+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.
 
 ## Release
 
@@ -139,3 +113,5 @@ the tool's own timeout. If presence can no longer be verified, the hard timeout
 also checks time since the last verified presence; a single missed check after a
 long wait does not immediately terminate the turn. The existing idle-driver
 release policy is independent and still applies after the turn finishes.
+
+Remote Direct is enabled by default. Cloudflare is off unless explicitly requested with `npx vibelet --cloudflare`. Use `--access=local` for LAN-only pairing.