remosidian 0.1.11 → 0.1.13

package/CHANGELOG.md

@@ -1,5 +1,13 @@
 # Remosidian CLI 更新日志
 
+## 0.1.13
+
+- Resume paired assistant conversations and cancel stalled replies before continuing.
+
+## 0.1.12
+
+- Test paired vault access and assistant conversations over local or secure remote connections.
+
 ## 0.1.11
 
 - Updated beta build for testing paired vault access, assistant messages, and remote connections.

package/README.md

@@ -54,20 +54,24 @@ stored in `~/.remosidian/pairings.json` and reused on subsequent connections.
 
 ```bash
 remosidian --access=local                       # LAN/local pairing only
-remosidian --access=remote --force              # Force a fresh Cloudflare Tunnel URL
+remosidian --cloudflare --force                 # Also start a fresh Cloudflare Tunnel
 remosidian --access=https://<your-tunnel-url>   # Use your own relay URL
 remosidian --access=<tailscale-or-lan-host>     # Use a direct private-network host
 remosidian --access=<host>,<fallback1>          # Add fallback private-network hosts
 remosidian --access=                            # Clear saved relay URL
 ```
 
-Remote access is enabled by default for `remosidian` and `remosidian start`. Use
+Remote Direct is enabled by default for `remosidian` and `remosidian start`. 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`.
+`--tunnel`. These aliases use the default Remote Direct path.
 
-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,
+Remote Direct requires the updated Remosidian mobile app with its native transport.
+The CLI bundle includes the transport binaries for macOS, Linux, and Windows.
+
+Cloudflare is optional: add `--cloudflare` to also start a managed tunnel. Saved
+relay URLs are ignored unless explicitly requested. Managed tunnels default to
+HTTP/2; `REMOSIDIAN_CLOUDFLARED_PROTOCOL=auto` enables automatic transport selection. The CLI checks its bundled,
 user-owned cloudflared binary for updates at most once every 24 hours. A failed
 check does not prevent startup, and system package-manager binaries are never
 modified. Versions older than 2026.5.2 temporarily stay on HTTP/2 because their
@@ -79,6 +83,15 @@ is stored in `~/.remosidian/cloudflared-update.json`.
 By default, Remosidian stores identity, pairings, and the QR PNG under `~/.remosidian/`.
 Override with `--data-dir <path>` or the `REMOSIDIAN_HOME` environment variable.
 
+Private mobile features are advertised by the daemon. Run `remosidian start
+--personal-agent` (or `--pa`) to expose the Personal Agent entry in paired
+mobile apps, or `remosidian start --no-personal-agent` (or `--no-pa`) to hide
+it. The CLI restarts a background
+daemon it manages when the requested state differs from the running state. The
+entry stays hidden by default and on older daemons that do not advertise the
+capability. `REMOSIDIAN_PERSONAL_AGENT=1` and
+`server.features.personalAgent` remain available for service deployments.
+
 ## Protocol
 
 WebSocket + JSON messages defined in [`@lifeos/remosidian-protocol`](https://www.npmjs.com/package/@lifeos/remosidian-protocol).