dsh-dispatch 0.1.0 → 0.3.0
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.
- package/cordis.patch.yml +8 -0
- package/dist/index.js +433 -43
- package/dist/index.js.map +1 -1
- package/package.json +17 -11
- package/LICENSE +0 -21
package/cordis.patch.yml
CHANGED
|
@@ -11,6 +11,7 @@
|
|
|
11
11
|
# config:
|
|
12
12
|
# relay: 'wss://relay.example.com'
|
|
13
13
|
# allowedRoots: ['/Users/me/code']
|
|
14
|
+
# allowFullAccessDispatch: false
|
|
14
15
|
#
|
|
15
16
|
# `relay` is REQUIRED and ships empty, which is the explicit "not configured
|
|
16
17
|
# yet" state: the plugin loads, logs one actionable error, and reports
|
|
@@ -19,9 +20,16 @@
|
|
|
19
20
|
# OFF — approval forwarding still works; dispatch requests are answered with a
|
|
20
21
|
# visible "dispatch not enabled" error until you list the directories you are
|
|
21
22
|
# willing to have an agent run in.
|
|
23
|
+
#
|
|
24
|
+
# `allowFullAccessDispatch` lets the phone ask for dsh's `danger-full-access`
|
|
25
|
+
# permission preset (full file access, no approval prompts). It is off by
|
|
26
|
+
# default and should stay off unless you know exactly which machine this is;
|
|
27
|
+
# a full-access session also raises no approvals, so nothing reaches your phone
|
|
28
|
+
# for review while it runs.
|
|
22
29
|
- insert:
|
|
23
30
|
- id: dsh-dispatch
|
|
24
31
|
name: dsh-dispatch
|
|
25
32
|
config:
|
|
26
33
|
relay: ''
|
|
27
34
|
allowedRoots: []
|
|
35
|
+
allowFullAccessDispatch: false
|