@boxes-dev/dvb-runtime 1.0.1051 → 1.0.1052

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.
@@ -29,8 +29,26 @@ Ground rules:
29
29
 
30
30
  ## Phase 1: Prerequisites
31
31
 
32
- 1. The user must be logged in: have them run `dvb setup` (opens a browser).
33
- 2. Billing activation may be required before launch; `run` will say so with
32
+ 1. The user must be signed in to boxes.dev. The setup prompt from boxes.dev
33
+ includes a login code, and `dvb agent-init --login-code <code>` signs in
34
+ with it. If there is no code or it no longer works, follow the sign-in
35
+ instruction that `dvb agent-init` prints. `dvb agent-init login` waits
36
+ until the user finishes signing in, so run it in the background and give
37
+ them the sign-in link it prints.
38
+ 2. The user's accounts must be connected. The Template box runs Codex or
39
+ Claude Code on the user's own account, so `check` requires at least one
40
+ of them. Run `dvb agent-init accounts` in the background: it opens a
41
+ boxes.dev page where the user can connect Codex, Claude Code, GitHub, and
42
+ Slack, and it waits until they click Done, which can take several minutes.
43
+ Read its first lines, then tell the user what the page is for and give
44
+ them the link it printed in case the browser didn't open. Continue once it
45
+ reports the connected agents. If the user says they're done while it is
46
+ still waiting, they finished on the page with sign-in codes because their
47
+ browser couldn't reach this computer; stop it and run
48
+ `dvb agent-init status`.
49
+ Over SSH it prints a link for the user to open instead and exits without
50
+ waiting; continue when the user says they're done.
51
+ 3. Billing activation may be required before launch; `run` will say so with
34
52
  a link if needed. Composition can proceed regardless.
35
53
 
36
54
  ## Phase 2: Start
@@ -137,8 +155,15 @@ uninterrupted.
137
155
  the consent gate: `run` uploads their files (encrypted) and provisions a
138
156
  Template box on their account.
139
157
  3. `dvb agent-init run` — executes end to end: package (including fresh
140
- database dumps), encrypt, upload, provision, remote setup. It streams
141
- progress lines; relay the interesting ones. Expect several minutes.
158
+ database dumps), encrypt, upload, provision, remote setup. Expect several
159
+ minutes or more. Run it in the background and check its output regularly:
160
+ it streams progress lines, and you should relay the interesting ones.
161
+
162
+ Once the setup thread starts on the Template box, `run` prints one
163
+ `[handoff]` line saying where the user can follow it: the boxes.dev Mac app
164
+ (with a download link, or `dvb agent-init open-desktop` if it's installed)
165
+ or the mobile app. Relay it to the user right away, and keep watching `run`.
166
+ Don't point the user to an app before this line appears.
142
167
 
143
168
  If signing setup prints a public key, relay it with its Git-host registration
144
169
  instructions. The user can retrieve these again with `dvb agent-init status`.
@@ -148,9 +173,8 @@ re-confirm with the user.
148
173
 
149
174
  ## Phase 6: Wrap up
150
175
 
151
- When `run` completes, tell the user their Template box is ready. They can open
152
- it in the boxes.dev desktop app, connect with `dvb connect <name>`, or use the
153
- mobile app. If any imported MCP servers need re-authentication, the remote
154
- setup notes them — the user completes those from the desktop app.
176
+ When `run` completes, tell the user their Template box is ready, using the
177
+ options it prints. If any imported MCP servers need re-authentication, the
178
+ remote setup notes them — the user completes those from the desktop app.
155
179
 
156
180
  If anything fails, see `guide recovery` — setup is resumable at every stage.