@boxes-dev/dvb-runtime 1.0.1098 → 1.0.1099

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 (31) hide show
  1. package/dist/agent-init-guides/git-ssh.md +2 -2
  2. package/dist/bin/dvb.mjs +14 -14
  3. package/dist/bin/dvbd.mjs +4 -4
  4. package/dist/product-docs/references/agent-tools.md +6 -7
  5. package/dist/product-docs/references/automations.md +4 -4
  6. package/dist/product-docs/references/aws.md +17 -11
  7. package/dist/product-docs/references/billing-and-limits.md +23 -11
  8. package/dist/product-docs/references/cli.md +14 -15
  9. package/dist/product-docs/references/core-concepts.md +35 -30
  10. package/dist/product-docs/references/desktop-workbench.md +24 -24
  11. package/dist/product-docs/references/files-git-and-review.md +14 -15
  12. package/dist/product-docs/references/fork-workflows.md +20 -19
  13. package/dist/product-docs/references/getting-started.md +7 -8
  14. package/dist/product-docs/references/glossary.md +46 -22
  15. package/dist/product-docs/references/google-cloud.md +13 -8
  16. package/dist/product-docs/references/index.md +18 -16
  17. package/dist/product-docs/references/linear.md +2 -2
  18. package/dist/product-docs/references/managed-environment-files.md +1 -1
  19. package/dist/product-docs/references/member-managed-files.md +4 -4
  20. package/dist/product-docs/references/mobile.md +18 -16
  21. package/dist/product-docs/references/onbox-agent-tools.md +25 -26
  22. package/dist/product-docs/references/ports-terminal-and-runtime.md +27 -28
  23. package/dist/product-docs/references/project-setup.md +9 -9
  24. package/dist/product-docs/references/security-and-data.md +10 -10
  25. package/dist/product-docs/references/slack.md +3 -3
  26. package/dist/product-docs/references/tailscale.md +2 -2
  27. package/dist/product-docs/references/team-template.md +22 -22
  28. package/dist/product-docs/references/template-box-environment.md +7 -3
  29. package/dist/product-docs/references/threads-and-agents.md +41 -22
  30. package/dist/product-docs/references/troubleshooting.md +24 -25
  31. package/package.json +2 -2
@@ -46,12 +46,12 @@ and choose **Retry now**.
46
46
 
47
47
  If the selected Template box, devbox, or agent seems like it is in a bad state,
48
48
  use **Machine > Reset** from the menu bar. Reset kills all non-essential
49
- processes on the selected machine and restarts the boxes.dev daemon.
49
+ processes on the selected box and restarts the boxes.dev daemon.
50
50
 
51
51
  If Reset does not recover a running machine, use **Machine > Reboot** only as a
52
52
  last resort. Reboot preserves files but stops every process, terminal, agent
53
53
  session, background command, user service, and network connection before
54
- starting the exact selected machine again. boxes.dev reports success only after
54
+ starting the exact selected box again. boxes.dev reports success only after
55
55
  the machine is running and a fresh boxes.dev service heartbeat arrives.
56
56
 
57
57
  If reboot says the machine is sleeping, its files were preserved but startup
@@ -64,7 +64,7 @@ Signing in again should return you to the main workbench page.
64
64
 
65
65
  If you closed the main window, reopen it with **File > Show Workbench**.
66
66
 
67
- If the selected machine's CPU or RAM is pegged and the app feels frozen, click
67
+ If the selected box's CPU or RAM is pegged and the app feels frozen, click
68
68
  the CPU/Mem indicator to open an Activity Monitor-style view and kill the
69
69
  runaway processes. boxes.dev reserves some resources for control, so this works
70
70
  even when agent or user processes are stuck. If it still does not recover, use
@@ -153,9 +153,9 @@ project folder but rebuilds the setup state and bundle.
153
153
  If billing failed during setup, open billing, add or update the payment method,
154
154
  then retry setup.
155
155
 
156
- ## Team Template Member Project Is Not Ready
156
+ ## Managed project is not ready
157
157
 
158
- A Team Template member project must confirm required GitHub repository access
158
+ A managed project must confirm required GitHub repository access
159
159
  and prepare at least one real devbox before it can open. If it shows **GitHub
160
160
  access needs review**, use **Review GitHub access**, reconnect the intended
161
161
  GitHub account or grant the boxes.dev App access to every named repository, and
@@ -217,8 +217,7 @@ connectors** is on. Start a new Claude session after changing either.
217
217
 
218
218
  If an MCP server needs auth, open **Integrations → MCPs** and use the agent chip
219
219
  on that connection. In a project with a Template box, MCP servers installed
220
- directly there are under **Template-managed MCPs** in the same place. Team
221
- Template member projects omit that inventory. If sign-in fails, follow the
220
+ directly there are under **Template-managed MCPs** in the same place. Managed projects omit that inventory. If sign-in fails, follow the
222
221
  recovery message on that MCP's card.
223
222
 
224
223
  Without the desktop app, use **MCPs** on the boxes.dev website instead. If
@@ -280,7 +279,7 @@ Codex failure cards distinguish several failure layers so the recovery step
280
279
  matches what happened:
281
280
 
282
281
  - Selected-model capacity and temporary provider throttling come from the model
283
- provider, not the selected machine. When the selected model is at capacity,
282
+ provider, not the selected box. When the selected model is at capacity,
284
283
  boxes.dev continues the thread automatically after a short wait, with longer
285
284
  waits if capacity stays limited, and sends no failure notification while it
286
285
  does. If the card asks you to reply, boxes.dev has stopped trying: continue
@@ -288,7 +287,7 @@ matches what happened:
288
287
  continue after a short wait.
289
288
  - Codex credits and authentication are account problems. Add or wait for
290
289
  credits, or reconnect Codex before continuing.
291
- - A box networking card means the selected machine could not reach the model
290
+ - A box networking card means the selected box could not reach the model
292
291
  provider. Continue after connectivity recovers.
293
292
  - Codex internal, rejected-request, and execution-sandbox cards identify a
294
293
  failure inside the Codex execution path. Review any available detail before
@@ -304,7 +303,7 @@ delivered is a separate recovery action.
304
303
 
305
304
  Devbox starts can fail because billing blocks compute, the awake devbox limit is
306
305
  reached, the selected snapshot or Team Template saved version is unavailable,
307
- or the runtime could not be prepared.
306
+ or the box could not be prepared.
308
307
 
309
308
  Sometimes a devbox fails to start because the underlying infrastructure provider
310
309
  is temporarily slow or unavailable. This is usually recoverable. Retry
@@ -319,18 +318,18 @@ failed, the thread action menu can offer **Move back to Template box**.
319
318
  If the failure persists after retrying and no billing or awake devbox limit is
320
319
  shown, contact support with the thread, project, and approximate time.
321
320
 
322
- ## Sleeping Or Waking Runtime
321
+ ## Sleeping or waking box
323
322
 
324
323
  When a Template box or devbox is sleeping, files, git, terminal, and ports may
325
324
  show a wake prompt. Use **Wake Template box** or **Wake devbox**.
326
325
 
327
- When a runtime is waking, wait for the selected surface to reload. The terminal,
328
- files, git status, and ports load after the runtime is ready.
326
+ When a box is waking, wait for the selected surface to reload. The terminal,
327
+ files, git status, and ports load after the box is ready.
329
328
 
330
329
  Waking can sometimes take many seconds or even a few minutes because of the
331
- underlying infrastructure provider. If the wake attempt fails, the runtime
330
+ underlying infrastructure provider. If the wake attempt fails, the box
332
331
  returns to Sleeping instead of retrying continuously. With auto-wake on,
333
- returning to the runtime after 15 minutes can make one new wake attempt. Use the
332
+ returning to the box after 15 minutes can make one new wake attempt. Use the
334
333
  explicit **Wake Template box** or **Wake devbox** action to retry sooner. If
335
334
  repeated wake attempts fail and no billing or capacity block is shown, contact
336
335
  support with the project and approximate time.
@@ -338,35 +337,35 @@ support with the project and approximate time.
338
337
  If a devbox cannot wake because the awake devbox limit is reached, sleep another
339
338
  devbox first or adjust billing/plan capacity if available.
340
339
 
341
- If a recovery notice says the selected machine recovered after an unexpected
340
+ If a recovery notice says the selected box recovered after an unexpected
342
341
  stop or timeout, recent changes after the restored snapshot may be missing.
343
342
  Inspect git status and files before continuing.
344
343
 
345
344
  ## Ports Missing Or Not Forwarded
346
345
 
347
- The ports menu follows the selected runtime. If the wrong thread, devbox, or
346
+ The ports menu follows the selected box. If the wrong thread, devbox, or
348
347
  Template box is selected, the ports menu may appear empty or show ports for a
349
- different runtime.
348
+ different box.
350
349
 
351
- If the selected runtime is sleeping, wake it before inspecting ports.
350
+ If the selected box is sleeping, wake it before inspecting ports.
352
351
 
353
- If the ports menu says it is waiting for the selected runtime or waiting for an
354
- initial port snapshot, give the runtime a moment to report running services.
352
+ If the ports menu says it is waiting for the selected box or waiting for an
353
+ initial port snapshot, give the box a moment to report running services.
355
354
 
356
355
  If a visible port is not forwarded because the local port is already in use,
357
356
  use **Use next available** when offered, or stop the local process that is
358
357
  holding the port.
359
358
 
360
359
  If there are no forwarded ports, make sure the app or service is actually
361
- running inside the selected runtime.
360
+ running inside the selected box.
362
361
 
363
362
  ## Files Or Git Will Not Load
364
363
 
365
- Files and git status require the selected runtime to be awake. Wake the runtime
364
+ Files and git status require the selected box to be awake. Wake the box
366
365
  first.
367
366
 
368
367
  If the file viewer or git view still does not load, check that the selected
369
- runtime is the one that contains the work. Devbox files and Template box files
368
+ box is the one that contains the work. Devbox files and Template box files
370
369
  are separate after the devbox is created.
371
370
 
372
371
  If Git can inspect local files but an automatic GitHub fetch, pull, or push is
@@ -378,7 +377,7 @@ check again, or use SSH. Ordinary automatic fetch, pull, and push can still
378
377
  work while that workflow permission is pending.
379
378
 
380
379
  If work appears missing after a recovery notice, inspect git status and recent
381
- files on that runtime. Changes made after the restored snapshot may need to be
380
+ files on that box. Changes made after the restored snapshot may need to be
382
381
  recreated from git, agent output, or local notes.
383
382
 
384
383
  ## Git Commit Uses The Wrong Author
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@boxes-dev/dvb-runtime",
3
- "version": "1.0.1098",
3
+ "version": "1.0.1099",
4
4
  "description": "Runtime for the boxes.dev CLI. Install @boxes-dev/dvb to use the CLI.",
5
5
  "homepage": "https://boxes.dev",
6
6
  "type": "module",
@@ -77,5 +77,5 @@
77
77
  "e2b": "^2.18.0",
78
78
  "ink-testing-library": "^4.0.0"
79
79
  },
80
- "devboxReleasedAt": "2026-10-20T04:54:57Z"
80
+ "devboxReleasedAt": "2026-10-20T19:22:41Z"
81
81
  }