vibelet 1.2.224 → 1.2.227

package/README.md

@@ -35,11 +35,16 @@ vibelet stop         # Stop the daemon
 vibelet restart      # Restart the daemon
 vibelet status       # Show service and daemon status
 vibelet logs         # Print recent daemon logs
-vibelet reset        # Reset pairings and print a fresh QR code
+vibelet reset        # Clear pairings and saved device connections; print a fresh QR code
 vibelet --help       # Show help
 vibelet --version    # Show CLI version
 ```
 
+`reset` clears this daemon's synced device profiles (including saved connection addresses),
+revokes all pairings, and disconnects authenticated clients. Scan the fresh QR code to pair again.
+It does not erase records stored on your phone; those can sync back after pairing,
+so remove obsolete computers in the app as well when you want to discard them permanently.
+
 The printed `Web UI` link uses `http://localhost:<port>` for a stable, browser-trusted
 same-machine connection. When another advertised route is available, the CLI also
 prints `Web UI (other devices)` for LAN or remote browsers.
@@ -47,17 +52,17 @@ prints `Web UI (other devices)` for LAN or remote browsers.
 ## Options
 
 ```bash
-vibelet --access=local                       # Disable Tailcat and Cloudflare 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
 ```
 
-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`.
+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,39 +72,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
-
-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:
-
-```bash
-npx vibelet --tailcat
-```
+## Remote Direct
 
-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 and Tailscale remain available as fallbacks. Tailcat mode skips automatic
-Cloudflare Tunnel startup and saved relay URLs. To also enable Cloudflare, use
-`npx vibelet --tailcat --cloudflare`; for a custom relay, add
-`--access=https://<url>`.
-
-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
-```
+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.
 
-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
 
@@ -142,4 +119,4 @@ 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.
 
-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.
+Remote Direct is enabled by default. Cloudflare is off unless explicitly requested with `npx vibelet --cloudflare`. Use `--access=local` for LAN-only pairing.