@boxes-dev/dvb-runtime 1.0.1077 → 1.0.1079

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/bin/dvbd.mjs CHANGED
@@ -64675,9 +64675,9 @@ var init_sentry = __esm({
64675
64675
  uncaughtExceptionMonitorInstalled = false;
64676
64676
  currentDevboxSentryUser = null;
64677
64677
  readBuildMetadata = () => {
64678
- const rawPackageVersion = "1.0.1077";
64679
- const rawGitSha = "8b1aec823d1569de8d7eba6b9f55b50c500f38de";
64680
- const rawSentryRelease = "boxes-dev-dvb@1.0.1077+8b1aec823d1569de8d7eba6b9f55b50c500f38de";
64678
+ const rawPackageVersion = "1.0.1079";
64679
+ const rawGitSha = "b4796ddf10b015d808aba367f5eeb521c6ea0812";
64680
+ const rawSentryRelease = "boxes-dev-dvb@1.0.1079+b4796ddf10b015d808aba367f5eeb521c6ea0812";
64681
64681
  const packageVersion = typeof rawPackageVersion === "string" ? rawPackageVersion : void 0;
64682
64682
  const gitSha = typeof rawGitSha === "string" ? rawGitSha : void 0;
64683
64683
  const sentryRelease = typeof rawSentryRelease === "string" ? rawSentryRelease : void 0;
@@ -66894,7 +66894,7 @@ var init_packageVersion = __esm({
66894
66894
  return path8.join(process.cwd(), "dvb");
66895
66895
  };
66896
66896
  readEmbeddedPackageVersion = () => {
66897
- const raw = "1.0.1077";
66897
+ const raw = "1.0.1079";
66898
66898
  return trimVersion(raw);
66899
66899
  };
66900
66900
  readNearestPackageMetadata = (basePath) => {
@@ -330,6 +330,31 @@ thread also marks it read, but a pending request for input stays visible until
330
330
  it is answered. `threads list` reports each thread's `notificationsMuted`
331
331
  value.
332
332
 
333
+ Archive or unarchive an owned thread with an explicit command:
334
+
335
+ ```bash
336
+ dvb threads archive --thread <client-thread-id> --json
337
+ dvb threads unarchive --thread <client-thread-id> --json
338
+ ```
339
+
340
+ Archive preserves the history and removes the thread from the active list.
341
+ The result contains `clientThreadId`, `archived`, and `changed`; repeating a
342
+ command returns `changed: false` when its requested state is already set.
343
+ Codex archive updates its saved session and may wake the machine. Claude
344
+ archive changes shared metadata without waking it.
345
+
346
+ On a shared devbox, keep its anchor thread and archive the secondary task
347
+ threads. The first thread started on a previously threadless devbox becomes
348
+ its anchor and cannot be archived separately. These commands also support
349
+ threads on the Template box. Restore cold threads in the desktop or mobile
350
+ app before unarchiving them; history-only threads cannot be restored.
351
+
352
+ For a script that cleans up successful tasks, retain each task's result and
353
+ check `threads wait`'s `data.status` for `completed` before archiving. A
354
+ successful command exit or `ok: true` can also describe needs-input, failure,
355
+ timeout, or idle. Starting a thread only accepts its startup; an idle
356
+ observation during startup does not establish completion.
357
+
333
358
  ## Lifecycle Mutations And Cleanup
334
359
 
335
360
  Use exact project and target identifiers:
@@ -209,11 +209,39 @@ The creating run retains cleanup ownership; existing cleanup preserves devboxes
209
209
  with additional durable threads. The sidebar groups shared-devbox threads once,
210
210
  while run history keeps each workflow separately.
211
211
 
212
+ To send a follow-up to a standing conversation, use its boxes.dev thread ID
213
+ (the `clientThreadId` returned by the API, or the ID shown by `dvb threads list`):
214
+
215
+ ```json
216
+ {
217
+ "prompt": "Add reviewing the forwarded invoice to my to-do list.",
218
+ "target": { "kind": "existing_thread", "threadId": "<threadId>" }
219
+ }
220
+ ```
221
+
222
+ The thread must belong to you and to the automation's project; it need not have
223
+ been created by that automation. An idle agent will start the prompt, and a busy
224
+ agent will queue it after its current turn. The thread will keep its conversation,
225
+ title, agent settings, placement, and notification behavior. Omit `threadTitle`
226
+ and `execution` for this target. Omit `prompt` to send the saved automation prompt.
227
+ The automation's devbox cleanup and Slack output destinations do not apply to
228
+ these follow-ups.
229
+ A sleeping target's box will wake if capacity is available. An awake target
230
+ needs no additional awake slot.
231
+
232
+ Missing, archived, deleted, history-only, or otherwise unavailable threads return
233
+ `409 thread_unavailable`. A target that becomes unavailable after acceptance
234
+ can cause delivery to fail; inspect the run's status. This option creates a run
235
+ record but no thread or devbox. The response's `followUp.disposition` will become
236
+ `started` or `queued` when the run reaches `thread_ready`. It does not report
237
+ when the agent finishes. Retry an uncertain request with the same idempotency
238
+ key and body to avoid sending the prompt twice.
239
+
212
240
  An accepted request returns `202`, the run id, a status URL, nullable `devboxId`, and the effective
213
241
  thread title and agent controls without echoing the prompt. GET requests to the
214
242
  status URL require the same Bearer secret and report launch progress.
215
- `thread_ready` means the child thread exists and can be
216
- opened; it does not mean the first agent turn has finished. A request may be
243
+ `thread_ready` means the new thread exists, or the existing-thread follow-up
244
+ was accepted as started or queued; it does not mean the agent turn has finished. A request may be
217
245
  rejected if the automation is still a draft, paused, errored, or cannot create a
218
246
  devbox because the awake devbox limit is reached. Independent requests can start
219
247
  runs in parallel; use `Idempotency-Key` to make retries reuse the original run.
@@ -233,8 +261,8 @@ Capacity settings do not override billing limits or unavailable runtime state.
233
261
  They only help when the blocker is the awake devbox concurrency limit and an
234
262
  idle devbox can be slept.
235
263
 
236
- An API request targeting an awake devbox needs no additional awake slot.
237
- Sleeping targets wake if capacity is available. The sleep-idle option applies only
264
+ An `existing_devbox` API request targeting an awake devbox needs no additional
265
+ awake slot. Sleeping targets wake if capacity is available. The sleep-idle option applies only
238
266
  to new-devbox requests; a wake blocked by capacity produces a failed run with
239
267
  `startup_active_fork_limit_reached` at its status URL.
240
268
 
@@ -190,6 +190,45 @@ combined stdout/stderr tail of up to 4,000 characters. These reads do not wake
190
190
  the Template box or start maintenance. Logs can be incomplete during an active
191
191
  run; unknown or expired IDs return `maintenance_run_not_found`.
192
192
 
193
+ ## Agent Permissions
194
+
195
+ The same Agent permissions shown in a desktop thread header, the mobile app,
196
+ and Project settings are available from the terminal. Choose one box by alias
197
+ or the project's shared setting:
198
+
199
+ ```bash
200
+ dvb permissions get --box <box>
201
+ dvb permissions get --project <project>
202
+ dvb permissions set message-agents on --project <project>
203
+ dvb permissions set folder-access move --box <box>
204
+ ```
205
+
206
+ `set` takes a permission name from `get` and a value: `on` or `off` for
207
+ switches, `none`, `move`, or `create` for `folder-access`, and `none`,
208
+ `project`, `user`, `shared`, or `team` for `read-threads`. A box change applies
209
+ only to that box, while a project change applies to existing and future
210
+ devboxes except those configured separately. Template-box-only permissions such as
211
+ `create-team-templates` are rejected for a devbox or a project. Lifecycle and
212
+ maintenance rows appear only while the Template box is running. Turning on a
213
+ permission that an agent is waiting for completes its request.
214
+
215
+ When an agent asks for a permission with `dvb-onbox permissions request`, list
216
+ and answer the request from the terminal:
217
+
218
+ ```bash
219
+ dvb permissions requests
220
+ dvb permissions allow <request-id>
221
+ dvb permissions allow <request-id> --project
222
+ dvb permissions deny <request-id>
223
+ ```
224
+
225
+ `requests` shows each pending request's question, the box and thread it came
226
+ from, and minutes until it expires. `allow` matches **Allow**, `--project`
227
+ matches **Always allow for project**, and `deny` matches **Deny**. Requests
228
+ for 3-hour thread access, such as `edit-project-settings`, can only be allowed
229
+ for their thread. A request that expired or was already answered elsewhere
230
+ reports that it is no longer pending. Add `--json` for structured output.
231
+
193
232
  ## Open A Terminal
194
233
 
195
234
  Use:
@@ -115,6 +115,19 @@ Claude session. In a Team Template-managed project, the desktop app warns the
115
115
  member about each missing required value, such as one the team added later,
116
116
  and links to **Project settings**.
117
117
 
118
+ Project creation groups required values and member files under **Needed to
119
+ create the project**. **Optional values** starts collapsed, groups rows by destination
120
+ file and shows search when there are more than eight optional rows. Search
121
+ and disclosure changes preserve entered values. Identical names in different
122
+ files remain separate inputs. Optional values never block creation, but the
123
+ tools that use them may need them later.
124
+
125
+ Unsaved values are readable by default. One **Hide values** / **Show values**
126
+ setting applies across required and optional inputs for this setup session.
127
+ The form's bottom actions name missing requirements and link to their fields;
128
+ submitting an incomplete form marks and focuses the missing inputs. A failed
129
+ creation attempt keeps the entries available for retry.
130
+
118
131
  A normal project created from a Team Template receives an independent copy of
119
132
  the definitions and the Team/member values entered for that project. Later Team
120
133
  Template changes do not update it, and another project created from the same
@@ -123,7 +136,7 @@ template does not share its value objects.
123
136
  A Team Template-managed project follows the current Team Template definitions
124
137
  and Team values. Each member's values belong only to that member's exact
125
138
  project. Members can replace, remove, reveal, copy, or export their own project
126
- values. Team admins cannot read member values.
139
+ values. Team admins cannot read member values through Team Template management.
127
140
 
128
141
  A member can also add their own variables in **Project settings → Environment
129
142
  files**: in a file the Team Template manages, or in a new file of their own
@@ -27,6 +27,15 @@ the project. The original local filename is used only in that browser view and
27
27
  is not saved by boxes.dev. Files may contain arbitrary bytes and can be up to
28
28
  256 KiB.
29
29
 
30
+ During project creation, files appear with required environment values under
31
+ **Needed to create the project**, before the collapsed optional values. **Choose file**
32
+ opens the native file picker. After reading it, the form shows the local
33
+ filename and byte size, with **Change** and **Remove** actions.
34
+ Reading the file does not verify its contents or credentials.
35
+ Home destinations use `~/` in this form.
36
+ Oversized or unreadable files show an error at that requirement. The bottom
37
+ actions name missing files and link back to them.
38
+
30
39
  ## Storage And Delivery
31
40
 
32
41
  boxes.dev encrypts each member file for that exact project. An ordinary project
@@ -705,7 +705,10 @@ Add `--json` for a stable structured result.
705
705
 
706
706
  The command creates one request for the exact managed thread and source box,
707
707
  then waits up to ten minutes while the owner sees **Deny**, **Allow**, and,
708
- where supported, **Always allow for project** in boxes.dev.
708
+ where supported, **Always allow for project** in boxes.dev. An owner working
709
+ from a terminal on their computer can answer with `dvb permissions requests`,
710
+ then `dvb permissions allow <request-id>` (add `--project` for **Always allow
711
+ for project**) or `dvb permissions deny <request-id>`.
709
712
  **Allow** changes the existing persistent Agent permission
710
713
  for every agent on that source box until the owner turns it off; it is not a
711
714
  one-operation grant. **Deny** declines this request without changing permission
@@ -1197,11 +1200,15 @@ observing until it starts or fails. A wait without `--turn` can return `idle`
1197
1200
  in that interval; it does not prove the assignment has finished. After a wait
1198
1201
  times out, wait again on the same turn while the assignment remains pending.
1199
1202
 
1200
- A child returns its work to the parent in its final reply. To pass work from
1201
- one child to another, read the first child's result and forward what the other
1202
- needs with `threads send`; both steps need only **Create devboxes and threads**.
1203
- Children messaging the parent or each other with `dvb-onbox threads message`
1204
- need **Message other agents** on both the sending and receiving devboxes (see
1203
+ Choose how to exchange work based on the child's assignment. For a
1204
+ self-contained task, collect its final reply with `threads wait` or
1205
+ `threads result`; you can forward that result to another child with
1206
+ `threads send`. For direct collaboration during a turn, use `threads message`
1207
+ to exchange questions, findings, and feedback with the parent or other agents.
1208
+
1209
+ Collecting and forwarding final replies needs only **Create devboxes and
1210
+ threads**. Direct messages need **Message other agents** on both the sending
1211
+ and receiving devboxes (see
1205
1212
  [Message Other Agents](#message-other-agents)). When a plan depends on those
1206
1213
  messages, request `message-agents` once before starting the children. The
1207
1214
  request returns `already_granted` immediately when messaging is already on.
@@ -1272,17 +1279,17 @@ matches more than one thread you can read, use the thread's `id` instead.
1272
1279
  Listings, reads, and search results report the thread's last-reported execution
1273
1280
  `status`: `draft`, `starting`, `idle`, `running`, `needs_input`, `failed`, or
1274
1281
  `archived`. They also include `activeTurnId` and `activeTurnStatus` (both
1275
- nullable), alongside `updatedAt`. Check the thread's `status` when deciding
1276
- whether to nudge an idle agent; `transcript.status: ready` only means its
1277
- conversation can be read. These stored states can lag live work or change
1278
- before a message arrives, so they do not guarantee idle-only delivery. Reading
1279
- status does not wake a devbox or require delegation permission.
1282
+ nullable), alongside `updatedAt`. Use the thread's `status` to check its
1283
+ execution state. `transcript.status: ready` only means its conversation can
1284
+ be read, even while the agent is working. These stored states can lag live work
1285
+ or change before a message arrives, so they do not guarantee idle-only delivery.
1286
+ Reading status does not wake a devbox or require delegation permission.
1280
1287
 
1281
1288
  For known threads, fetch their metadata together instead of scanning the whole
1282
1289
  project or reading their conversations:
1283
1290
 
1284
1291
  ```bash
1285
- dvb-onbox threads status --scope project --ids-file lanes.json --json
1292
+ dvb-onbox threads status --scope project --ids-file thread-ids.json --json
1286
1293
  ```
1287
1294
 
1288
1295
  The file must contain a JSON array of 1 through 100 thread `id` values from
@@ -1390,7 +1397,7 @@ dvb-onbox threads message --to <thread-id> \
1390
1397
  --message "The endpoint now returns 422 for invalid widgets." --json
1391
1398
 
1392
1399
  dvb-onbox threads message --to <thread-id> --message "Review the endpoint." \
1393
- --idempotency-key keeper-2026-10-14-lane-1 --idle-only --json
1400
+ --idempotency-key endpoint-review-1 --idle-only --json
1394
1401
 
1395
1402
  dvb-onbox threads message --batch-file /tmp/messages.json --idle-only --json
1396
1403
  ```
@@ -1399,7 +1406,7 @@ The batch file is a JSON array of 1–100 objects, up to 3 MiB:
1399
1406
 
1400
1407
  ```json
1401
1408
  [
1402
- {"to": "<thread-id>", "message": "Review the endpoint.", "idempotencyKey": "keeper-2026-10-14-lane-1"}
1409
+ {"to": "<thread-id>", "message": "Review the endpoint.", "idempotencyKey": "endpoint-review-1"}
1403
1410
  ]
1404
1411
  ```
1405
1412
 
@@ -1441,8 +1448,9 @@ instead.
1441
1448
  Keys reuse the same receipt on the same source machine, including across CLI
1442
1449
  invocations. Retrying with the same key and message recovers that outcome
1443
1450
  without another delivery. Changing the recipient, message, attachments, or
1444
- idle-only policy under that key fails with `idempotency_key_reused`. Use a new key for each new
1445
- logical nudge or cadence pass, including when reconsidering a busy skip.
1451
+ idle-only policy under that key fails with `idempotency_key_reused`. Use a new
1452
+ key for each distinct message. If delivery was skipped because the recipient
1453
+ was busy, use a new key if you later decide to send it again.
1446
1454
 
1447
1455
  `--to` takes a boxes.dev thread ID, such as one named in a received message,
1448
1456
  one returned by `dvb-onbox threads start`, or one from
@@ -1486,7 +1494,7 @@ the outcome before reporting `operation_indeterminate`, so a script that runs
1486
1494
  it should allow at least four minutes per delivery; batches may need longer
1487
1495
  because each group can include slow wakes. If a send is stopped early, recover
1488
1496
  with the same key or treat the unkeyed message as possibly delivered. Batch
1489
- concurrency does not guarantee a five-minute cadence when machines must wake.
1497
+ delivery time depends on how long recipients' devboxes take to wake or update.
1490
1498
 
1491
1499
  If sending reports `messaging_disabled`, request `message-agents`.
1492
1500
  `recipient_messaging_disabled` means the recipient's devbox has messaging off;
@@ -440,13 +440,30 @@ another.
440
440
 
441
441
  ## Creating A Project
442
442
 
443
- For an ordinary project with its own Template box, start the ordinary
444
- new-project flow and choose **Start from a Team Template**.
445
- Select the exact template, then name the project and choose which coding agents
446
- should be available. The picker shows only templates with a current saved
447
- version and does not preselect one. Before creation, the flow shows the
448
- exact version, machine size, and a read-only summary of the current Project
449
- defaults.
443
+ Start the ordinary new-project flow and choose **Start from a Team Template**.
444
+ The picker shows only templates with a current saved version and does not
445
+ preselect one. Select the exact template, name the project and complete
446
+ **Needed to create the project**, which brings required environment values
447
+ and all member files together. **Optional values** starts collapsed; these
448
+ can be added now or later in Project settings. Independent projects also
449
+ offer coding-agent choices; at least one must be selected when the template
450
+ includes setup instructions. Team defaults remain available for review.
451
+
452
+ The persistent bottom actions identify missing items and link to their
453
+ fields. **Create project** marks missing fields and focuses the first one.
454
+ Checks still enforce GitHub access, billing and the template's actual
455
+ requirements; values being present does not prove the credentials work.
456
+
457
+ **Change template** keeps the active draft in memory, and **Back to setup**
458
+ returns to it from the picker. Selecting a different template or closing setup
459
+ asks before discarding meaningful entries. Reloading clears unsaved entries; there is
460
+ no cross-session draft storage. Creation errors keep the entries for retry.
461
+
462
+ Git identity appears as an account summary. **Edit account identity** opens
463
+ the fields, and changes update the account identity when the project is
464
+ created. An opted-out account stays opted out unless the member chooses
465
+ **Turn on for your account**. This does not create a project-specific Git
466
+ identity.
450
467
 
451
468
  For saved GitHub repositories, project creation checks the member's current
452
469
  boxes.dev GitHub connection and pull/push access. Any GitHub maintenance watch,
@@ -1210,6 +1210,16 @@ Thread rows can show unread and active indicators so users can see which
1210
1210
  threads need attention. Desktop and mobile notifications can also point users
1211
1211
  back to threads that finished, need input, or changed state.
1212
1212
 
1213
+ While boxes.dev is in the foreground, phone alerts stay quiet for all projects.
1214
+ When boxes.dev is in the background and the user is using the computer,
1215
+ phone alerts stay quiet for the selected project.
1216
+ This requires an updated desktop app and an enabled desktop notification,
1217
+ sound, or attention effect. Phone alerts resume after five minutes without
1218
+ keyboard or mouse input, or when the background desktop app detects a locked
1219
+ screen. Quitting the app or sleeping the computer releases the desktop claim
1220
+ within about 45 seconds. Other projects remain eligible for phone alerts. Unread markers and
1221
+ badges continue to sync across devices.
1222
+
1213
1223
  **Mute notifications** turns off one thread's notifications for finished,
1214
1224
  failed, and interrupted turns and keeps those turns from marking it unread. A
1215
1225
  request for input still notifies and marks the thread. A muted thread shows a
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@boxes-dev/dvb-runtime",
3
- "version": "1.0.1077",
3
+ "version": "1.0.1079",
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-15T19:24:00Z"
80
+ "devboxReleasedAt": "2026-10-15T22:32:18Z"
81
81
  }