@bli-cockpit/cli 0.1.21 → 0.1.22
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/README.md +33 -21
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -14,24 +14,24 @@ device pairing.
|
|
|
14
14
|
Run this from the repo where work will happen:
|
|
15
15
|
|
|
16
16
|
```bash
|
|
17
|
-
COCKPIT_DEVICE_NAME="$(scutil --get ComputerName 2>/dev/null || hostname -s)"
|
|
18
17
|
npm install -g @bli-cockpit/cli@latest
|
|
19
|
-
cockpit onboard
|
|
20
|
-
|
|
21
|
-
|
|
22
|
-
|
|
18
|
+
cockpit onboard --workspace "$PWD"
|
|
19
|
+
```
|
|
20
|
+
|
|
21
|
+
Interactive onboarding prompts for the dashboard email. Enter the approved
|
|
22
|
+
intern/operator email. For reused laptops, VMs, or headless/agent-run setup,
|
|
23
|
+
pass the email explicitly:
|
|
24
|
+
|
|
25
|
+
```bash
|
|
26
|
+
cockpit onboard --email <APPROVED_EMAIL> --workspace "$PWD"
|
|
23
27
|
```
|
|
24
28
|
|
|
25
29
|
If a work folder contains multiple repos, run the same command from the parent:
|
|
26
30
|
|
|
27
31
|
```bash
|
|
28
32
|
cd ~/Downloads/bluepearl-workspace
|
|
29
|
-
COCKPIT_DEVICE_NAME="$(scutil --get ComputerName 2>/dev/null || hostname -s)"
|
|
30
33
|
npm install -g @bli-cockpit/cli@latest
|
|
31
|
-
cockpit onboard
|
|
32
|
-
--email <APPROVED_EMAIL> \
|
|
33
|
-
--device-name "$COCKPIT_DEVICE_NAME" \
|
|
34
|
-
--workspace "$PWD"
|
|
34
|
+
cockpit onboard --workspace "$PWD"
|
|
35
35
|
```
|
|
36
36
|
|
|
37
37
|
The CLI defaults to the production dashboard. Normal intern/operator setup,
|
|
@@ -50,6 +50,11 @@ to install or replace it. The managed guidance is scoped to the workspace path
|
|
|
50
50
|
used for onboarding, so agents should ignore it in private chats or unrelated
|
|
51
51
|
repos.
|
|
52
52
|
|
|
53
|
+
For intern machines, accept the onboarding prompt to keep Cockpit syncing in the
|
|
54
|
+
background. It installs the launchd autostart agent so Cockpit syncs at login
|
|
55
|
+
and every 15 minutes. If skipped, run
|
|
56
|
+
`cockpit autostart install --workspace "$PWD"` later.
|
|
57
|
+
|
|
53
58
|
```bash
|
|
54
59
|
# Repair/manual path, or headless/json onboarding where Cockpit cannot prompt.
|
|
55
60
|
cockpit agent-rules install --workspace "$PWD"
|
|
@@ -79,33 +84,40 @@ What happens:
|
|
|
79
84
|
1. npm installs or updates the public `@bli-cockpit/cli` package.
|
|
80
85
|
2. `cockpit onboard` writes local user config.
|
|
81
86
|
3. Cockpit prints a dashboard pairing URL and code.
|
|
82
|
-
4. Admin approves the
|
|
83
|
-
|
|
84
|
-
|
|
87
|
+
4. Admin approves the persistent email access request from Ambient -> Collector
|
|
88
|
+
approvals. Pair codes still expire, but the access request remains. If the
|
|
89
|
+
terminal is still polling, approval pairs it immediately; if not, the intern
|
|
90
|
+
reruns `cockpit onboard --email <APPROVED_EMAIL> --workspace "$PWD"` and the
|
|
91
|
+
stored approval auto-pairs without another Admin action. Admin can still
|
|
92
|
+
paste the printed code there as a rescue path. The signed-in intern can still
|
|
93
|
+
use the printed URL. If the claimed email is not an app user yet, a super
|
|
94
|
+
admin approval creates the user, adds team membership, and sends the
|
|
95
|
+
Supabase invite flow automatically.
|
|
85
96
|
5. The CLI starts general ambient capture, uploads private raw evidence objects
|
|
86
97
|
when present (chunked and resumable, with identical content acknowledged
|
|
87
98
|
instead of re-uploaded), then uploads one safe metadata/ref envelope.
|
|
88
99
|
6. The CLI prints `PASS: Cockpit collector is ready for harvest.`
|
|
89
100
|
|
|
90
|
-
`--device-name` is
|
|
91
|
-
`"Savina MacBook"
|
|
101
|
+
`--device-name` is optional and only a readable label in Cockpit. Pass it only
|
|
102
|
+
when you want a specific label such as `"Savina MacBook"` or `"Box VM 42"`.
|
|
92
103
|
On reused laptops or VMs, keep `--email <APPROVED_EMAIL>` in the command.
|
|
93
104
|
`cockpit onboard` skips pairing only when the existing valid session belongs to
|
|
94
105
|
that same email and dashboard URL (the production default unless overridden); a
|
|
95
106
|
different email or dashboard forces a new approval.
|
|
96
107
|
|
|
97
|
-
Before the command runs, an Admin
|
|
98
|
-
|
|
99
|
-
|
|
100
|
-
|
|
101
|
-
|
|
108
|
+
Before the command runs, an Admin does not need to open Supabase or pre-create
|
|
109
|
+
ordinary interns in Settings -> Team. Approval of the claimed email in Ambient
|
|
110
|
+
creates the missing app user and stores the durable access approval. Settings
|
|
111
|
+
-> Team remains available for manual pre-provisioning, including
|
|
112
|
+
temporary-password launch. For temporary-password accounts, the intern signs in
|
|
113
|
+
directly; there is no separate invite acceptance step.
|
|
102
114
|
|
|
103
115
|
When ticket work starts later:
|
|
104
116
|
|
|
105
117
|
```bash
|
|
106
118
|
cockpit start \
|
|
107
119
|
--ticket <ticket-id> \
|
|
108
|
-
--
|
|
120
|
+
--workspace "$PWD"
|
|
109
121
|
|
|
110
122
|
cockpit sync \
|
|
111
123
|
--workspace "$PWD" \
|