remotelink 0.3.14 → 0.4.1

package/README.md

@@ -17,7 +17,8 @@ On first run, `remotelink`:
 2. opens the Remote Arc pairing page in your browser;
 3. asks you to sign in and approve the device;
 4. stores a device credential locally in `~/.remotearc/config.json`;
-5. connects the computer to Remote Arc over an outbound WebSocket.
+5. connects in the foreground while you choose device permissions;
+6. if Background connection remains selected, installs a user-level login service only after you finish browser setup.
 
 No public IP, VPN, router port forwarding, repository clone, or manual token
 copy is required.
@@ -39,12 +40,15 @@ https://remotearc.app
 ## Commands
 
 ```text
-npx remotelink             Connect with dashboard-managed skills
-npx remotelink --safe      Hard local read-only cap
-npx remotelink --developer Legacy alias for dashboard-managed capabilities
-npx remotelink --reset     Remove local pairing credentials
-npx remotelink --version   Show the CLI version
-npx remotelink --help      Show help
+npx remotelink                 Pair, reconnect, or ensure the configured connection mode
+npx remotelink --safe          Hard local read-only cap
+npx remotelink --developer     Legacy alias for dashboard-managed capabilities
+npx remotelink --foreground    Keep this run attached to the terminal
+npx remotelink --background    Enable/repair login background mode
+npx remotelink --no-background Disable login background mode and stay foreground
+npx remotelink --reset         Remove local pairing and background registration
+npx remotelink --version       Show the CLI version
+npx remotelink --help          Show help
 ```
 
 The package also exposes the aliases `remote-link` and `remote-arc`.
@@ -72,6 +76,18 @@ while the relay enforces the saved per-device policy before forwarding a call.
 Use `--safe` when you want an additional local hard cap that prevents write
 skills from running even if they are enabled in the dashboard.
 
+Device permissions, Trusted Write Locations, Sensitive Path settings, Approval
+Broker decisions, and Undo policy are managed from Remote Arc Cloud and enforced
+again by the local execution core. The
+CLI does not keep a second editable copy of those policies. Local options such as
+`--safe` may only make access stricter; they cannot silently broaden Dashboard
+permissions.
+
+Background mode is different because it is operating-system state. The Dashboard
+can request a change while the device is online, but the local agent reports the
+actual launchd, Task Scheduler, or systemd-user result back before the Dashboard
+shows the setting as enabled.
+
 ## Local Undo
 
 Remote Arc snapshots the previous local file state before supported
@@ -89,20 +105,28 @@ Local Undo covers Remote Arc file writes only. It cannot reverse external side
 effects such as publishing a package, deploying cloud infrastructure, sending a
 request to another service, or mutating a remote database.
 
-## Workspace and sensitive-path policy
+## Trusted Write Locations, approvals and sensitive paths
 
-The dashboard can configure allowed workspace roots, additional protected
+The dashboard can configure Trusted Write Locations, additional protected
 paths, and narrow sensitive-path exceptions per device. Online devices also
-support a local directory picker so workspace roots can be selected without
-typing paths manually. Sensitive-path
-protection stays on by default for common credential locations and `.env`
-files; an exception bypasses only sensitive-path protection, not Workspace
-Scope.
+support a local directory picker so trusted write roots can be selected without
+typing paths manually.
+
+Ordinary non-sensitive read-only file tools may inspect paths outside Trusted
+Write Locations. Supported mutations stay inside trusted write roots unless an
+out-of-scope write receives a matching Approval Broker grant. The dashboard and
+an interactive remotelink terminal can approve once, allow the same file
+briefly, trust the parent folder, or deny the request.
+
+Sensitive-path protection remains independent and stays enabled for common
+credential locations and `.env` files. A sensitive-path exception grants
+visibility to that path; it does not grant write authority outside Trusted Write
+Locations.
 
 Filesystem paths are canonicalized and checked locally immediately before
-execution. If workspace roots are configured, file operations must stay under
-those roots. Full terminal mode requires an in-scope `cwd`, but shell commands
-are not an OS sandbox and can still reference other paths.
+execution. Full terminal mode requires an in-scope `cwd` when trusted write
+roots are configured, but shell commands are not an OS sandbox and can still
+reference other paths, credentials, processes or network services.
 
 ## Safety Guard