@boxes-dev/dvb-runtime 1.0.1098 → 1.0.1100

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 (66) hide show
  1. package/dist/agent-init-guides/git-ssh.md +2 -2
  2. package/dist/bin/dvb.mjs +121 -72
  3. package/dist/bin/dvbd.mjs +6 -6
  4. package/dist/postgres-tools/SHA256SUMS +32 -8
  5. package/dist/postgres-tools/linux-arm64-el8/bin/pg_dump +0 -0
  6. package/dist/postgres-tools/linux-arm64-el8/bin/pg_restore +0 -0
  7. package/dist/postgres-tools/linux-arm64-el8/lib/libpq.so.5 +0 -0
  8. package/dist/postgres-tools/linux-arm64-el8/notices/PostgreSQL-COPYRIGHT.txt +23 -0
  9. package/dist/postgres-tools/linux-arm64-el9/bin/pg_dump +0 -0
  10. package/dist/postgres-tools/linux-arm64-el9/bin/pg_restore +0 -0
  11. package/dist/postgres-tools/linux-arm64-el9/lib/libpq.so.5 +0 -0
  12. package/dist/postgres-tools/linux-arm64-el9/notices/PostgreSQL-COPYRIGHT.txt +23 -0
  13. package/dist/postgres-tools/linux-arm64-ubuntu22.04/bin/pg_dump +0 -0
  14. package/dist/postgres-tools/linux-arm64-ubuntu22.04/bin/pg_restore +0 -0
  15. package/dist/postgres-tools/linux-arm64-ubuntu22.04/lib/libpq.so.5 +0 -0
  16. package/dist/postgres-tools/linux-x64-el8/bin/pg_dump +0 -0
  17. package/dist/postgres-tools/linux-x64-el8/bin/pg_restore +0 -0
  18. package/dist/postgres-tools/linux-x64-el8/lib/libpq.so.5 +0 -0
  19. package/dist/postgres-tools/linux-x64-el8/notices/PostgreSQL-COPYRIGHT.txt +23 -0
  20. package/dist/postgres-tools/linux-x64-el9/bin/pg_dump +0 -0
  21. package/dist/postgres-tools/linux-x64-el9/bin/pg_restore +0 -0
  22. package/dist/postgres-tools/linux-x64-el9/lib/libpq.so.5 +0 -0
  23. package/dist/postgres-tools/linux-x64-el9/notices/PostgreSQL-COPYRIGHT.txt +23 -0
  24. package/dist/postgres-tools/linux-x64-ubuntu22.04/bin/pg_dump +0 -0
  25. package/dist/postgres-tools/linux-x64-ubuntu22.04/bin/pg_restore +0 -0
  26. package/dist/postgres-tools/linux-x64-ubuntu22.04/lib/libpq.so.5 +0 -0
  27. package/dist/postgres-tools/linux-x64-ubuntu22.04/notices/PostgreSQL-and-Debian-copyright.txt +270 -0
  28. package/dist/postgres-tools/linux-x64-ubuntu24.04/notices/PostgreSQL-and-Debian-copyright.txt +270 -0
  29. package/dist/postgres-tools/release.json +306 -18
  30. package/dist/product-docs/references/agent-tools.md +6 -7
  31. package/dist/product-docs/references/automations.md +4 -4
  32. package/dist/product-docs/references/aws.md +17 -11
  33. package/dist/product-docs/references/billing-and-limits.md +26 -13
  34. package/dist/product-docs/references/cli.md +14 -15
  35. package/dist/product-docs/references/convex.md +92 -0
  36. package/dist/product-docs/references/core-concepts.md +35 -30
  37. package/dist/product-docs/references/desktop-workbench.md +62 -47
  38. package/dist/product-docs/references/files-git-and-review.md +14 -15
  39. package/dist/product-docs/references/fork-workflows.md +26 -25
  40. package/dist/product-docs/references/getting-started.md +11 -12
  41. package/dist/product-docs/references/glossary.md +46 -22
  42. package/dist/product-docs/references/google-cloud.md +13 -8
  43. package/dist/product-docs/references/index.md +20 -16
  44. package/dist/product-docs/references/linear.md +2 -2
  45. package/dist/product-docs/references/managed-environment-files.md +1 -1
  46. package/dist/product-docs/references/member-managed-files.md +4 -4
  47. package/dist/product-docs/references/mobile.md +18 -16
  48. package/dist/product-docs/references/onbox-agent-tools.md +63 -41
  49. package/dist/product-docs/references/ports-terminal-and-runtime.md +31 -28
  50. package/dist/product-docs/references/project-setup.md +15 -12
  51. package/dist/product-docs/references/security-and-data.md +23 -13
  52. package/dist/product-docs/references/slack.md +45 -7
  53. package/dist/product-docs/references/tailscale.md +2 -2
  54. package/dist/product-docs/references/team-template.md +26 -23
  55. package/dist/product-docs/references/template-box-environment.md +7 -3
  56. package/dist/product-docs/references/threads-and-agents.md +48 -24
  57. package/dist/product-docs/references/troubleshooting.md +24 -25
  58. package/package.json +2 -2
  59. /package/dist/postgres-tools/{linux-arm64 → linux-arm64-ubuntu22.04}/notices/PostgreSQL-and-Debian-copyright.txt +0 -0
  60. /package/dist/postgres-tools/{linux-arm64 → linux-arm64-ubuntu24.04}/bin/pg_dump +0 -0
  61. /package/dist/postgres-tools/{linux-arm64 → linux-arm64-ubuntu24.04}/bin/pg_restore +0 -0
  62. /package/dist/postgres-tools/{linux-arm64 → linux-arm64-ubuntu24.04}/lib/libpq.so.5 +0 -0
  63. /package/dist/postgres-tools/{linux-x64 → linux-arm64-ubuntu24.04}/notices/PostgreSQL-and-Debian-copyright.txt +0 -0
  64. /package/dist/postgres-tools/{linux-x64 → linux-x64-ubuntu24.04}/bin/pg_dump +0 -0
  65. /package/dist/postgres-tools/{linux-x64 → linux-x64-ubuntu24.04}/bin/pg_restore +0 -0
  66. /package/dist/postgres-tools/{linux-x64 → linux-x64-ubuntu24.04}/lib/libpq.so.5 +0 -0
@@ -38,9 +38,9 @@ actions name missing files and link back to them.
38
38
 
39
39
  ## Storage And Delivery
40
40
 
41
- boxes.dev encrypts each member file for that exact project. An ordinary project
41
+ boxes.dev encrypts each member file for that exact project. An independent project
42
42
  created from a Team Template receives a frozen, independently encrypted copy.
43
- A Member project continues following the Team Template's current file
43
+ A managed project continues following the Team Template's current file
44
44
  destinations, while each member's bytes remain scoped to their own project.
45
45
 
46
46
  The devbox writes the exact uploaded bytes. Missing parent directories are
@@ -66,7 +66,7 @@ safely does block them until it is fixed, and Project settings explains what
66
66
  the member must do. An agent session that is already running is not stopped
67
67
  when a requirement or file changes.
68
68
 
69
- When an admin changes a Home/Project choice or relative path for a Member
69
+ When an admin changes a Home/Project choice or relative path for a managed
70
70
  project, boxes.dev removes the old managed destination but does not write the
71
71
  saved bytes to the new destination automatically. The member must explicitly
72
72
  choose **Use my saved file at this new destination** or upload a replacement.
@@ -84,7 +84,7 @@ Google account linked to the current boxes.dev account.
84
84
 
85
85
  Central storage contains encrypted bytes, not plaintext or a usable root key.
86
86
  Authorized boxes.dev services can decrypt a file to deliver it to the exact
87
- member project or return it after that member confirms their account. This is
87
+ managed project or return it after that member confirms their account. This is
88
88
  not end-to-end or zero-knowledge encryption.
89
89
 
90
90
  The delivered file is plaintext on the devbox. The project owner, root user,
@@ -83,20 +83,20 @@ Open a project to see its threads. The list can include:
83
83
 
84
84
  Opening the project, browsing its thread history, or editing an unstarted draft
85
85
  does not wake or connect to a machine. Mobile connects only after you open a
86
- live thread that has a runtime, or choose an action such as Send, Terminal,
86
+ live thread that has a box, or choose an action such as Send, Terminal,
87
87
  Browser, Files, snapshot, sleep, or destroy that needs one. A live devbox
88
88
  thread connects to that exact devbox rather than another project machine.
89
89
 
90
90
  Tap the new-thread button to open a new-devbox draft directly. Long-press it
91
- to open the menu with **New thread** and, in an ordinary project,
92
- **New thread on Template box**. A Team Template member project has no template
91
+ to open the menu with **New thread** and, in an independent project,
92
+ **New thread on Template box**. A managed project has no template
93
93
  choice. If the project does not support devboxes, tapping opens a Template-box
94
94
  draft instead. The draft uses the project's last Codex or Claude choice from
95
95
  mobile, desktop, or
96
96
  `dvb agents`, and otherwise uses Codex unless you configured only Claude during
97
97
  desktop setup. Codex and Claude are the agent choices, with no separate Claude
98
98
  CLI thread type for new work. An ordinary new devbox starts from the latest
99
- Template-box snapshot; a member-project devbox starts from the Team Template's
99
+ Template-box snapshot; a managed-project devbox starts from the Team Template's
100
100
  current saved version. Inside an existing devbox group, **New thread** opens a
101
101
  draft directly on that same devbox, where you choose the agent before sending.
102
102
 
@@ -105,15 +105,15 @@ unpinning, marking unread, muting notifications, archiving, unarchiving,
105
105
  deleting when available, and ending live sessions. Eligible Codex and Claude threads on the Template box can
106
106
  be moved to a new devbox after their current turn finishes.
107
107
 
108
- For an ordinary project, from an open Template-box thread, use **New snapshot** in the header overflow
108
+ For an independent project, from an open Template-box thread, use **New snapshot** in the header overflow
109
109
  menu to update the snapshot used by future devboxes. The Template box briefly
110
110
  becomes unavailable while the snapshot is created; the mobile app reports when
111
111
  it succeeds or why it could not start.
112
112
 
113
113
  An archived cold-storage thread stays readable on mobile without waking a
114
- machine. In an ordinary project, use **Restore thread**, then choose **To new
114
+ machine. In an independent project, use **Restore thread**, then choose **To new
115
115
  devbox** to restore from the latest project snapshot or **To Template box** to
116
- use the existing Template-box path. A Team Template member project offers only
116
+ use the existing Template-box path. A managed project offers only
117
117
  **To new devbox** and pins the current Team Template saved version when the
118
118
  restore starts. The restored thread returns directly to the normal thread list.
119
119
 
@@ -133,8 +133,8 @@ notifications** turns them back on.
133
133
  The session view shows the thread transcript and a composer for sending new
134
134
  messages. Archived, cold-storage, and history-only sessions remain read-only
135
135
  from project data until you explicitly restore them. Unstarted drafts remain
136
- editable without a runtime and connect only when you Send. Merely opening any
137
- of these sessions does not wake a runtime. On a new-thread screen, you can
136
+ editable without a box and connect only when you Send. Merely opening any
137
+ of these sessions does not wake a box. On a new-thread screen, you can
138
138
  choose Codex or Claude, add attachments, and tap **Send** immediately while the
139
139
  draft record finishes creating quietly in the background. Claude Code
140
140
  transcripts use the same structured rendering as the
@@ -190,7 +190,7 @@ Close Find with **×** to return to reading or replying.
190
190
 
191
191
  The rate-limit indicator shows the newest reading available for the selected
192
192
  Codex or Claude account. Its last reading remains visible while the thread's
193
- runtime is asleep or disconnected, and updates after boxes.dev receives a
193
+ box is asleep or disconnected, and updates after boxes.dev receives a
194
194
  newer reading.
195
195
 
196
196
  When Codex waits for MCP servers during startup, the startup row names the
@@ -206,7 +206,7 @@ the warning offers **Open MCPs**.
206
206
 
207
207
  After you tap **Send** on an existing managed Codex or Claude thread, you can
208
208
  leave the thread immediately. boxes.dev keeps the follow-up in its delivery
209
- queue while the runtime wakes or the agent accepts it.
209
+ queue while the box wakes or the agent accepts it.
210
210
 
211
211
  Claude follow-ups waiting for the current turn appear at the end of the
212
212
  scrollable transcript. Once a message reaches the devbox, use its delete
@@ -261,7 +261,7 @@ still drafts in the composer so you can send them as soon as the turn finishes
261
261
  stopping.
262
262
 
263
263
  Choose **… → Terminal** in a thread when you need a shell for the
264
- thread's current runtime.
264
+ thread's current box.
265
265
 
266
266
  Choose **… → Agent permissions** in an open thread to view or change what
267
267
  agents on that thread's devbox or Template box can do. Each row shows the
@@ -360,11 +360,11 @@ desktop workbench workflows.
360
360
 
361
361
  ## Terminal
362
362
 
363
- The mobile terminal attaches to the selected thread runtime when terminal
363
+ The mobile terminal attaches to the selected thread's box when terminal
364
364
  access is available. It shows connection states such as opening the shell,
365
- preparing terminal size, connecting, reconnecting, and waking the runtime.
365
+ preparing terminal size, connecting, reconnecting, and waking the box.
366
366
 
367
- If the shell exits, use **Reopen shell**. If the route or runtime target is no
367
+ If the shell exits, use **Reopen shell**. If the route or box target is no
368
368
  longer available, go back to the thread and reopen the terminal.
369
369
 
370
370
  The terminal includes mobile accessory controls for Ctrl, paste, special keys,
@@ -480,6 +480,8 @@ include:
480
480
  - quiet hours, a one-hour notification pause, phone alerts, and unread app icon
481
481
  badge preference;
482
482
  - theme, monospace font, and thread text size;
483
+ - **Sort threads**, the thread list order shared with desktop (see
484
+ `threads-and-agents.md`, Thread List Organization);
483
485
  - release package details and refresh controls in installed builds;
484
486
  - account deletion.
485
487
  - a Help center link that opens the public guides at `https://boxes.dev/help`
@@ -572,7 +574,7 @@ app-store update.
572
574
  ## Mobile Versus Desktop
573
575
 
574
576
  Use desktop for setup, full project orientation, file upload/download workflows,
575
- Git staging and commits, port forwarding, runtime process inspection, and
577
+ Git staging and commits, port forwarding, box process inspection, and
576
578
  detailed review.
577
579
 
578
580
  Use mobile when you want to monitor progress, answer questions, send a quick
@@ -189,7 +189,7 @@ MCPs**. Codex-synced plugins use Codex's own trusted install flow. Local Codex
189
189
  plugins, Claude plugins, and unsupported/local MCPs belong on the Template box
190
190
  when they should become part of future devboxes.
191
191
 
192
- A Team Template member project has no personal Template box. Native-only
192
+ A managed project has no personal Template box. Native-only
193
193
  Plugins and unsupported/local MCPs installed on one of its devboxes stay on
194
194
  that exact devbox; the member cannot publish them into the shared Team
195
195
  Template. Centrally managed project MCPs continue to use **Integrations →
@@ -278,7 +278,7 @@ agent permission defaults (the values in effect, with
278
278
  `permissionDefaultsLockedByTeamTemplate` true when a Team Template locks
279
279
  them), and Claude and Codex agent settings
280
280
  (`agentSettings`, plus the Team Template's read-only `teamAgentSettings` in a
281
- member project). `effectiveGitAction` includes the account's default
281
+ managed project). `effectiveGitAction` includes the account's default
282
282
  when no project preference is set. `autoWake` reports the account-wide
283
283
  preference shown in Project settings. `permissionDefaultsEditable` is always false.
284
284
 
@@ -291,7 +291,7 @@ Older projects without recorded creation inputs report a null origin.
291
291
 
292
292
  Team Template output includes its identity, description, source/repositories,
293
293
  machine size, active saved version, project defaults and save epochs, setup
294
- instructions, integration requirements, member-project policy, cleanup,
294
+ instructions, integration requirements, managed-project policy, cleanup,
295
295
  maintenance and watches, Project URL/MCP definitions, environment definitions,
296
296
  member-file requirements, agent settings, and `agentPermissions` (the saved
297
297
  `policy` with `locked` and `values`, or null before an admin saves one, plus
@@ -313,7 +313,7 @@ grant. An active `edit-template-box` or `edit-team-template` grant also covers
313
313
  that thread's project settings. Team Template writes need team-admin authority
314
314
  and `edit-team-template`, or an existing authorized template editing host or
315
315
  association. A grant for the source template works without an editing session,
316
- including from an ordinary project created from it. Request only the minimum
316
+ including from an independent project created from it. Request only the minimum
317
317
  permission returned by a denied write. Agent permission defaults remain
318
318
  user-only even with an editing grant.
319
319
 
@@ -348,9 +348,9 @@ Project operations use these fields in addition to `section`:
348
348
  | `maintenance_delete` | No additional fields. |
349
349
  | `maintenance_watches` | `expectedRevision` from `maintenance.revision`, `confirmWatchRemovals`, `script`, `timeoutSeconds`, `watches` with `repository`, `enabled`, and `paths`; preserves the schedule. |
350
350
  | `member_files` | `expectedDefinitionScopeId`, `expectedDefinitionDesiredRevision`, `expectedMemberDesiredRevision` from `memberFilesRevision`; `updates` with `fileId` and `valueAction` (`kind: "delete"`, `kind: "accept"`, or `kind: "replace"` with `plaintextBase64` and `byteLength`). |
351
- | `environment_file` | `draft` for an ordinary project's environment file, as described below. For a managed project's personal values, use `env set|remove`. |
352
- | `environment_file_delete` | `contextId`, `expectedContextRevision` for an ordinary project's environment file. |
353
- | `agent_settings` | `agent` (`claude` or `codex`), `content`, `expectedRevision`, as described below. In a member project, this saves the member's own settings. |
351
+ | `environment_file` | `draft` for an independent project's environment file, as described below. For a managed project's personal values, use `env set|remove`. |
352
+ | `environment_file_delete` | `contextId`, `expectedContextRevision` for an independent project's environment file. |
353
+ | `agent_settings` | `agent` (`claude` or `codex`), `content`, `expectedRevision`, as described below. In a managed project, this saves the member's own settings. |
354
354
 
355
355
  Team Template operations use these fields in addition to `section`:
356
356
 
@@ -377,7 +377,7 @@ Team Template operations use these fields in addition to `section`:
377
377
  | `agent_settings` | `agent` (`claude` or `codex`), `content`, `expectedRevision`, as described below. |
378
378
  | `agent_permissions` | `expectedRevision` from `agentPermissions.revision`, `locked`, and complete `values` with every field from the read result. The first save with `locked: false` while `memberProjectCount` is above zero also needs `existingMembers`: `follow_team_template` or `keep_current`. |
379
379
 
380
- Before a first `agent_permissions` save with existing member projects, ask
380
+ Before a first `agent_permissions` save with existing managed projects, ask
381
381
  the user whether those projects should move to the new permissions
382
382
  (`follow_team_template`) or keep their current ones as each member's own
383
383
  choice (`keep_current`); without the field the save fails with
@@ -389,7 +389,7 @@ An environment `draft` contains `contextId`, `expectedContextRevision`, `path`,
389
389
  `displayOrder`, `adoptionRevision`, `adoptionSourceSha256`,
390
390
  `adoptionManagedNames`, `adoptionRemovedNames`, and the complete `rows` array.
391
391
  Read these file fields before editing; for a new file use null IDs/revisions,
392
- empty adoption arrays, and a new relative path. Ordinary project drafts also
392
+ empty adoption arrays, and a new relative path. Independent project drafts also
393
393
  need `state: "active"` or `"pending_adoption"`.
394
394
  Each row contains `rowId`, `displayOrder`, `name`, `inlineComment`,
395
395
  `description`, and `valueAction`. Team Template rows also need `provider`
@@ -839,7 +839,7 @@ those configured separately. Other devboxes will keep their individual
839
839
  permissions. The choice is personal to the owner's
840
840
  project, including projects created from a Team Template; it will not change
841
841
  teammates' permissions. Template-only permissions keep their existing scope.
842
- In a Member project whose Team Template locks agent permissions, **Always
842
+ In a managed project whose Team Template locks agent permissions, **Always
843
843
  allow for project** is not offered; **Allow** still enables the permission on
844
844
  the requesting box. See `team-template.md` for how a Team Template sets these
845
845
  project permissions.
@@ -1179,9 +1179,8 @@ If that source box has no saved defaults for the agent, the managed catalog
1179
1179
  default is used.
1180
1180
 
1181
1181
  The new devbox belongs to the source box's project and uses that project's
1182
- current reusable source. An ordinary project uses its latest eligible
1183
- Template-box snapshot and returns `snapshot_required` when none exists. A Team
1184
- Template member project uses the current saved version. The command never
1182
+ current reusable source. An independent project uses its latest eligible
1183
+ Template-box snapshot and returns `snapshot_required` when none exists. A managed project uses the current saved version. The command never
1185
1184
  snapshots or clones the live source box. Files, edits, branches, and commits
1186
1185
  that exist only on the source devbox are absent. Push a needed commit to a Git
1187
1186
  remote and tell the child to fetch and check it out, or use `current-devbox`;
@@ -1327,10 +1326,10 @@ dvb-onbox threads read \
1327
1326
  ```
1328
1327
 
1329
1328
  This returns a bounded preview of the durable boxes.dev transcript, thread
1330
- status, and older-page cursor. Long messages are marked as shortened. It can
1331
- briefly lag the live runtime. Pending Codex and Claude queue entries remain
1332
- runtime state and do not appear as transcript messages until the provider
1333
- accepts them as turns.
1329
+ status, latest stop metadata, and older-page cursor. Long messages are marked
1330
+ as shortened. It can briefly lag the live runtime. Pending Codex and Claude
1331
+ queue entries remain runtime state and do not appear as transcript messages
1332
+ until the provider accepts them as turns.
1334
1333
 
1335
1334
  List and observe that same source-scoped child pool without waking a child
1336
1335
  devbox:
@@ -1356,12 +1355,22 @@ dvb-onbox threads events <delegated-thread-id> \
1356
1355
  shows other project threads, including children created by a different source
1357
1356
  box. To find other threads in the project, use `threads list --scope project`
1358
1357
  from [Read Other Threads](#read-other-threads), which needs only **Read other
1359
- threads**. `threads result` returns the complete stored final response for one
1358
+ threads**. Delegated list and read results include `lastStopReason`,
1359
+ `lastStopAt` (Unix milliseconds), and `lastStopTurnId`. These describe the
1360
+ latest lifecycle event if it is a completion, interruption, or failure;
1361
+ otherwise they are null. A later event can replace or clear them. `idle`
1362
+ describes activity, not successful completion. Muting does not hide this
1363
+ metadata.
1364
+
1365
+ `threads result` returns the complete stored final response for one
1360
1366
  exact terminal turn and automatically assembles its transport pages. Use it instead
1361
1367
  of asking the child to summarize a shortened `threads read` preview. When
1362
- `threads wait` omits `--turn`, it snapshots the current active turn once. A
1363
- completed wait includes that same complete response as `output.text`; Ctrl+C
1364
- stops only the local wait. `threads events` emits durable lifecycle events with
1368
+ `threads wait` omits `--turn`, it snapshots the current active turn once. If
1369
+ there is no active turn, it returns `idle` with any available latest stop
1370
+ metadata as context. That stop can belong to an earlier assignment, so compare
1371
+ its turn ID with the work you are checking. A completed wait includes that
1372
+ same complete response as `output.text`; Ctrl+C stops only the local wait.
1373
+ `threads events` emits durable lifecycle events with
1365
1374
  an opaque resume cursor on every JSONL row. With no turn, cursor, or
1366
1375
  `--from-start`, it follows only events created after the command starts. An
1367
1376
  exact-turn stream ends after needs-input or a terminal event.
@@ -1372,8 +1381,15 @@ deleted, and controls return `thread_not_found`. Retrying its original start wit
1372
1381
  reports `child_thread_deleted` and keeps the original child ID; it does not
1373
1382
  create another thread or recover the deleted transcript.
1374
1383
 
1375
- Use a message's `turnId` from `threads read`, or an active turn ID from
1376
- `threads list`, directly with `result`, `wait`, and `events`. These observations
1384
+ Save a message's `turnId` from `threads read`, or an active turn ID from
1385
+ `threads list`, and use it directly with `result`, `wait`, and `events`. If the
1386
+ turn stopped before the first check, use `lastStopTurnId` to inspect its result.
1387
+ If that ID is null, find the assignment in `threads read` and use its saved
1388
+ message's `turnId`.
1389
+ Check `data.status` and the exact result before considering the assignment
1390
+ complete or sending a continuation; `ok: true` only means the lookup succeeded.
1391
+ Keep each assignment's turn ID even after a retry, because a successful later
1392
+ turn can replace the latest stop metadata. These observations
1377
1393
  also accept the transcript turn keys returned by older versions. For `steer`
1378
1394
  and `interrupt`, use the child's current `activeTurnId`.
1379
1395
 
@@ -1682,16 +1698,22 @@ shared. If any file cannot be transferred, the message will not be delivered.
1682
1698
  Attachments cannot be sent to a teammate's thread; send a link they can open
1683
1699
  instead.
1684
1700
 
1685
- Keys reuse the same receipt on the same source machine, including across CLI
1686
- invocations. After a retryable failure that confirms the message was not
1687
- delivered, repeat the command with the same key and message to try delivery
1688
- again. Successful sends, permanent failures, and uncertain delivery outcomes
1689
- keep their recorded result; repeating the command does not send them again.
1701
+ Keys reuse the same receipt on the same source devbox, including across CLI
1702
+ invocations. After a retryable failure, repeat the command with the same key
1703
+ and identical arguments. Keep only one call outstanding for each key. A
1704
+ retryable failure does not by itself prove that an earlier or overlapping call
1705
+ with that key never delivered the message. Successful sends, permanent
1706
+ failures, and uncertain delivery outcomes keep their recorded result;
1707
+ repeating the command does not send them again.
1690
1708
  Changing the recipient, message, attachments, or idle-only policy under that
1691
1709
  key fails with `idempotency_key_reused`. Use a new key for each distinct message.
1692
1710
  If delivery was skipped because the recipient was busy, use a new key if you
1693
1711
  later decide to send it again.
1694
1712
 
1713
+ If the error reports that a devbox is out of disk space, free space on the
1714
+ named source or recipient devbox before retrying. Waiting alone will not free
1715
+ space. Reuse the original key and arguments after cleanup.
1716
+
1695
1717
  `credits_depleted` means billing blocked the recipient's devbox before the
1696
1718
  message was delivered. If you're a team admin, add credits in **Billing**;
1697
1719
  otherwise, ask a team admin to add them. Then send the message again with a
@@ -2111,9 +2133,9 @@ Run `dvb-onbox box status --json` before choosing a workflow:
2111
2133
 
2112
2134
  - `team_template_edit_box`: the agent runs directly on the Team Template
2113
2135
  editing machine. Use **Work directly on a Team Template editing box** below.
2114
- - `template_box`: local shell commands affect an ordinary project's Template
2136
+ - `template_box`: local shell commands affect an independent project's Template
2115
2137
  box. To edit an associated Team Template, use **Work on a Team Template from
2116
- an ordinary Template box**. To create a new definition from the current
2138
+ a project's Template box**. To create a new definition from the current
2117
2139
  project, use **Create a Team Template from this project**.
2118
2140
  - `devbox`: local edits affect only this devbox; do not treat it as the shared
2119
2141
  template. In a Team Template project, a team admin's agent can edit that
@@ -2137,10 +2159,10 @@ on its current editing machine. Ordinary file and shell tools operate on that
2137
2159
  checkout. Use the actual repository paths there; do not use remote `exec` or
2138
2160
  `push` commands to reach the machine you already occupy.
2139
2161
 
2140
- This editing machine is not an ordinary project's Template box. Use
2162
+ This editing machine is not an independent project's Template box. Use
2141
2163
  `dvb-onbox project maintenance get|apply` for its Team Template maintenance
2142
2164
  policy and the **Member-file requirements** commands for member-file
2143
- definitions. Ordinary project setup completion, project lifecycle commands,
2165
+ definitions. Independent project setup completion, project lifecycle commands,
2144
2166
  and `dvb-onbox snapshot` are not the Team Template save workflow. Configure
2145
2167
  startup behavior in the Team Template's **When a new devbox is created** card
2146
2168
  and use the editor's save flow when the user has requested publication. See
@@ -2160,7 +2182,7 @@ project created from the template with `edit-team-template`, without an editing
2160
2182
  session. Run these commands in its current editing box too. From an ordinary
2161
2183
  Template box with an active editor association, add `--template <team-template-id>`
2162
2184
  to select that associated Team Template. Every operation edits the Team
2163
- Template; it does not add requirements to the caller's ordinary project.
2185
+ Template; it does not add requirements to the caller's independent project.
2164
2186
 
2165
2187
  ```bash
2166
2188
  dvb-onbox team-template member-files list --json
@@ -2184,7 +2206,7 @@ and removals. After an uncertain response, list again to inspect the outcome
2184
2206
  before retrying a change.
2185
2207
 
2186
2208
  Definitions take effect independently of saving a filesystem version. Existing
2187
- Member projects follow these requirements, and a missing file will block their
2209
+ managed projects follow these requirements, and a missing file will block their
2188
2210
  next startup. Changing a destination will require members to approve the new
2189
2211
  destination or upload a replacement. Changing instructions will not require
2190
2212
  destination approval. See [Member files](member-managed-files.md) for upload
@@ -2209,19 +2231,19 @@ dvb-onbox team-template env remove --file sandbox/.env.local --name LOG_LEVEL
2209
2231
  ```
2210
2232
 
2211
2233
  Paths are relative to `/home/boxes`. `--value` or `--value-stdin` saves a Team
2212
- value that every member project receives. `--member` asks each member for their
2234
+ value that every managed project receives. `--member` asks each member for their
2213
2235
  own value instead, required unless `--optional` is added, with optional
2214
2236
  `--instructions`. Switching a variable from Team to Member deletes its Team
2215
2237
  value. From an ordinary Template box, add `--template <team-template-id>`.
2216
2238
 
2217
- Changes take effect without saving a new Team Template version. Existing member
2239
+ Changes take effect without saving a new Team Template version. Existing managed
2218
2240
  projects receive Team values within about a minute. A new required Member value
2219
2241
  does not block existing devboxes; members will see it as needed in **Project
2220
2242
  settings → Environment files**.
2221
2243
 
2222
2244
  ### Create a Team Template from this project
2223
2245
 
2224
- A team admin can ask an agent on an ordinary project's Template box to create
2246
+ A team admin can ask an agent on an independent project's Template box to create
2225
2247
  a new Team Template based on that project. This path uses clean GitHub clones;
2226
2248
  it never snapshots the source box or copies its home directory, credentials,
2227
2249
  environment values, uncommitted files, or unrelated machine state.
@@ -2327,7 +2349,7 @@ fields, including `sourceKey` even when its schedule is disabled:
2327
2349
 
2328
2350
  When adding a new definition that has no source counterpart, choose a stable,
2329
2351
  nonempty `sourceKey` for it. Include definitions, never MCP credentials or
2330
- environment values. If member project creation is enabled,
2352
+ environment values. If managed project creation is enabled,
2331
2353
  `environmentConfirmed` confirms that the template does not capture or depend
2332
2354
  on member-specific environment values.
2333
2355
 
@@ -2404,13 +2426,13 @@ dvb-onbox team-template edit-box discard --edit-box <edit-box-id> \
2404
2426
  ```
2405
2427
 
2406
2428
  Saving fences this exact edit box and uses the normal verified Team Template
2407
- release pipeline. Requested member project creation becomes active only after
2429
+ release pipeline. Requested managed project creation becomes active only after
2408
2430
  the first saved release is eligible. `edit-box discard` is only for the
2409
2431
  unsaved draft created through this path.
2410
2432
 
2411
- ### Work on a Team Template from an ordinary Template box
2433
+ ### Work on a Team Template from a project's Template box
2412
2434
 
2413
- This section applies to an agent on an ordinary project's Template box with an
2435
+ This section applies to an agent on an independent project's Template box with an
2414
2436
  active association to a Team Template editing session, including one created
2415
2437
  through the creation workflow above. It does not describe a thread running
2416
2438
  directly in the Team Template editor. Agents and other processes on the
@@ -1,25 +1,25 @@
1
- # Ports, Terminal, And Runtime
1
+ # Ports, Terminal, and box controls
2
2
 
3
- The Ports menu, Terminal, Files, and Git follow the selected runtime. If you
3
+ The Ports menu, Terminal, Files, and Git follow the selected box. If you
4
4
  select the Template box, they use the Template box. If you select a devbox
5
5
  thread, they use that devbox. Ordinary `localhost` forwarding follows selection
6
6
  by default, but you can keep it on one devbox while working elsewhere. Stable
7
7
  local URLs also stay with each opted-in devbox after you select another thread.
8
8
 
9
- ## Runtime Status
9
+ ## Box status
10
10
 
11
- The runtime status pill in the desktop titlebar shows whether the selected
12
- runtime is running, sleeping, waking, connecting, snapshotting, upgrading, or at
11
+ The box status pill in the desktop titlebar shows whether the selected
12
+ box is running, sleeping, waking, connecting, snapshotting, upgrading, or at
13
13
  the awake devbox limit.
14
14
 
15
- When the runtime is running, open the status menu to sleep it. The same menu can
15
+ When the box is running, open the status menu to sleep it. The same menu can
16
16
  also toggle whether sleeping Template boxes and devboxes wake automatically when
17
17
  you return to them. Auto-wake is on by default and is saved as an account
18
- preference. When auto-wake is off, passive navigation leaves the runtime
18
+ preference. When auto-wake is off, passive navigation leaves the box
19
19
  asleep. Explicitly sending a message to a Codex or Claude thread will still
20
20
  wake its machine through the normal wake flow, even with auto-wake off.
21
21
 
22
- When the runtime is sleeping, use Wake from the status pill, Terminal, Files,
22
+ When the box is sleeping, use Wake from the status pill, Terminal, Files,
23
23
  Git, or Ports. If a devbox is sleeping because the awake devbox limit is full,
24
24
  boxes.dev asks you to sleep another devbox before continuing.
25
25
 
@@ -31,6 +31,10 @@ that protection sooner. When the limit expires, normal idle sleep can resume;
31
31
  the limit does not terminate the command. You can still sleep the machine
32
32
  yourself.
33
33
 
34
+ Claude's background shell commands in the chat view have a separate execution
35
+ limit: 30 minutes by default, up to two hours. When that limit expires, Claude
36
+ stops the command and receives a notification.
37
+
34
38
  A boxes.dev update can restart Claude, which stops its running background
35
39
  commands. boxes.dev will then send the agent a message in the thread that lists
36
40
  the stopped commands, so it can check their work and restart any it still
@@ -72,14 +76,14 @@ If delivery could not be confirmed, inspect the thread before trying again.
72
76
  boxes.dev will not automatically resend an uncertain check. This helps avoid
73
77
  repeating a deployment or similar operation after a lost response.
74
78
 
75
- ## Selected Runtime
79
+ ## Selected box
76
80
 
77
- Most runtime tools route to the selected thread:
81
+ Most box tools route to the selected thread:
78
82
 
79
83
  - Template box selected: tools run against the project Template box.
80
84
  - Devbox thread selected: tools run against that devbox.
81
- - A thread that has not started or has no connected runtime yet: runtime tools
82
- may ask you to wait, select a connected thread, or wake the runtime.
85
+ - A thread that has not started or has no connected box yet: box tools
86
+ may ask you to wait, select a connected thread, or wake the box.
83
87
 
84
88
  This routing matters most for ports and Git. A server started on a devbox
85
89
  appears in the devbox's Ports menu, not the Template box's menu.
@@ -87,7 +91,7 @@ appears in the devbox's Ports menu, not the Template box's menu.
87
91
  ## Terminal
88
92
 
89
93
  Open Terminal from the desktop titlebar. The terminal pane supports multiple
90
- terminal tabs for the selected runtime.
94
+ terminal tabs for the selected box.
91
95
 
92
96
  Common terminal actions:
93
97
 
@@ -96,7 +100,7 @@ Common terminal actions:
96
100
  - Drag tabs to reorder them.
97
101
  - Close a terminal tab with the close control on the tab.
98
102
  - If a detached session is shown, choose Connect to attach to it again.
99
- - If the selected runtime is sleeping, use Wake before terminal sessions load.
103
+ - If the selected box is sleeping, use Wake before terminal sessions load.
100
104
 
101
105
  Closing a terminal tab ends that terminal session. Closing the desktop app
102
106
  preserves open terminal sessions and restores their tabs when you reopen it.
@@ -135,7 +139,7 @@ alerts when terminal notification settings allow them.
135
139
  Paste a clipboard image into a desktop terminal with **Cmd+V** on macOS,
136
140
  **Ctrl+V** on Linux, or the terminal's **Paste** menu. Claude's image shortcut
137
141
  (**Ctrl+V** on macOS/Linux, **Alt+V** on Windows) also works. boxes.dev will
138
- upload the image to the selected machine and paste its file path. Claude Code
142
+ upload the image to the selected box and paste its file path. Claude Code
139
143
  will recognize that path as an image attachment; a shell will receive the path
140
144
  without running a command.
141
145
  PNG and JPEG images are supported, up to 20 MiB per image and 50 MiB per paste.
@@ -155,7 +159,7 @@ syntax is intentional. `--stdin` passes stdin bytes. JSON reports separate
155
159
  bounded stdout and stderr, the remote exit code, duration, timeout or
156
160
  cancellation state, and whether either stream was truncated.
157
161
 
158
- The command wakes a sleeping target through the normal runtime path. Ctrl+C
162
+ The command wakes a sleeping target through the normal box path. Ctrl+C
159
163
  cancels only the selected command. If the devbox needs a newer local boxes.dev
160
164
  service, exec fails explicitly and does not fall back to another transport.
161
165
 
@@ -303,8 +307,7 @@ availability to refresh, then retry the link.
303
307
 
304
308
  Choose **Configure port forwarding…** for project-level rules. The same
305
309
  configuration applies to every real machine in the project: the Template box
306
- and devboxes in an ordinary project, or only assigned devboxes in a Team
307
- Template member project. These rules also apply when you keep localhost on a
310
+ and devboxes in an independent project, or only assigned devboxes in a managed project. These rules also apply when you keep localhost on a
308
311
  box. Stable local URLs remain active for every opted-in devbox. New projects
309
312
  forward detected ports to the matching local port by default. Configuration can
310
313
  change that default, allow or exclude individual ports and inclusive ranges,
@@ -324,16 +327,16 @@ row can say that the port is in use locally or is not forwarded.
324
327
  When available, choose **Use next available** to approve forwarding that remote
325
328
  port to a different local port. The chosen local port stays pinned for the
326
329
  current desktop app session across box sleep/wake, renderer reloads, and thread
327
- or runtime reselection. Use the quiet inline **Unpin** action to return to the
330
+ or box reselection. Use the quiet inline **Unpin** action to return to the
328
331
  saved project mapping. Quitting the desktop app clears the pin. Session pins do
329
332
  not change the saved project mapping.
330
333
 
331
- With a connected runtime and no detected ports, the menu header simply counts
334
+ With a connected box and no detected ports, the menu header simply counts
332
335
  zero ports. In other empty states the menu explains itself: waiting for the
333
- selected runtime, waiting for the first port snapshot, reconnecting, or
336
+ selected box, waiting for the first port snapshot, reconnecting, or
334
337
  unavailable.
335
338
 
336
- ## Runtime Usage And Activity
339
+ ## Box usage and activity
337
340
 
338
341
  When live metrics are available, the titlebar can show CPU and memory usage.
339
342
  Memory usage covers the whole machine, including containers and system services,
@@ -343,7 +346,7 @@ for a service update, its tooltip may show **Workload memory** instead, which
343
346
  covers only the processes managed by boxes.dev.
344
347
 
345
348
  Click the usage indicator to open Activity. Activity lists processes inside the
346
- selected runtime, with command, CPU, memory, PID, and owner labels when
349
+ selected box, with command, CPU, memory, PID, and owner labels when
347
350
  available. Activity's **Workload memory** total covers that workload, while the
348
351
  titlebar shows the whole machine. Per-process memory figures may also include
349
352
  shared memory, so the rows do not necessarily add up to either total. You can
@@ -359,12 +362,12 @@ to recover. Reduce memory use before retrying the interrupted work.
359
362
  ## Reset
360
363
 
361
364
  The desktop app menu has **Machine > Reset (stop processes)…** when the selected
362
- managed runtime is running. Reset kills shells, agent sessions, background
363
- commands, and user services, while preserving files and keeping the runtime running.
365
+ managed box is running. Reset kills shells, agent sessions, background
366
+ commands, and user services, while preserving files and keeping the box running.
364
367
 
365
- If a devbox thread is selected, reset targets that devbox. In an ordinary
368
+ If a devbox thread is selected, reset targets that devbox. In an independent
366
369
  project, selecting the Template box targets it instead. A project with no
367
- selected real runtime has no reset target. boxes.dev confirms before resetting
370
+ selected real box has no reset target. boxes.dev confirms before resetting
368
371
  and then reports what was stopped.
369
372
 
370
373
  The Machine menu names the target as a Devbox with the selected thread's title
@@ -377,7 +380,7 @@ machine's service to be running and cannot recover a failed wake attempt.
377
380
  For a running machine, try **Machine > Reset (stop processes)…** before rebooting.
378
381
  **Machine > Reboot (restart machine)…** works on running and sleeping Template
379
382
  boxes and devboxes. It starts that exact machine without restoring saved memory.
380
- After a failed wake leaves the selected machine sleeping, a warning banner
383
+ After a failed wake leaves the selected box sleeping, a warning banner
381
384
  offers **Try again** to retry a normal wake and **Reboot…** to restart without
382
385
  saved memory. The normal **Wake** control remains available to retry waking.
383
386