@boxes-dev/dvb-runtime 1.0.1053 → 1.0.1055

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
@@ -64667,9 +64667,9 @@ var init_sentry = __esm({
64667
64667
  uncaughtExceptionMonitorInstalled = false;
64668
64668
  currentDevboxSentryUser = null;
64669
64669
  readBuildMetadata = () => {
64670
- const rawPackageVersion = "1.0.1053";
64671
- const rawGitSha = "76361e7078c6a6e750a6d2ba0cf73167ab361588";
64672
- const rawSentryRelease = "boxes-dev-dvb@1.0.1053+76361e7078c6a6e750a6d2ba0cf73167ab361588";
64670
+ const rawPackageVersion = "1.0.1055";
64671
+ const rawGitSha = "f79c13a9c9d8ec1a57505f400122d23ec18b0a9c";
64672
+ const rawSentryRelease = "boxes-dev-dvb@1.0.1055+f79c13a9c9d8ec1a57505f400122d23ec18b0a9c";
64673
64673
  const packageVersion = typeof rawPackageVersion === "string" ? rawPackageVersion : void 0;
64674
64674
  const gitSha = typeof rawGitSha === "string" ? rawGitSha : void 0;
64675
64675
  const sentryRelease = typeof rawSentryRelease === "string" ? rawSentryRelease : void 0;
@@ -66884,7 +66884,7 @@ var init_packageVersion = __esm({
66884
66884
  return path8.join(process.cwd(), "dvb");
66885
66885
  };
66886
66886
  readEmbeddedPackageVersion = () => {
66887
- const raw = "1.0.1053";
66887
+ const raw = "1.0.1055";
66888
66888
  return trimVersion(raw);
66889
66889
  };
66890
66890
  readNearestPackageMetadata = (basePath) => {
@@ -71,6 +71,16 @@ 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
+ **Completion notifications**, also under **More settings**, controls whether a
75
+ turn that finishes in one of the automation's threads sends a desktop or mobile
76
+ notification. **Every turn** is the default. **Follow-ups only** skips the
77
+ notification for the automation's first turn, and **Off** skips it for every
78
+ turn in the automation's threads, including follow-ups. Failed turns and turns
79
+ that need input still notify. Muted threads still show an unread dot unless
80
+ **Mark successful runs as read** also applies. This choice is also saved with
81
+ each new run, and Slack and Linear replies and output destinations are
82
+ unaffected.
83
+
74
84
  ## Automations Created By Agents
75
85
 
76
86
  You can ask an agent in one of the project's threads to set up or change an
@@ -62,7 +62,8 @@ capacity. After a prepared devbox is assigned and wakes for the member, it is
62
62
  accounted for exactly like that member's other devboxes.
63
63
 
64
64
  The desktop titlebar can show a usage icon next to the project selector; hover
65
- it for current box-hour usage and awake devbox usage. The billing page shows
65
+ or click it for current box-hour usage, the billing period end date when
66
+ available, and awake devbox usage. The billing page shows
66
67
  usage for the current billing period. Its Usage history section shows
67
68
  box-hours used by hour for the last 24 hours or seven days, plus the boxes that
68
69
  contributed to that usage. The seven-day chart defaults to one bar per 24-hour
@@ -252,7 +252,8 @@ separate `--prompt-file`, not both. File paths can be relative or absolute.
252
252
 
253
253
  - `name`, the prompt, `execution`, and `trigger` are required. Other keys
254
254
  default to the desktop defaults: runs under the automation, successful runs
255
- not marked read, no capacity options, devbox cleanup **Never** with both
255
+ not marked read, completion notifications for every turn, no capacity
256
+ options, devbox cleanup **Never** with both
256
257
  safeguards, and no outputs. `create` saves the automation paused.
257
258
  - `execution`: `backend` is `codex` or `claude`. Take `model` and
258
259
  `reasoningEffort` from `automations options`; `reasoningEffort` is `null`
@@ -269,6 +270,11 @@ separate `--prompt-file`, not both. File paths can be relative or absolute.
269
270
  - `threadPlacement`: `nested` (under the automation) or `main` (the main
270
271
  thread list).
271
272
  - `markSuccessfulRunsRead`: `true` or `false`.
273
+ - `completionNotifications`: `all` (the default), `follow_ups_only` (no
274
+ notification when the automation's first turn finishes), or `none` (no
275
+ notification when any turn in its threads finishes). Failed turns and turns
276
+ that need input still notify. See
277
+ [Editing Automations](automations.md#editing-automations).
272
278
  - `capacity`: `sleepIdleDevboxWhenFull` and `deferScheduledRunWhenFull`, both
273
279
  required when `capacity` is given. See
274
280
  [Capacity Behavior](automations.md#capacity-behavior).
@@ -54,10 +54,15 @@ actions to email, copy, or share a link to the page, and the desktop step is
54
54
  left out. The first project is set up by the coding agent; **Create from
55
55
  GitHub** is offered when the user adds a later project.
56
56
 
57
- When a user copies the prompt, the page confirms the copy and can show when
58
- the CLI connects, prepares the project, waits for launch approval, and starts
59
- launching. The coding agent still owns the setup work, and `dvb agent-init
60
- status` remains the source for its exact next action.
57
+ When a user copies the prompt, the page confirms the copy and then follows
58
+ that setup by project name. It shows when the CLI connects and prepares the
59
+ project, when the user needs to connect accounts or GitHub or add an SSH key,
60
+ when the agent is fixing issues a check found, when the setup plan is ready for
61
+ approval, and the upload percentage. If a setup command fails, the page shows
62
+ its error. Once the CLI connects, the progress leads the card and the prompt
63
+ moves behind **Setup prompt**, which the user can open to copy the prompt again
64
+ (for example, to start over). The coding agent still owns the setup work, and
65
+ `dvb agent-init status` remains the source for its exact next action.
61
66
 
62
67
  After setup, the website's **Projects** page lists projects and their last-used
63
68
  activity. Choose a project name or **Open in desktop app** to continue in the
@@ -209,16 +214,19 @@ followed by a Team Template when the team has one. The local-folder and GitHub
209
214
  options are fallbacks under **Other setup options** at the bottom of the step,
210
215
  with the local folder first. The prompt and **Copy prompt** are visible
211
216
  immediately. Paste the prompt into Codex or Claude Code in the local project
212
- folder. During first-run setup, the card also shows when the CLI connects and
213
- prepares the project, including after a reload. For a later project, the card
214
- confirms the copy and setup progress appears once uploading begins.
217
+ folder. The card then shows that setup's progress, including after a reload:
218
+ when the CLI connects and prepares the project, when the user needs to act,
219
+ when a setup command fails, and when the setup plan is ready for approval.
220
+ Once the CLI connects, the prompt moves behind **Setup prompt** below the
221
+ progress. In **New project**, the card only follows a setup started after the
222
+ wizard opened.
215
223
 
216
224
  The folder wizard's steps and **Continue** appear only after a local folder
217
225
  is selected. **Other setup options** remembers whether it was open across
218
226
  reloads in the same app session. Once
219
227
  the agent's `dvb agent-init run` starts uploading, the Project step's setup
220
228
  choices are replaced by that project's setup status: the project name and four
221
- stages (uploading the project files, creating the Template box, unpacking the
229
+ stages (uploading the project files, with a percentage, creating the Template box, unpacking the
222
230
  files on the Template box, and starting setup on the Template box). When the setup thread starts on the Template box, the
223
231
  desktop app opens it in the workbench. The workbench banner then shows
224
232
  **Setup in progress** and **Finishing setup** until setup completes, and new
@@ -321,10 +329,12 @@ the agent where the user can follow it. On a Mac with the desktop app
321
329
  installed, the agent offers to open it with `dvb agent-init open-desktop`,
322
330
  which opens the Template box on the setup thread. On a Mac without the app,
323
331
  the agent gives the download link, and on other computers or over SSH, it
324
- points to the mobile app. When setup finishes, the agent lists the same
325
- choices along with `dvb agents <project>`, which opens the Template box's
326
- agent threads in the terminal (`--workspace` keeps the thread list beside the
327
- open agent).
332
+ points to the mobile app. When setup finishes on a Mac with the desktop app
333
+ installed, `dvb agent-init` opens the app on the setup thread, where the user
334
+ can read the setup agent's summary. Otherwise, the agent lists the same
335
+ choices. Either way, the agent also mentions `dvb agents <project>`, which
336
+ opens the Template box's agent threads in the terminal (`--workspace` keeps
337
+ the thread list beside the open agent).
328
338
 
329
339
  Launch requires the same billing activation as desktop setup. The machine
330
340
  created this way is a normal Template box: it appears in the desktop app,
@@ -29,6 +29,11 @@ final replies, including conversations started in the apps. Search can lag
29
29
  recent messages and returns a bounded result set. Read the thread before
30
30
  continuing it; discovery includes whether it can accept a follow-up now.
31
31
 
32
+ The assistant can also list current and recently finished work across the
33
+ selected projects in one request. Conversations waiting for an answer or
34
+ approval are listed first, and finished ones include the start of the final
35
+ reply.
36
+
32
37
  A new task starts Codex or Claude in a new devbox from the project's saved
33
38
  environment. Finish project setup and save its environment before starting.
34
39
  Continuing an existing thread preserves its context and can wake its sleeping
@@ -36,6 +41,12 @@ devbox. Archived conversations need to be unarchived in boxes.dev first;
36
41
  conversations in storage need to be restored. A history-only conversation
37
42
  cannot continue. These recovery actions are not performed automatically.
38
43
 
44
+ A new task uses the agent's saved model and reasoning effort for the project,
45
+ and its saved speed for Codex, unless the user asks for a specific model,
46
+ reasoning effort or Codex speed. The assistant can choose from the models the
47
+ boxes.dev model picker lists for the account, and the start receipt reports
48
+ what the agent was launched with.
49
+
39
50
  Follow-ups queue by default while an agent is working. Codex also supports
40
51
  steering to redirect current work; Claude steering is unavailable through this
41
52
  connection. Claude follow-ups go directly to its session and do not appear in
@@ -52,10 +63,15 @@ assistant chats. Delivered means the prompt was handed off, not that it
52
63
  executed or completed.
53
64
 
54
65
  Read the conversation for current activity and saved messages. Refresh to see
55
- recent content, or page backward for earlier context. History previews can
56
- omit content and shorten messages; read listed messages in full when needed.
57
- For very large messages omitted from the preview, share the thread link.
58
- Revert or rewind can remove messages from current history.
66
+ recent content, or page backward for earlier context. Reading does not wake a
67
+ sleeping devbox. Activity shows whether the agent is starting, working, waiting
68
+ for input or finished. If the agent last reported work but its devbox is asleep
69
+ or not responding, the status is unverified: that work may have stopped or
70
+ finished, and its state can't be confirmed until the devbox responds again.
71
+
72
+ History previews can omit content and shorten messages; read listed messages in
73
+ full when needed. For very large messages omitted from the preview, share the
74
+ thread link. Revert or rewind can remove messages from current history.
59
75
 
60
76
  There is no per-request result mapping. The latest reply or completion notice
61
77
  may reflect another message, a human's work or a background continuation.
@@ -67,10 +83,11 @@ messages can arrive after an event. Subscriptions need renewal within 24 hours
67
83
  and do not replay old events. Poll current activity when notifications are
68
84
  unavailable or missed; legacy-only sessions may require polling.
69
85
 
70
- For native approvals or interactive questions, share the thread link so the
71
- user can respond in boxes.dev. A question may not appear in saved history and
72
- may reject remote interruption. Sending a queued prompt does not answer the
73
- native dialog.
86
+ For native approvals, interactive questions and boxes.dev permission
87
+ requests, the assistant can show what the agent is waiting on, then share the
88
+ thread link so the user can respond in boxes.dev. A question may not appear in
89
+ saved history and may reject remote interruption. Sending a queued prompt does
90
+ not answer the native dialog.
74
91
 
75
92
  ## Stop work or remove access
76
93
 
@@ -35,6 +35,15 @@ If the title bar shows an Offline or Reconnecting badge, the app itself cannot
35
35
  reach boxes.dev. Threads and status will catch up on their own once the badge
36
36
  clears, so check your network before reloading.
37
37
 
38
+ If the full window stays on **Checking sign-in…** or **Loading workspace…**,
39
+ wait for the **Reload** button to appear after 15 seconds, then choose it to
40
+ reload the desktop app. You can also press Cmd+R.
41
+
42
+ If a reload fails, the desktop app will retry automatically. If the window
43
+ stays on **Still reloading boxes.dev…**, choose **Reload** to start loading
44
+ the app again. If it shows **Can’t reach boxes.dev**, check your connection
45
+ and choose **Retry now**.
46
+
38
47
  If the selected Template box, devbox, or agent seems like it is in a bad state,
39
48
  use **Machine > Reset** from the menu bar. Reset kills all non-essential
40
49
  processes on the selected machine and restarts the boxes.dev daemon.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@boxes-dev/dvb-runtime",
3
- "version": "1.0.1053",
3
+ "version": "1.0.1055",
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-04T22:46:11Z"
80
+ "devboxReleasedAt": "2026-10-05T21:42:37Z"
81
81
  }