@boxes-dev/dvb-runtime 1.0.1077 → 1.0.1078
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/dvb.mjs +1416 -276
- package/dist/bin/dvbd.mjs +4 -4
- package/dist/product-docs/references/agent-tools.md +25 -0
- package/dist/product-docs/references/automations.md +32 -4
- package/dist/product-docs/references/cli.md +39 -0
- package/dist/product-docs/references/onbox-agent-tools.md +4 -1
- package/package.json +2 -2
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.
|
|
64679
|
-
const rawGitSha = "
|
|
64680
|
-
const rawSentryRelease = "boxes-dev-dvb@1.0.
|
|
64678
|
+
const rawPackageVersion = "1.0.1078";
|
|
64679
|
+
const rawGitSha = "8c516f16149b71ba8dc1fd9ba16fda4b614ce8bf";
|
|
64680
|
+
const rawSentryRelease = "boxes-dev-dvb@1.0.1078+8c516f16149b71ba8dc1fd9ba16fda4b614ce8bf";
|
|
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.
|
|
66897
|
+
const raw = "1.0.1078";
|
|
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
|
|
216
|
-
|
|
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
|
|
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:
|
|
@@ -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
|
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.1078",
|
|
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-
|
|
80
|
+
"devboxReleasedAt": "2026-10-15T21:42:40Z"
|
|
81
81
|
}
|