remotelink 0.4.0 → 0.4.2

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.
Files changed (4) hide show
  1. package/README.md +21 -12
  2. package/dist/index.js +9 -3720
  3. package/dist/index.js.map +1 -1
  4. package/package.json +1 -1
package/README.md CHANGED
@@ -76,8 +76,9 @@ while the relay enforces the saved per-device policy before forwarding a call.
76
76
  Use `--safe` when you want an additional local hard cap that prevents write
77
77
  skills from running even if they are enabled in the dashboard.
78
78
 
79
- Device permissions, Workspace Scope, Sensitive Path settings, and Undo policy are
80
- managed from Remote Arc Cloud and enforced again by the local execution core. The
79
+ Device permissions, Trusted Write Locations, Sensitive Path settings, Approval
80
+ Broker decisions, and Undo policy are managed from Remote Arc Cloud and enforced
81
+ again by the local execution core. The
81
82
  CLI does not keep a second editable copy of those policies. Local options such as
82
83
  `--safe` may only make access stricter; they cannot silently broaden Dashboard
83
84
  permissions.
@@ -104,20 +105,28 @@ Local Undo covers Remote Arc file writes only. It cannot reverse external side
104
105
  effects such as publishing a package, deploying cloud infrastructure, sending a
105
106
  request to another service, or mutating a remote database.
106
107
 
107
- ## Workspace and sensitive-path policy
108
+ ## Trusted Write Locations, approvals and sensitive paths
108
109
 
109
- The dashboard can configure allowed workspace roots, additional protected
110
+ The dashboard can configure Trusted Write Locations, additional protected
110
111
  paths, and narrow sensitive-path exceptions per device. Online devices also
111
- support a local directory picker so workspace roots can be selected without
112
- typing paths manually. Sensitive-path
113
- protection stays on by default for common credential locations and `.env`
114
- files; an exception bypasses only sensitive-path protection, not Workspace
115
- Scope.
112
+ support a local directory picker so trusted write roots can be selected without
113
+ typing paths manually.
114
+
115
+ Ordinary non-sensitive read-only file tools may inspect paths outside Trusted
116
+ Write Locations. Supported mutations stay inside trusted write roots unless an
117
+ out-of-scope write receives a matching Approval Broker grant. The dashboard and
118
+ an interactive remotelink terminal can approve once, allow the same file
119
+ briefly, trust the parent folder, or deny the request.
120
+
121
+ Sensitive-path protection remains independent and stays enabled for common
122
+ credential locations and `.env` files. A sensitive-path exception grants
123
+ visibility to that path; it does not grant write authority outside Trusted Write
124
+ Locations.
116
125
 
117
126
  Filesystem paths are canonicalized and checked locally immediately before
118
- execution. If workspace roots are configured, file operations must stay under
119
- those roots. Full terminal mode requires an in-scope `cwd`, but shell commands
120
- are not an OS sandbox and can still reference other paths.
127
+ execution. Full terminal mode requires an in-scope `cwd` when trusted write
128
+ roots are configured, but shell commands are not an OS sandbox and can still
129
+ reference other paths, credentials, processes or network services.
121
130
 
122
131
  ## Safety Guard
123
132