@boxes-dev/dvb-runtime 1.0.1012 → 1.0.1015
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/dist/agent-init-guides/env-files.md +29 -3
- package/dist/agent-init-guides/flow.md +14 -1
- package/dist/agent-init-guides/manifest.md +4 -0
- package/dist/bin/dvb.mjs +2046 -1961
- package/dist/bin/dvbd.mjs +8 -8
- package/dist/product-docs/SKILL.md +4 -0
- package/dist/product-docs/references/agent-tools.md +3 -3
- package/dist/product-docs/references/automations.md +10 -6
- package/dist/product-docs/references/aws.md +4 -3
- package/dist/product-docs/references/billing-and-limits.md +6 -4
- package/dist/product-docs/references/core-concepts.md +3 -3
- package/dist/product-docs/references/desktop-workbench.md +17 -4
- package/dist/product-docs/references/environment-setup-validation.md +44 -0
- package/dist/product-docs/references/files-git-and-review.md +46 -11
- package/dist/product-docs/references/fork-workflows.md +21 -9
- package/dist/product-docs/references/glossary.md +5 -2
- package/dist/product-docs/references/index.md +9 -3
- package/dist/product-docs/references/linear.md +10 -7
- package/dist/product-docs/references/member-managed-files.md +5 -2
- package/dist/product-docs/references/mobile.md +9 -4
- package/dist/product-docs/references/onbox-agent-tools.md +102 -40
- package/dist/product-docs/references/ports-terminal-and-runtime.md +24 -9
- package/dist/product-docs/references/project-setup.md +8 -0
- package/dist/product-docs/references/security-and-data.md +43 -26
- package/dist/product-docs/references/slack.md +45 -15
- package/dist/product-docs/references/tailscale.md +3 -0
- package/dist/product-docs/references/team-template.md +30 -41
- package/dist/product-docs/references/template-box-environment.md +5 -0
- package/dist/product-docs/references/threads-and-agents.md +38 -15
- package/dist/product-docs/references/troubleshooting.md +35 -26
- package/package.json +2 -2
|
@@ -129,29 +129,27 @@ script row states its timing, the directory it runs in, and the template's
|
|
|
129
129
|
repository paths, and each script is edited in place with **Add script** or
|
|
130
130
|
**Edit script**, then **Save script** or **Cancel**.
|
|
131
131
|
|
|
132
|
-
|
|
133
|
-
version contains exactly one repository
|
|
134
|
-
|
|
135
|
-
|
|
132
|
+
For managed projects, both startup scripts run inside the repository when the
|
|
133
|
+
saved version contains exactly one repository. With zero or multiple
|
|
134
|
+
repositories, they run in the project root, normally `/home/boxes`.
|
|
135
|
+
Teardown scripts continue to run in the project root.
|
|
136
136
|
|
|
137
137
|
For a managed template the startup sequence is:
|
|
138
138
|
|
|
139
|
-
1. Start from the saved template.
|
|
140
|
-
2.
|
|
141
|
-
|
|
142
|
-
|
|
143
|
-
|
|
144
|
-
|
|
145
|
-
|
|
146
|
-
|
|
147
|
-
|
|
148
|
-
5. **Member startup script** (default for new projects). It runs once per new
|
|
149
|
-
devbox, before the first agent turn, with the member's configured GitHub
|
|
150
|
-
access and files ready. It is copied into each new project, and members
|
|
151
|
-
edit their own copy afterward; saving the default does not change existing
|
|
152
|
-
projects. A failure shows a warning and the devbox still starts.
|
|
139
|
+
1. Start from the saved template and prepare the member's durable environment.
|
|
140
|
+
2. The prepared devbox may wait until that member needs it.
|
|
141
|
+
3. boxes.dev checks the member's configured connections and files.
|
|
142
|
+
4. **Team startup script** (optional, team-owned). It runs with the same member
|
|
143
|
+
environment as the member startup script, immediately before it. Saving
|
|
144
|
+
applies to future devboxes for every managed project using the template.
|
|
145
|
+
5. **Member startup script** (default for new projects). It is copied into each
|
|
146
|
+
new project, and members edit their own copy afterward; saving the default
|
|
147
|
+
does not change existing projects.
|
|
153
148
|
6. The first agent turn starts.
|
|
154
149
|
|
|
150
|
+
A script error or timeout shows a warning. The next script and agent still
|
|
151
|
+
start, and other members can continue creating devboxes.
|
|
152
|
+
|
|
155
153
|
An independent template shows the same sequence without the team stages,
|
|
156
154
|
starting from the project's own Template box. Another thread on an existing
|
|
157
155
|
devbox, or waking one, does not run the sequence again.
|
|
@@ -162,14 +160,13 @@ Each devbox runs the team teardown captured when it was prepared; saving that
|
|
|
162
160
|
script applies to later preparations. Unused or failed preparations may skip
|
|
163
161
|
the member teardown script.
|
|
164
162
|
|
|
165
|
-
|
|
166
|
-
|
|
167
|
-
|
|
168
|
-
|
|
169
|
-
|
|
163
|
+
Team startup failures appear on the affected member's devbox, with details
|
|
164
|
+
collapsed until opened. Admins can choose **Review startup script**; other
|
|
165
|
+
members can contact their team admin. Saving a correction applies to future
|
|
166
|
+
devboxes and does not rerun startup on the current one.
|
|
167
|
+
|
|
168
|
+
Team teardown failures remain available on the template page. Saving a script
|
|
170
169
|
records it; it does not run it or publish a new saved version.
|
|
171
|
-
When a later run of the same saved team script succeeds, its earlier failure
|
|
172
|
-
disappears from the page.
|
|
173
170
|
|
|
174
171
|
## Environment And Member Files
|
|
175
172
|
|
|
@@ -306,7 +303,7 @@ When editing is finished, choose one of these actions:
|
|
|
306
303
|
are saved before teardown. The confirmation requires typing `DISCARD`.
|
|
307
304
|
|
|
308
305
|
Members can continue creating projects from the current saved version while an
|
|
309
|
-
admin edits a future version. Admins can choose **
|
|
306
|
+
admin edits a future version. Admins can choose **Restore this version** for an
|
|
310
307
|
older ready version under **Previous versions**. boxes.dev prepares that saved
|
|
311
308
|
environment in the background and keeps the current version active until the
|
|
312
309
|
older one is ready; the page shows preparation progress or a retryable failure.
|
|
@@ -362,21 +359,13 @@ the only startup status. Once the thread is running, only failed per-devbox
|
|
|
362
359
|
setup such as Tailscale appears above the composer; setup that is still applying
|
|
363
360
|
stays in the background without an extra checklist.
|
|
364
361
|
|
|
365
|
-
If the
|
|
366
|
-
|
|
367
|
-
|
|
368
|
-
|
|
369
|
-
|
|
370
|
-
|
|
371
|
-
|
|
372
|
-
After repeated startup failures, **Devbox creation is paused** will explain
|
|
373
|
-
why new devboxes cannot start. A team admin can use **Review startup script**
|
|
374
|
-
to open the **Team preparation script** under **When a new devbox is created**,
|
|
375
|
-
review it, and use **Retry saved script**.
|
|
376
|
-
Your draft and attachments will remain available while the team resolves it.
|
|
377
|
-
|
|
378
|
-
If boxes.dev cannot prepare the saved template or finish setup after the startup
|
|
379
|
-
script succeeds, the notice will explain which part failed. Open **View details**
|
|
362
|
+
If the team startup script fails or times out, the devbox still starts. Its
|
|
363
|
+
warning identifies the team script and lets you open or copy its details.
|
|
364
|
+
Admins can choose **Review startup script**; other members should contact
|
|
365
|
+
their team admin. A member startup failure has its own result, so both remain
|
|
366
|
+
inspectable if both scripts fail.
|
|
367
|
+
|
|
368
|
+
If boxes.dev cannot prepare the saved template or finish setup, the notice will explain which part failed. Open **View details**
|
|
380
369
|
and use **Copy details** to share the diagnostic with your team admin or boxes.dev
|
|
381
370
|
support. These setup errors do not necessarily mean the startup script needs to
|
|
382
371
|
change. If waiting for preparation times out, the notice will say that completion
|
|
@@ -30,6 +30,11 @@ and install only the missing dependencies the project needs.
|
|
|
30
30
|
|
|
31
31
|
## Development-Environment Setup
|
|
32
32
|
|
|
33
|
+
For setup and repairs, follow
|
|
34
|
+
[Development environment validation](environment-setup-validation.md) alongside
|
|
35
|
+
the current thread's setup plan. It covers persistent tool activation, fresh
|
|
36
|
+
agent and terminal checks, service startup, and reporting unfinished work.
|
|
37
|
+
|
|
33
38
|
Treat Template box setup as environment work, not application feature work.
|
|
34
39
|
Read the repository's own documentation and configuration, determine the
|
|
35
40
|
relevant run path, and use the package manager and toolchain the project
|
|
@@ -221,13 +221,15 @@ and the destination devbox enrolls with its own identity.
|
|
|
221
221
|
|
|
222
222
|
Open **Integrations → MCPs** in the desktop app to manage remote MCP servers in
|
|
223
223
|
one list. Choose **Add MCP**, then paste either the server URL or the Codex or
|
|
224
|
-
Claude setup command supplied by the provider
|
|
224
|
+
Claude setup command supplied by the provider, and choose **Continue**.
|
|
225
|
+
boxes.dev detects the supported
|
|
225
226
|
remote transport and the authentication method, so the form asks only for the
|
|
226
227
|
name, the scope, and which agents to add the connection to. The URL, the
|
|
227
228
|
authentication mode, and the name the agents use sit under **Advanced**, which
|
|
228
229
|
opens on its own when a header or API key still has to be typed in. New
|
|
229
230
|
connections default to **This project**; choose **All projects** only when the
|
|
230
|
-
same server and account should be available everywhere.
|
|
231
|
+
same server and account should be available everywhere. Choose the agents under
|
|
232
|
+
**Add to**, then choose **Add MCP** to save and authorize the connection.
|
|
231
233
|
|
|
232
234
|
Codex and Claude are enabled independently from the same connection row. OAuth
|
|
233
235
|
opens a local browser sign-in for the selected agent, so enabling both agents
|
|
@@ -243,7 +245,14 @@ a command such as `codex mcp add <name> --url <url>` or `claude mcp add
|
|
|
243
245
|
--transport http <name> <url>` in a Template box or devbox creates the central
|
|
244
246
|
current-project connection and continues authorization through the desktop app
|
|
245
247
|
or the shown local-computer instructions. It does not create a separate
|
|
246
|
-
machine-only copy.
|
|
248
|
+
machine-only copy. To enable both agents, run each agent's setup command with
|
|
249
|
+
the same name, URL, and authentication details, including any API-key headers.
|
|
250
|
+
The second command will add its agent to the existing project connection;
|
|
251
|
+
repeating either command will keep the existing connection and sign-in. OAuth
|
|
252
|
+
still requires authorization for each agent. For an **All projects** connection
|
|
253
|
+
or different settings under the same name, use the existing row's agent button
|
|
254
|
+
in **Integrations → MCPs**, or choose another name for a separate connection.
|
|
255
|
+
Unsupported transports and options, including local `stdio`,
|
|
247
256
|
legacy SSE, and custom OAuth clients, continue through the native agent command
|
|
248
257
|
and remain **Template-managed**. Run those commands on the Template box and take
|
|
249
258
|
a snapshot if future devboxes need that local setup.
|
|
@@ -416,8 +425,10 @@ boxes.dev applies the new sign-in to every devbox and the notice clears on its
|
|
|
416
425
|
own. For an MCP installed directly on the Template box, reauthorize it under
|
|
417
426
|
**Template-managed MCPs**, then take a snapshot so new devboxes will have it;
|
|
418
427
|
existing devboxes keep running without that MCP. In a Team Template member
|
|
419
|
-
project, a Template admin
|
|
420
|
-
|
|
428
|
+
project, a Template admin repairs a machine-local MCP inherited in the saved
|
|
429
|
+
environment. Centrally managed definitions copied from Team Template defaults
|
|
430
|
+
still use the member's own per-agent sign-in and **Reauthorize** action.
|
|
431
|
+
Dismissing the notice hides that MCP server's warning for every
|
|
421
432
|
devbox in the project, including after reloads. The warning will return if the
|
|
422
433
|
server starts successfully and its authorization expires again. boxes.dev does
|
|
423
434
|
not show raw MCP startup errors in the thread.
|
|
@@ -453,7 +464,8 @@ When the agent is working, the composer may stay available for follow-ups. Some
|
|
|
453
464
|
follow-ups are queued and delivered after the current turn. They stay in the
|
|
454
465
|
same user-bubble queue used during startup and reconnect. Queued follow-ups can
|
|
455
466
|
be edited, deleted, or restored. During an active Codex turn, `Steer now`
|
|
456
|
-
|
|
467
|
+
interrupts the current turn and starts the oldest queued follow-up. Remaining
|
|
468
|
+
messages stay queued in order.
|
|
457
469
|
|
|
458
470
|
For Claude, choose **Queue** to wait for the current work to finish or **Steer**
|
|
459
471
|
to send a correction without interrupting a running tool. Claude will use a
|
|
@@ -468,14 +480,21 @@ An idle thread starts normally with either preference. Once Claude accepts a
|
|
|
468
480
|
steer, it cannot be edited or deleted as a waiting Queue message.
|
|
469
481
|
|
|
470
482
|
The desktop and mobile composers also stay available while Codex or Claude
|
|
471
|
-
Code is starting, reconnecting, or preparing a new fork.
|
|
472
|
-
|
|
473
|
-
|
|
474
|
-
|
|
475
|
-
|
|
476
|
-
|
|
477
|
-
|
|
478
|
-
the
|
|
483
|
+
Code is starting, reconnecting, or preparing a new fork. On desktop, sending to
|
|
484
|
+
an existing thread on a sleeping box will wake the box and use the same queue.
|
|
485
|
+
Messages sent during that wait appear as regular queued bubbles and send
|
|
486
|
+
automatically in order once the agent is ready. Supported images and files stay
|
|
487
|
+
attached to their queued message. boxes.dev stores waiting messages before
|
|
488
|
+
handing them to the runtime, so delivery after server receipt does not depend
|
|
489
|
+
on keeping the app open.
|
|
490
|
+
Keep the app open until any attachment uploads finish and the message reaches
|
|
491
|
+
the server; messages saved only on your device will resume when you reopen
|
|
492
|
+
their thread. If startup or connection fails, messages that have not reached
|
|
493
|
+
the runtime return to the composer as one draft, separated by newlines, with
|
|
494
|
+
attachments restored when the current client supports them. Use **Stop** to
|
|
495
|
+
return waiting messages to your draft, including while attachments upload.
|
|
496
|
+
If you quit before an upload finishes, you may need to attach the files again;
|
|
497
|
+
boxes.dev will name any attachments it couldn't restore.
|
|
479
498
|
|
|
480
499
|
If a direct Claude Code message fails after leaving the composer, its failed
|
|
481
500
|
bubble can be deleted from the live tail. When boxes.dev can prove that Claude
|
|
@@ -767,13 +786,17 @@ Interrupting asks the agent to stop the current turn. It does not delete the
|
|
|
767
786
|
thread. After a turn stops, the user can send another prompt, inspect changes,
|
|
768
787
|
or decide whether to keep or discard the devbox.
|
|
769
788
|
|
|
770
|
-
|
|
789
|
+
On desktop, stopping also returns queued messages that have not reached the runtime to the
|
|
771
790
|
current composer as one editable draft, with their attachments. Messages
|
|
772
791
|
already accepted by the runtime remain there so they are not sent twice, and
|
|
773
792
|
the next one starts as soon as the stopped turn finishes settling. To keep
|
|
774
793
|
those from running, delete them individually or use the control that returns
|
|
775
794
|
all queued prompts to the composer before the turn settles.
|
|
776
795
|
|
|
796
|
+
On mobile, Stop returns undelivered Claude messages to the composer but leaves
|
|
797
|
+
undelivered Codex messages pending. Codex follow-ups already accepted into its
|
|
798
|
+
Queue remain queued on both surfaces and can start after the interrupted turn.
|
|
799
|
+
|
|
777
800
|
Claude steers already accepted by Claude are different: Stop may leave them
|
|
778
801
|
waiting for Claude's next response, and they cannot be taken back through the
|
|
779
802
|
Queue controls. A steer that Claude already read remains in the thread even
|
|
@@ -22,7 +22,8 @@ the existing setup state.
|
|
|
22
22
|
|
|
23
23
|
## Desktop App Looks Stale Or Stuck
|
|
24
24
|
|
|
25
|
-
The desktop app's
|
|
25
|
+
The desktop app's **Help and feedback** button beside the account menu at the
|
|
26
|
+
bottom of the sidebar lists the most
|
|
26
27
|
common quick fixes; the steps below match what it shows.
|
|
27
28
|
|
|
28
29
|
If thread content or another desktop view looks stale, stuck, or slightly
|
|
@@ -71,10 +72,13 @@ If remote setup pauses at a recoverable step, the setup UI can offer **Retry
|
|
|
71
72
|
setup**. Use that when the issue looks temporary or the UI says the step is
|
|
72
73
|
retryable.
|
|
73
74
|
|
|
74
|
-
|
|
75
|
-
|
|
76
|
-
|
|
77
|
-
|
|
75
|
+
For a local-folder setup's remote Git access failure, choose **Fix Git access**.
|
|
76
|
+
boxes.dev removes the incomplete Template box and returns to Finalize Bundle,
|
|
77
|
+
keeping the approved review and other bundle choices. Restore the named GitHub
|
|
78
|
+
account's repository access, switch to and verify SSH, or skip Git access before
|
|
79
|
+
continuing. For SSH, register the displayed public key with the Git host and
|
|
80
|
+
verify it. Use **Rebuild bundle** when setup specifically asks to prepare the
|
|
81
|
+
upload again; deleting the project is not required for Git repair.
|
|
78
82
|
|
|
79
83
|
If Create from GitHub's automatic access cannot clone a selected repository,
|
|
80
84
|
follow the specific recovery shown: reconnect the GitHub account used for the
|
|
@@ -102,12 +106,14 @@ GitHub account or grant the boxes.dev App access to every named repository, and
|
|
|
102
106
|
then retry. boxes.dev does not switch to an older Team Template saved version
|
|
103
107
|
or to SSH for this project type.
|
|
104
108
|
|
|
105
|
-
|
|
106
|
-
|
|
107
|
-
|
|
108
|
-
|
|
109
|
-
|
|
110
|
-
|
|
109
|
+
Team startup scripts run after Send, once the member's files and credentials
|
|
110
|
+
are ready. A script failure or timeout shows a warning; the member's own
|
|
111
|
+
startup script and agent turn continue. Open **View details** and use **Copy
|
|
112
|
+
details** to share the failure with a team admin. An admin can choose **Review
|
|
113
|
+
startup script** and correct it under **When a new devbox is created**.
|
|
114
|
+
Corrections apply to future devboxes; saving does not rerun the script on the
|
|
115
|
+
current machine. A startup-script warning does not pause devbox creation or
|
|
116
|
+
block other members.
|
|
111
117
|
|
|
112
118
|
Optional setup such as an MCP connection can warn without blocking the first
|
|
113
119
|
thread. Follow the warning's own sign-in or retry action. GitHub access needed
|
|
@@ -246,7 +252,7 @@ If the ports menu says it is waiting for the selected runtime or waiting for an
|
|
|
246
252
|
initial port snapshot, give the runtime a moment to report running services.
|
|
247
253
|
|
|
248
254
|
If a visible port is not forwarded because the local port is already in use,
|
|
249
|
-
use **Use next available
|
|
255
|
+
use **Use next available** when offered, or stop the local process that is
|
|
250
256
|
holding the port.
|
|
251
257
|
|
|
252
258
|
If there are no forwarded ports, make sure the app or service is actually
|
|
@@ -276,9 +282,11 @@ recreated from git, agent output, or local notes.
|
|
|
276
282
|
## Git Commit Uses The Wrong Author
|
|
277
283
|
|
|
278
284
|
Open Account settings to inspect or edit the boxes.dev **Git identity**
|
|
279
|
-
fallback.
|
|
280
|
-
|
|
281
|
-
|
|
285
|
+
fallback. Unless you saved an override, it comes from your connected GitHub
|
|
286
|
+
account's name and private no-reply email. Save an edit here if you prefer
|
|
287
|
+
another commit identity. If Account reports a failed update for a saved
|
|
288
|
+
override, use **Retry**. GitHub defaults retry automatically. Sleeping
|
|
289
|
+
machines stay asleep and retry on their next normal wake.
|
|
282
290
|
|
|
283
291
|
An imported or later-written `~/.gitconfig` identity intentionally overrides
|
|
284
292
|
the Account fallback for that machine. A repository-local identity overrides
|
|
@@ -307,18 +315,19 @@ commands become available.
|
|
|
307
315
|
When the setting is on and the current project's repository access is ready,
|
|
308
316
|
do not repair authentication by running `gh auth login`, `gh auth logout`, `gh
|
|
309
317
|
auth refresh`, or `gh auth switch`; manage that identity from boxes.dev. When
|
|
310
|
-
the setting is off, GitHub is not connected to boxes.dev, or the App
|
|
311
|
-
access
|
|
312
|
-
configuration and environment instead. In the
|
|
313
|
-
to run `gh auth login` on that machine.
|
|
314
|
-
automatic Git fetch, pull, or push for a
|
|
315
|
-
method.
|
|
318
|
+
the setting is off, GitHub is not connected to boxes.dev, or neither the App nor
|
|
319
|
+
authorized personal access can reach every known repository in this project,
|
|
320
|
+
`gh` uses its ordinary local configuration and environment instead. In the
|
|
321
|
+
missing-access case, it is safe to run `gh auth login` on that machine.
|
|
322
|
+
Disabling GitHub CLI does not disable automatic Git fetch, pull, or push for a
|
|
323
|
+
project that uses that separate access method.
|
|
316
324
|
|
|
317
325
|
If a repository or API request is still rejected while `gh` is enabled, use
|
|
318
|
-
**Manage repository access** to
|
|
319
|
-
|
|
320
|
-
|
|
321
|
-
|
|
326
|
+
**Manage repository access** to check App access, and reconnect GitHub if the
|
|
327
|
+
page requests it. If your organization cannot approve the App, choose **Use
|
|
328
|
+
personal access** and authorize the official GitHub CLI. boxes.dev can manage
|
|
329
|
+
the CLI identity only when either the App or personal authorization can access
|
|
330
|
+
every known repository in the project.
|
|
322
331
|
|
|
323
332
|
## Billing Or Limit Blocks
|
|
324
333
|
|
|
@@ -402,7 +411,7 @@ triggers depend on a healthy workspace connection and linked user identity.
|
|
|
402
411
|
|
|
403
412
|
## When To Contact Support
|
|
404
413
|
|
|
405
|
-
Contact
|
|
414
|
+
Contact hi@boxes.dev when:
|
|
406
415
|
|
|
407
416
|
- Setup repeatedly fails after retrying upload/setup or starting over.
|
|
408
417
|
- A Template box or devbox cannot wake and no billing or capacity fix is
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@boxes-dev/dvb-runtime",
|
|
3
|
-
"version": "1.0.
|
|
3
|
+
"version": "1.0.1015",
|
|
4
4
|
"type": "module",
|
|
5
5
|
"license": "UNLICENSED",
|
|
6
6
|
"imports": {
|
|
@@ -77,5 +77,5 @@
|
|
|
77
77
|
"e2b": "^2.18.0",
|
|
78
78
|
"ink-testing-library": "^4.0.0"
|
|
79
79
|
},
|
|
80
|
-
"devboxReleasedAt": "2026-09-
|
|
80
|
+
"devboxReleasedAt": "2026-09-21T19:26:25Z"
|
|
81
81
|
}
|