@boxes-dev/dvb-runtime 1.0.1046 → 1.0.1047

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 CHANGED
@@ -1,6 +1,6 @@
1
1
  #!/usr/bin/env node
2
2
 
3
- !function(){try{var e="undefined"!=typeof window?window:"undefined"!=typeof global?global:"undefined"!=typeof globalThis?globalThis:"undefined"!=typeof self?self:{},n=(new e.Error).stack;n&&(e._sentryDebugIds=e._sentryDebugIds||{},e._sentryDebugIds[n]="2e34de02-2792-542c-b897-a59ea76825c6")}catch(e){}}();
3
+ !function(){try{var e="undefined"!=typeof window?window:"undefined"!=typeof global?global:"undefined"!=typeof globalThis?globalThis:"undefined"!=typeof self?self:{},n=(new e.Error).stack;n&&(e._sentryDebugIds=e._sentryDebugIds||{},e._sentryDebugIds[n]="c2a70501-be74-548e-b89c-b97a3ec6f60d")}catch(e){}}();
4
4
  import { createRequire as __dvbCreateRequire } from "node:module";
5
5
  import { dirname as __dvbDirname } from "node:path";
6
6
  import { fileURLToPath as __dvbFileURLToPath } from "node:url";
@@ -101146,8 +101146,8 @@ var init_otel = __esm({
101146
101146
  return trimmed && trimmed.length > 0 ? trimmed : void 0;
101147
101147
  };
101148
101148
  readBuildMetadata = () => {
101149
- const rawPackageVersion = "1.0.1046";
101150
- const rawGitSha = "d7f36a74aca199e338af7169982e817ff16d02e7";
101149
+ const rawPackageVersion = "1.0.1047";
101150
+ const rawGitSha = "e6ca031d74515a42d5195f3e8a8ff7a606c687ff";
101151
101151
  const packageVersion = typeof rawPackageVersion === "string" ? rawPackageVersion : void 0;
101152
101152
  const gitSha = typeof rawGitSha === "string" ? rawGitSha : void 0;
101153
101153
  return { packageVersion, gitSha };
@@ -133553,9 +133553,9 @@ var init_sentry = __esm({
133553
133553
  uncaughtExceptionMonitorInstalled = false;
133554
133554
  currentDevboxSentryUser = null;
133555
133555
  readBuildMetadata2 = () => {
133556
- const rawPackageVersion = "1.0.1046";
133557
- const rawGitSha = "d7f36a74aca199e338af7169982e817ff16d02e7";
133558
- const rawSentryRelease = "boxes-dev-dvb@1.0.1046+d7f36a74aca199e338af7169982e817ff16d02e7";
133556
+ const rawPackageVersion = "1.0.1047";
133557
+ const rawGitSha = "e6ca031d74515a42d5195f3e8a8ff7a606c687ff";
133558
+ const rawSentryRelease = "boxes-dev-dvb@1.0.1047+e6ca031d74515a42d5195f3e8a8ff7a606c687ff";
133559
133559
  const packageVersion = typeof rawPackageVersion === "string" ? rawPackageVersion : void 0;
133560
133560
  const gitSha = typeof rawGitSha === "string" ? rawGitSha : void 0;
133561
133561
  const sentryRelease = typeof rawSentryRelease === "string" ? rawSentryRelease : void 0;
@@ -138773,7 +138773,7 @@ var init_packageVersion = __esm({
138773
138773
  return path17.join(process.cwd(), "dvb");
138774
138774
  };
138775
138775
  readEmbeddedPackageVersion = () => {
138776
- const raw = "1.0.1046";
138776
+ const raw = "1.0.1047";
138777
138777
  return trimVersion(raw);
138778
138778
  };
138779
138779
  readNearestPackageMetadata = (basePath) => {
@@ -313568,7 +313568,9 @@ var init_controlPlane2 = __esm({
313568
313568
  preflightDesktopInitProject: (request2) => query(preflightProject, request2),
313569
313569
  upsertDesktopInitRegistryStatus: (request2) => mutation(registryUpsert2, request2),
313570
313570
  removeDesktopInitRegistryProject: (request2) => mutation(registryRemove, request2),
313571
- startOrResumeDesktopInitJob: (request2) => mutation(startOrResumeJob, request2),
313571
+ // Marks the job as agent-driven so the desktop app observes it instead
313572
+ // of resuming it as its own setup.
313573
+ startOrResumeDesktopInitJob: (request2) => mutation(startOrResumeJob, { ...request2, startedBy: "agent_init" }),
313572
313574
  createDesktopInitUploadSession: (request2) => action(createUploadSession, request2),
313573
313575
  refreshDesktopInitMultipartUploadParts: (request2) => action(refreshMultipartUploadParts, request2),
313574
313576
  listDesktopInitMultipartUploadedParts: (request2) => action(listMultipartUploadedParts, request2),
@@ -360010,4 +360012,4 @@ react/cjs/react-jsx-runtime.development.js:
360010
360012
  *)
360011
360013
  */
360012
360014
 
360013
- //# debugId=2e34de02-2792-542c-b897-a59ea76825c6
360015
+ //# debugId=c2a70501-be74-548e-b89c-b97a3ec6f60d
package/dist/bin/dvbd.mjs CHANGED
@@ -96328,8 +96328,8 @@ var init_otel = __esm({
96328
96328
  return trimmed && trimmed.length > 0 ? trimmed : void 0;
96329
96329
  };
96330
96330
  readBuildMetadata = () => {
96331
- const rawPackageVersion = "1.0.1046";
96332
- const rawGitSha = "d7f36a74aca199e338af7169982e817ff16d02e7";
96331
+ const rawPackageVersion = "1.0.1047";
96332
+ const rawGitSha = "e6ca031d74515a42d5195f3e8a8ff7a606c687ff";
96333
96333
  const packageVersion = typeof rawPackageVersion === "string" ? rawPackageVersion : void 0;
96334
96334
  const gitSha = typeof rawGitSha === "string" ? rawGitSha : void 0;
96335
96335
  return { packageVersion, gitSha };
@@ -128624,9 +128624,9 @@ var init_sentry = __esm({
128624
128624
  uncaughtExceptionMonitorInstalled = false;
128625
128625
  currentDevboxSentryUser = null;
128626
128626
  readBuildMetadata2 = () => {
128627
- const rawPackageVersion = "1.0.1046";
128628
- const rawGitSha = "d7f36a74aca199e338af7169982e817ff16d02e7";
128629
- const rawSentryRelease = "boxes-dev-dvb@1.0.1046+d7f36a74aca199e338af7169982e817ff16d02e7";
128627
+ const rawPackageVersion = "1.0.1047";
128628
+ const rawGitSha = "e6ca031d74515a42d5195f3e8a8ff7a606c687ff";
128629
+ const rawSentryRelease = "boxes-dev-dvb@1.0.1047+e6ca031d74515a42d5195f3e8a8ff7a606c687ff";
128630
128630
  const packageVersion = typeof rawPackageVersion === "string" ? rawPackageVersion : void 0;
128631
128631
  const gitSha = typeof rawGitSha === "string" ? rawGitSha : void 0;
128632
128632
  const sentryRelease = typeof rawSentryRelease === "string" ? rawSentryRelease : void 0;
@@ -130826,7 +130826,7 @@ var init_packageVersion = __esm({
130826
130826
  return path8.join(process.cwd(), "dvb");
130827
130827
  };
130828
130828
  readEmbeddedPackageVersion = () => {
130829
- const raw = "1.0.1046";
130829
+ const raw = "1.0.1047";
130830
130830
  return trimVersion(raw);
130831
130831
  };
130832
130832
  readNearestPackageMetadata = (basePath) => {
@@ -71,6 +71,29 @@ automatically. The choice is saved with each new run, so changing it affects
71
71
  future runs without changing existing run history. Slack and Linear replies and
72
72
  output destinations are unaffected.
73
73
 
74
+ ## Automations Created By Agents
75
+
76
+ You can ask an agent in one of the project's threads to set up or change an
77
+ automation, for example "every weekday at 9:30, run the tests and post any
78
+ failures to #eng". Agents can read the project's automations and their runs
79
+ without asking. If you describe recurring work without asking for an
80
+ automation, the agent explains how one would run and offers to create it
81
+ first. To create one, the agent asks for access in the thread: **Allow this
82
+ thread to edit your automations?** with **Allow for 3 hours** and **Deny**. Allowing it lets the
83
+ agent in that thread create, change, pause, activate, run, and delete your
84
+ automations in this project for 3 hours; other threads don't receive it.
85
+
86
+ Agents can set up Manual and Schedule automations with the same settings as the
87
+ desktop editor, including Slack output destinations. API, Slack, and Linear
88
+ triggers can be set up only in the desktop app, but an agent can change the
89
+ name, prompt, and settings of those automations.
90
+
91
+ An automation created by an agent is saved paused, like one created with
92
+ **Create**, and appears in the Automations section. The agent posts a link that
93
+ opens it. Its detail pane shows the
94
+ thread that created it, with a link to that thread. You can edit, pause, or
95
+ delete it the usual way.
96
+
74
97
  ## Trigger Modes
75
98
 
76
99
  **Manual** means the automation runs only when you choose **Run now**.
@@ -24,6 +24,12 @@ Team and enterprise arrangements may differ from these self-serve limits.
24
24
  Included box-hours, project limits, and awake-devbox limits apply per user;
25
25
  prepaid overage credits are shared through the team's billing account.
26
26
 
27
+ For the YC deal, redeem the offer on YC and sign in to boxes.dev with the same
28
+ email. The offer will apply to your team after your email is verified. If you
29
+ already have a paid subscription or used a different email, contact
30
+ hi@boxes.dev for help applying the offer; redemption will not automatically
31
+ replace a paid subscription.
32
+
27
33
  ## Box-Hours
28
34
 
29
35
  One box-hour means one default 4 vCPU / 8 GiB devbox awake for one hour.
@@ -222,8 +222,16 @@ particular machine. This page contains **Project storage**, **Git**, **Agent
222
222
  permissions for this project**, and **Devbox lifecycle**, including the
223
223
  project's preferred Git action, commit thread-link behavior, startup script,
224
224
  shared agent guidance, automatic waking of sleeping machines, and other
225
- new-devbox defaults. The automatic idle-sleep timeout is not user-configurable.
226
- Opening it does not select or wake a machine.
225
+ new-devbox defaults. Opening it does not select or wake a machine.
226
+
227
+ To change the automatic idle-sleep timeout, open **Account
228
+ → Sleep timeout** and choose 5, 15, 30, or 60 minutes, or **Team default**.
229
+ Team admins can set the default in **Team Settings → Sleep timeout**; without
230
+ a custom setting it is five minutes. Your choice overrides the team default
231
+ for your Template boxes and devboxes, including Team Template member projects.
232
+ Changes apply to existing and new boxes. A running box may keep its current
233
+ sleep deadline until its next activity; saving will not wake a sleeping box.
234
+ Longer timeouts use more box-hours; active agents can still keep boxes awake.
227
235
 
228
236
  The same Settings section opens **Desktop app settings...** and **Configure
229
237
  agents...** in separate windows. Desktop app settings contains only preferences
@@ -81,10 +81,11 @@ Use this terminology consistently:
81
81
  one-off exec, lifecycle mutations, JSON envelopes, and safe retries.
82
82
  - `onbox-agent-tools.md`: the separate, narrow `dvb-onbox` surface available
83
83
  only to coding agents inside a Template box or devbox, including setup,
84
- snapshots, user-authorized delegated thread starts, and project devbox
85
- folders.
84
+ snapshots, user-authorized delegated thread starts, project devbox
85
+ folders, and managing the project's automations.
86
86
  - `automations.md`: Thread Automations, scheduled/API-triggered runs, Slack and
87
- Linear-triggered runs, run history, capacity, and spawned devbox threads.
87
+ Linear-triggered runs, run history, capacity, spawned devbox threads, and
88
+ automations created by agents.
88
89
  - `slack.md`: Slack connection, identity linking, Slack-triggered automations,
89
90
  mentions, follow-ups, final replies, attachment import basics, and limits.
90
91
  - `linear.md`: Linear Agent App install, identity linking, assignment-triggered
@@ -17,7 +17,9 @@ their existing box or project setting is enabled. Turning one of those settings
17
17
  off removes its projected skill from both managed agent homes. The devbox
18
18
  lifecycle and Template maintenance skill is deliberately always discoverable
19
19
  on an ordinary Template box so an agent can inspect the workflow, receive the
20
- operation-specific denial, and request only the exact missing permission.
20
+ operation-specific denial, and request only the exact missing permission. The
21
+ automations skill is always available too, because reading automations needs
22
+ no permission.
21
23
  Codex and Claude load the current catalog on their next start or resume; an
22
24
  already-running process can retain its startup catalog. Skill visibility is
23
25
  discovery, not authorization: each command checks the current setting when it
@@ -189,6 +191,150 @@ newline. `list` returns names, where each value comes from, and whether a value
189
191
  is saved; it never returns values. Saved changes reach running machines within
190
192
  about a minute. After an uncertain response, run `list` before retrying.
191
193
 
194
+ ## Automations
195
+
196
+ An agent can read and manage the current project's automations. Each
197
+ automation saves a prompt and agent settings; each run starts a new thread on
198
+ a new devbox. See [Automations](automations.md) for how they work.
199
+
200
+ Create an automation only when the user asks for recurring or unattended work.
201
+ Unless they asked for an automation by name, explain how one would run, offer
202
+ to create it, and wait for them to agree before requesting access. The
203
+ `boxes-automations` skill has the explanation to use.
204
+
205
+ ```bash
206
+ dvb-onbox automations options --json
207
+ dvb-onbox automations list --json
208
+ dvb-onbox automations get --automation <id> --json
209
+ dvb-onbox automations create --spec-file spec.json [--prompt-file prompt.md] --json
210
+ dvb-onbox automations update --automation <id> [--spec-file changes.json] [--prompt-file prompt.md] --if-revision <revision> [--dry-run] --json
211
+ dvb-onbox automations activate --automation <id> --json
212
+ dvb-onbox automations pause --automation <id> --json
213
+ dvb-onbox automations delete --automation <id> --json
214
+ dvb-onbox automations run --automation <id> --idempotency-key <key> --json
215
+ dvb-onbox automations runs --automation <id> [--cursor <cursor> | --run <run-id>] --json
216
+ ```
217
+
218
+ Each automation in a result has a `url` that opens it in the boxes.dev app.
219
+ After creating one, post that link for the user.
220
+
221
+ `options`, `list`, `get`, `runs`, and `update --dry-run` work from the
222
+ project's Template box or any of its devboxes without a permission. The other
223
+ commands need the current thread's `edit-automations` permission (see
224
+ [Agent Permissions](#agent-permissions)); without it they fail with
225
+ `automation_editing_disabled`.
226
+
227
+ ### Spec
228
+
229
+ `create` reads a JSON spec. Put the prompt in the spec as `prompt` or in a
230
+ separate `--prompt-file`, not both. File paths can be relative or absolute.
231
+
232
+ ```json
233
+ {
234
+ "name": "Nightly dependency check",
235
+ "prompt": "In /home/boxes/app, run `npm outdated` and list each outdated package with its current and latest versions.",
236
+ "execution": { "backend": "codex", "model": "<model>", "reasoningEffort": "<effort>", "serviceTier": "standard" },
237
+ "trigger": {
238
+ "kind": "schedule", "frequency": "daily", "interval": 1,
239
+ "timeZone": "America/Los_Angeles", "startDate": "2026-10-01",
240
+ "hour": 2, "minute": 0
241
+ },
242
+ "devboxCleanup": {
243
+ "timing": { "kind": "after_newer_runs", "runCount": 3 },
244
+ "repositoryWork": "keep_devbox",
245
+ "followups": "keep_devbox"
246
+ },
247
+ "outputs": [
248
+ { "kind": "slack_channel", "channel": "https://example.slack.com/archives/C0123456", "events": ["turn_completed", "run_failed"] }
249
+ ]
250
+ }
251
+ ```
252
+
253
+ - `name`, the prompt, `execution`, and `trigger` are required. Other keys
254
+ default to the desktop defaults: runs under the automation, successful runs
255
+ not marked read, no capacity options, devbox cleanup **Never** with both
256
+ safeguards, and no outputs. `create` saves the automation paused.
257
+ - `execution`: `backend` is `codex` or `claude`. Take `model` and
258
+ `reasoningEffort` from `automations options`; `reasoningEffort` is `null`
259
+ only for a model without reasoning control. Codex also takes `serviceTier`
260
+ `standard` (the default) or `fast`.
261
+ - `trigger`: `{"kind": "manual"}`, or a schedule with `frequency` `hourly`,
262
+ `daily`, `weekly`, or `monthly`; a whole-number `interval`; an IANA
263
+ `timeZone`; a `startDate` (`YYYY-MM-DD`); `hour` and `minute`; `weekdays`
264
+ (0–6, Sunday first) for weekly schedules; and `monthDay` for monthly ones.
265
+ Runs begin at the first matching time after now, so `startDate` can be
266
+ today or earlier. The `startDate` of a weekly schedule must fall on one of
267
+ its `weekdays`, and that of a monthly schedule on its `monthDay`. API,
268
+ Slack, and Linear triggers can be set up only in the desktop app.
269
+ - `threadPlacement`: `nested` (under the automation) or `main` (the main
270
+ thread list).
271
+ - `markSuccessfulRunsRead`: `true` or `false`.
272
+ - `capacity`: `sleepIdleDevboxWhenFull` and `deferScheduledRunWhenFull`, both
273
+ required when `capacity` is given. See
274
+ [Capacity Behavior](automations.md#capacity-behavior).
275
+ - `devboxCleanup`: `timing.kind` is `never`, `after_run_finishes`,
276
+ `after_inactive_days` with `days`, or `after_newer_runs` with `runCount`.
277
+ `repositoryWork` and `followups` are `keep_devbox` or `clean_up`. Cleanup
278
+ applies to future runs placed under the automation. See
279
+ [Automation Devbox Cleanup](automations.md#automation-devbox-cleanup).
280
+ - `outputs`: Slack destinations, each with `events` from `turn_completed`,
281
+ `needs_input`, and `run_failed`. A `slack_channel` output takes `channel`,
282
+ a channel ID or link; the boxes.dev Slack app must be in that channel. A
283
+ `slack_dm` output takes an optional `slackUserId` and otherwise goes to the
284
+ user's linked Slack account. Each destination can appear only once.
285
+ Slack-triggered automations reply in their Slack thread and take no outputs.
286
+
287
+ Spec errors (`invalid_spec`) name the field that failed, such as
288
+ `trigger.timeZone` or `outputs[1].channel`.
289
+
290
+ ### Change an automation
291
+
292
+ `get` returns a `revision`. Pass it to `update --if-revision`. An update is
293
+ partial: a key left out of the spec stays as it is, and a key included
294
+ replaces that whole value. `"outputs": []` removes all destinations, and
295
+ `{"trigger": {"kind": "manual"}}` removes a schedule. `update` needs
296
+ `--spec-file`, `--prompt-file`, or both.
297
+
298
+ If the automation changed after it was read, `update` fails with
299
+ `revision_conflict` and returns the current revision. Read it again, reconcile
300
+ the change with the user's request, and retry with the new revision.
301
+
302
+ `--dry-run` returns the result, including the next run times, without saving.
303
+ It checks new Slack destinations against the saved Slack connection without
304
+ contacting Slack, so a channel the boxes.dev app can't post to is reported
305
+ only when you save.
306
+
307
+ An automation with an API, Slack, or Linear trigger can have its name, prompt,
308
+ and settings changed, but a supplied `trigger` fails with
309
+ `unsupported_trigger_change`. `get` describes those triggers without their
310
+ settings, and `defaultIntegrationReceiver` is true for the default Slack or
311
+ Linear receiver.
312
+
313
+ ### Activate, run, and delete
314
+
315
+ - `activate` lets triggers start runs. It also recovers an errored
316
+ automation. `pause` stops new triggered runs; runs already started
317
+ continue.
318
+ - `run` starts one run now, even while the automation is paused. It starts a
319
+ new devbox and uses box-hours. When retrying, reuse the same
320
+ `--idempotency-key` to get the original run back. Errored automations and
321
+ default Slack and Linear receivers fail with `run_not_available`; launch
322
+ rejections fail with `run_rejected` and a `reasonCode`.
323
+ - `delete` works only while the automation has no runs. Otherwise it fails
324
+ with `automation_has_runs`; pause it instead.
325
+
326
+ ### Read runs
327
+
328
+ `runs` lists runs newest first, 20 at a time; pass the returned cursor with
329
+ `--cursor` for more. `runs --run <run-id>` adds the prompt and agent settings
330
+ that run used, or `null` for older runs that didn't record them. A run's
331
+ `thread_ready` status means its thread started, not that the work succeeded;
332
+ open the thread link to see the result. Schedule times include the local time
333
+ and UTC offset.
334
+
335
+ After `create` times out or fails without a clear result, run `list` before
336
+ trying again so you don't create a duplicate.
337
+
192
338
  ## Devbox Lifecycle And Template Maintenance
193
339
 
194
340
  From the project's current ordinary Template box, an agent can inspect and edit
@@ -298,8 +444,8 @@ The request values are `create-devboxes-and-threads`,
298
444
  `edit-devbox-lifecycle`, `edit-template-maintenance`, `destroy-devbox`,
299
445
  `read-project-threads`, `read-user-threads`, `read-shared-threads`,
300
446
  `read-team-threads`, `message-agents`, `edit-template-box`,
301
- `edit-team-template`, and `edit-personal-environment`. Add `--json` for a
302
- stable structured result.
447
+ `edit-team-template`, `edit-personal-environment`, and `edit-automations`.
448
+ Add `--json` for a stable structured result.
303
449
 
304
450
  The command creates one request for the exact managed thread and source box,
305
451
  then waits up to ten minutes while the owner sees **Deny**, **Allow**, and,
@@ -325,6 +471,12 @@ project; any member can receive it, and a thread that already has
325
471
  time. After the grant expires, the next command reports the missing permission
326
472
  and the agent needs a new request.
327
473
 
474
+ `edit-automations` is a 3-hour grant for the requesting thread too. Request
475
+ it from the project's Template box or any of its devboxes to create, change,
476
+ pause, activate, run, and delete the owner's automations in that project; see
477
+ [Automations](#automations). It is kept apart from the grants above, so a
478
+ thread can hold it together with one of them.
479
+
328
480
  For thread reads, agent messaging, folder access, thread titles, and creating
329
481
  devboxes and threads, the owner can choose **Always allow for project**
330
482
  directly.
@@ -195,9 +195,30 @@ The desktop app's Project step leads with **Set up with your coding agent**,
195
195
  followed by a Team Template when the team has one. The local-folder and GitHub
196
196
  options are fallbacks under **Other setup options** at the bottom of the step,
197
197
  with the local folder first. **Use coding agent** expands the card to show the
198
- prompt to copy into Codex or Claude Code in the local project folder. When the
199
- remote setup thread starts, the agent offers to open that project in the
200
- desktop app, so the Project step does not need to stay open.
198
+ prompt to copy into Codex or Claude Code in the local project folder. Once
199
+ the agent's `dvb agent-init run` starts uploading, the Project step's setup
200
+ choices are replaced by that project's setup status: the project name and four
201
+ stages (uploading the project files, creating the Template box, unpacking the
202
+ files on the Template box, and starting setup on the Template box). When the setup thread starts on the Template box, the
203
+ desktop app opens it in the workbench. The workbench banner then shows
204
+ **Setup in progress** and **Finishing setup** until setup completes, and new
205
+ devboxes are unavailable until then. In **New project**, the status only
206
+ follows a setup started while the wizard is open. The Project step does not
207
+ need to stay open for setup to continue.
208
+
209
+ If an agent-driven setup stops before its setup thread starts, the Project
210
+ step shows the error and asks the user to have their coding agent run
211
+ `dvb agent-init retry` in the project folder. **Delete setup**, shown on the
212
+ status whether setup is running or stopped, deletes the Template box, if one
213
+ was created, and the setup state saved on the computer, including the
214
+ manifest; the project folder is not affected. If setup
215
+ stops after the thread starts, the workbench banner shows the error and the
216
+ same retry command. A failure while bundling, before the upload starts,
217
+ appears only in the agent's `dvb agent-init` output. The agent's command
218
+ needs to be running when the Template box asks for the bundle's decrypt key;
219
+ if the Template box has waited more than a minute, the status view says setup
220
+ is waiting for the coding agent and asks the user to have it run `dvb
221
+ agent-init watch` in the project folder.
201
222
 
202
223
  The commands mirror the wizard's stages: `dvb agent-init start` seeds the
203
224
  version 3 manifest with everything detectable. A standard GitHub origin seeds
@@ -774,7 +795,11 @@ reopen setup at the step where it left off. The wizard row also offers
774
795
  **Continue setup** and a delete button; deleting removes only the incomplete
775
796
  setup state, and the local folder and its files won't be affected. A setup
776
797
  waiting on a recoverable error shows **Needs attention** in the project
777
- selector.
798
+ selector. Setups started by a coding agent with `dvb agent-init` are the
799
+ exception: the desktop app shows their status instead of wizard rows (see
800
+ Agent-Driven Setup From The Terminal) and never resumes them itself. If one
801
+ stops, the user should ask the coding agent to run `dvb agent-init retry` in
802
+ the project folder.
778
803
 
779
804
  Common recovery paths:
780
805
 
@@ -282,9 +282,11 @@ vulnerabilities should still be reported to security@boxes.dev.
282
282
 
283
283
  boxes.dev uses product analytics, crash reporting, and privacy-masked session
284
284
  replay to diagnose errors, screen flicker, animation problems, performance, and
285
- other reliability issues. Native mobile replay masks standard text-input fields
286
- before upload. Replays can contain ordinary displayed text, screen layout,
287
- movement, interactions, and other visual elements.
285
+ other reliability issues. Web and desktop replay mask text in agent conversations
286
+ and their message input regions before upload, while preserving layout and
287
+ surrounding controls for diagnostics. Native mobile replay masks standard
288
+ text-input fields before upload. Replays can contain ordinary displayed text,
289
+ screen layout, movement, interactions, and other visual elements.
288
290
 
289
291
  For the complete disclosure, retention details, and contact information, read
290
292
  the legal privacy policy at `https://boxes.dev/privacy`.
@@ -568,6 +568,13 @@ Codex threads expose model controls in the composer footer:
568
568
  Ultrafast when the model offers it. Fast and Ultrafast are labeled as faster
569
569
  with increased usage.
570
570
 
571
+ On desktop, type `$` in a Codex reply box to choose from the skills available
572
+ to Codex on that machine. Each row shows whether the skill comes from the
573
+ project, your personal skills, or Codex itself. Choosing a skill inserts a
574
+ `$name` link to its `SKILL.md`, and Codex will load that skill's instructions
575
+ with the message. A machine with an older boxes.dev service won't show the
576
+ list until its normal automatic update runs.
577
+
571
578
  Codex also shows context-window usage when available. When the context window
572
579
  gets full, the composer can show an auto-compaction warning and a Compact now
573
580
  action.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@boxes-dev/dvb-runtime",
3
- "version": "1.0.1046",
3
+ "version": "1.0.1047",
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",
@@ -79,5 +79,5 @@
79
79
  "e2b": "^2.18.0",
80
80
  "ink-testing-library": "^4.0.0"
81
81
  },
82
- "devboxReleasedAt": "2026-09-30T06:11:00Z"
82
+ "devboxReleasedAt": "2026-10-01T16:46:44Z"
83
83
  }