@boxes-dev/dvb-runtime 1.0.1079 → 1.0.1081

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
@@ -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]="a941a246-c3be-529b-8bb2-844ad6182b80")}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]="37a3fca6-6f66-5106-99a6-67552067615c")}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";
@@ -64675,9 +64675,9 @@ var init_sentry = __esm({
64675
64675
  uncaughtExceptionMonitorInstalled = false;
64676
64676
  currentDevboxSentryUser = null;
64677
64677
  readBuildMetadata = () => {
64678
- const rawPackageVersion = "1.0.1079";
64679
- const rawGitSha = "b4796ddf10b015d808aba367f5eeb521c6ea0812";
64680
- const rawSentryRelease = "boxes-dev-dvb@1.0.1079+b4796ddf10b015d808aba367f5eeb521c6ea0812";
64678
+ const rawPackageVersion = "1.0.1081";
64679
+ const rawGitSha = "13a23bcb8c308616abb295a6dd2553104ca405c0";
64680
+ const rawSentryRelease = "boxes-dev-dvb@1.0.1081+13a23bcb8c308616abb295a6dd2553104ca405c0";
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.1079";
66897
+ const raw = "1.0.1081";
66898
66898
  return trimVersion(raw);
66899
66899
  };
66900
66900
  readNearestPackageMetadata = (basePath) => {
@@ -80047,4 +80047,4 @@ smol-toml/dist/index.js:
80047
80047
  *)
80048
80048
  */
80049
80049
 
80050
- //# debugId=a941a246-c3be-529b-8bb2-844ad6182b80
80050
+ //# debugId=37a3fca6-6f66-5106-99a6-67552067615c
@@ -250,7 +250,7 @@ sending. Choose a stricter behavior with `--delivery`:
250
250
  | `next` | Starts a turn when the thread is idle, or queues behind the active turn. This is the default. |
251
251
  | `idle` | Starts a turn only when the thread is idle. Active work returns `thread_busy`. |
252
252
  | `queue` | Queues only behind active work. An idle thread returns `turn_not_active`. |
253
- | `steer` | Adds the follow-up to the exact active Codex turn given by `--turn <active-turn-id>`. Claude doesn't support steering. |
253
+ | `steer` | Adds the follow-up to the exact active Codex or Claude turn given by `--turn <active-turn-id>`. |
254
254
 
255
255
  `idle`, `queue`, and `steer` never fall back to another mode. The operation's
256
256
  `disposition` reports what happened: `started` or `steered` with a `turnId`,
@@ -259,6 +259,11 @@ including when that turn is interrupted, and appears in `threads read` once it
259
259
  starts. Take `<active-turn-id>` from the thread's `activeTurnId` in
260
260
  `threads list`.
261
261
 
262
+ Claude will read a steer at its next opportunity without interrupting a running
263
+ tool. Steering requires an updated local boxes.dev service and a running managed
264
+ Claude session. Interactive terminal sessions can't be steered. Answer pending
265
+ questions or approvals in boxes.dev before steering.
266
+
262
267
  A Claude terminal that a person is using stays off limits: the send returns
263
268
  `thread_controlled_elsewhere` and doesn't take over that terminal. Retry an
264
269
  uncertain result only with the same key and identical arguments, including
@@ -30,6 +30,10 @@ a Team Template member project, it is the Team Template's current saved
30
30
  version. Keep the source current when future automation runs need new
31
31
  dependencies, generated files, or shared setup changes.
32
32
 
33
+ Manual and scheduled automations can also send their saved prompt to an
34
+ existing thread you own in the same project. Those runs continue that
35
+ conversation on its current devbox, using the thread's current agent settings.
36
+
33
37
  ## Creating An Automation
34
38
 
35
39
  Open the Automations section in the desktop workbench and choose **New
@@ -40,6 +44,16 @@ API endpoint appears below the prompt.
40
44
  New automations start with the same agent, model, reasoning, and speed defaults
41
45
  that a new project thread would use.
42
46
 
47
+ For drafts with **Only when I click Run now** or **On a schedule** selected,
48
+ **Thread** lets you keep **New devbox and thread on each run** or select an
49
+ existing conversation you own in this project. Search by title to find a thread.
50
+ Changing the destination preserves the draft's prompt and schedule. The
51
+ selected thread must be an available, unarchived Codex or Claude Code thread.
52
+
53
+ You can also open the owned thread's actions menu and choose **Schedule a
54
+ prompt...** to create a draft with that conversation selected. Write the
55
+ prompt and schedule, then create and activate it through the same workflow.
56
+
43
57
  New automations keep their runs **Under this automation**. Change **Where runs
44
58
  appear** to **In the main thread list** when you want runs alongside normal
45
59
  devbox threads instead. Default Slack and Linear integration automations are
@@ -57,12 +71,16 @@ section.
57
71
 
58
72
  Draft automations autosave as you edit them. Active and paused automations do
59
73
  not: because a live automation can spawn runs at any time, your edits are held
60
- as unsaved changes and only take effect when you choose **Save changes**.
74
+ as unsaved changes and only take effect when you choose **Save**.
61
75
  **Revert** discards them and restores the saved version. Unsaved edits are kept
62
76
  on your device, so they survive a page refresh, and are not shared with other
63
77
  devices or people. If the automation changed somewhere else while you had
64
78
  unsaved edits, boxes.dev warns you before you save over the newer version.
65
79
 
80
+ An automation targeting an existing thread keeps that thread in its current
81
+ location. New-thread placement, model controls, completion preferences, Slack
82
+ outputs, and devbox cleanup do not apply to these runs.
83
+
66
84
  Under **More settings**, enable **Mark successful runs as read** when you do not
67
85
  want a completed automation's first response to create an unread dot or a
68
86
  boxes.dev mobile completion notification. Failed runs and runs that need input
@@ -139,6 +157,15 @@ active. API, Slack, and Linear triggers are event-based instead. Separate API
139
157
  requests, Slack threads, or Linear Agent Sessions can start separate automation
140
158
  runs in parallel, subject to awake devbox capacity.
141
159
 
160
+ For an existing-thread target, a scheduled occurrence is skipped when the
161
+ thread is already busy or an earlier prompt is still waiting for delivery.
162
+ If other work starts after that check, the prompt waits in the thread's normal
163
+ message queue. Skipped occurrences do not accumulate for later delivery.
164
+ Archived, deleted, or inaccessible threads cannot receive new prompts; the
165
+ failed run remains visible in history. Restore the target before continuing
166
+ the schedule, or create an automation from another thread. An on-box update
167
+ can also change the target.
168
+
142
169
  ## API Runs
143
170
 
144
171
  New API triggers use configurable requests. Each top-level field is optional:
@@ -266,6 +293,10 @@ awake slot. Sleeping targets wake if capacity is available. The sleep-idle optio
266
293
  to new-devbox requests; a wake blocked by capacity produces a failed run with
267
294
  `startup_active_fork_limit_reached` at its status URL.
268
295
 
296
+ Existing-thread prompts also use the target's current devbox. A sleeping
297
+ devbox will need to wake before delivery, subject to normal billing and
298
+ capacity checks.
299
+
269
300
  ## Automation Devbox Cleanup
270
301
 
271
302
  Scheduled and API automations whose runs stay nested under the automation can
@@ -300,6 +331,8 @@ Changing the setting applies only to future scheduled or API runs and future
300
331
  before explicitly applying the current policy to older eligible runs.
301
332
  Manual-only, Slack, Linear, and main-thread-list runs are not eligible for
302
333
  automation devbox cleanup.
334
+ Runs targeting an existing thread never make that thread's devbox eligible
335
+ for automation cleanup.
303
336
 
304
337
  If automatic cleanup repeatedly cannot access or destroy a devbox, boxes.dev
305
338
  stops after eight failed attempts instead of retrying forever. The affected run
@@ -315,6 +348,13 @@ Linear integration runs always use the main thread list. A run can be starting,
315
348
  ready, skipped, or failed. Ready runs have a child thread you can open like any
316
349
  other thread.
317
350
 
351
+ Existing-thread runs link to their target conversation and show prompt
352
+ delivery separately: **Sending**, **Sent**, or **Unconfirmed**, as well as
353
+ skips and failures. **Sent** means the thread accepted the prompt, possibly
354
+ into its message queue; it does not mean the agent finished the work.
355
+ **Unconfirmed** means delivery could not be established, so inspect the
356
+ conversation before submitting the prompt again.
357
+
318
358
  An automation run's devbox can be moved into a project folder from its existing
319
359
  **Move to** menu in either destination. A run under its automation stays there
320
360
  and also appears in the assigned folder; a run in the main thread list moves
@@ -336,11 +376,15 @@ prompt came from the saved automation, an API request, or trigger context.
336
376
  Editing the automation later affects future runs, not existing run history.
337
377
  Older runs created before launch snapshots were recorded show that information
338
378
  as unavailable instead of guessing from the automation's current settings.
379
+ Existing-thread runs keep the saved prompt but use the target's current
380
+ settings; they do not record a new-thread model selection.
339
381
 
340
382
  Manually destroying and archiving a run's devbox also preserves its run ID,
341
383
  recorded settings, and archived thread in run history. Explicitly deleting a
342
384
  saved run removes its history record. Previously deleted run records remain
343
385
  unavailable.
386
+ An existing-thread run can be deleted without deleting its target conversation
387
+ or devbox.
344
388
 
345
389
  Choose **View run history** from an automation's overflow menu to see every
346
390
  recorded run. Select a run to open its status, timing, trigger, and support
@@ -18,6 +18,11 @@ A team admin opens **Integrations → AWS** in the desktop app and chooses
18
18
  - the AWS region where the company configured IAM Identity Center, such as
19
19
  `us-east-1`.
20
20
 
21
+ The access portal shows both values: choose **Access keys** next to any
22
+ permission set, then read the SSO Start URL and SSO Region under **AWS IAM
23
+ Identity Center credentials**. An address copied from the browser with the
24
+ portal's `#/` page suffix also works.
25
+
21
26
  Starting the normal AWS sign-in validates these details before boxes.dev saves
22
27
  them for the team. The admin then finishes company sign-in and chooses an
23
28
  assigned account and permission set for the current project.
@@ -505,6 +505,60 @@ Desktop and mobile threads are usually easier for conversational work. CLI
505
505
  agent commands are most useful when you want the agent in a terminal-oriented
506
506
  workflow.
507
507
 
508
+ ## Manage MCPs
509
+
510
+ You can manage the same centrally connected MCPs as **Integrations → MCPs** in
511
+ the desktop app from a terminal, which is useful on Linux, Windows, over SSH,
512
+ or without the desktop app. Run these commands on your own computer, not inside
513
+ a box.
514
+
515
+ ```bash
516
+ dvb mcp list
517
+ dvb mcp list --project my-app
518
+ dvb mcp add https://mcp.linear.app/mcp --project my-app
519
+ dvb mcp authorize linear --agent codex
520
+ dvb mcp remove linear --agent claude
521
+ dvb mcp remove linear
522
+ ```
523
+
524
+ `dvb mcp list` shows your own MCPs with their id, the name the agents use, the
525
+ project (or all projects) they're available in, and each agent's status. With
526
+ `--project`, it lists everything available in that project, including MCPs
527
+ your team manages. Commands that take a connection accept its id, the name the
528
+ agents use, or its display name. If a name matches more than one MCP, add
529
+ `--project` or use the id.
530
+
531
+ `dvb mcp add` accepts a server URL or the `codex mcp add` or `claude mcp add`
532
+ command a provider gave you. boxes.dev reads the command but never runs it.
533
+ Quote the command, or put it after `--`:
534
+
535
+ ```bash
536
+ dvb mcp add --all-projects -- claude mcp add --transport http notion https://mcp.notion.com/mcp
537
+ ```
538
+
539
+ New MCPs are added to the project you choose with `--project`. If you have only
540
+ one project, the MCP is added there; use `--all-projects` to make it available
541
+ everywhere. Codex and Claude are both added unless you pass `--agent`, or the
542
+ pasted command belongs to one agent. Pass API keys with
543
+ `--header "Authorization: Bearer <key>"`. For a server that works with or
544
+ without an account, `--no-sign-in` adds it without signing in. Use `--name` to
545
+ choose the MCP's name, which the agents also use.
546
+
547
+ For an OAuth MCP, `dvb mcp add` signs in each agent right away, one consent
548
+ for Codex and one for Claude. Add `--no-authorize` to sign in later with
549
+ `dvb mcp authorize`.
550
+
551
+ When you sign in, the command prints a sign-in link and opens it in your
552
+ browser when one is available on this computer. In an SSH session, or with
553
+ `--no-browser`, open the link in a browser on any computer. After you approve
554
+ access, the browser will end on a `http://127.0.0.1:...` page that doesn't
555
+ load. Copy that page's full address and paste it into the terminal to finish.
556
+
557
+ `dvb mcp remove <connection>` removes the MCP for every agent.
558
+ `--agent codex` or `--agent claude` removes it from one agent and keeps the
559
+ connection. An MCP your team manages can only be removed from one agent at a
560
+ time.
561
+
508
562
  ## Copy Files Into A Machine
509
563
 
510
564
  Use:
@@ -11,11 +11,12 @@ The workbench has a few persistent areas:
11
11
 
12
12
  - The top bar is split at the left pane's edge. The left pane's own top area
13
13
  shows the project selector, a back button, a crosshair button, a thread
14
- search button, and a usage icon (billing usage details on hover, when relevant). The back button retraces earlier workbench
14
+ search button, and a usage icon (billing
15
+ usage details on hover, when relevant). The back button retraces earlier workbench
15
16
  selections, so an integration or automation detour can return to the thread
16
17
  you were viewing. It is disabled until there is somewhere to return. The
17
18
  crosshair button scrolls the thread list to the selected thread, first
18
- expanding the Devboxes or Template box section, folder, or devbox that hides
19
+ expanding Devboxes or Project and the Template box row, folder, or devbox that hides
19
20
  it. It is disabled when no thread is selected and hidden when the left pane
20
21
  is too narrow to fit it. A thread inside a collapsed automation stays hidden
21
22
  until you expand that automation. The
@@ -26,16 +27,25 @@ The workbench has a few persistent areas:
26
27
  If the app loses its connection, an Offline or Reconnecting badge appears
27
28
  beside the pane control and clears on its own once boxes.dev is reachable
28
29
  again.
29
- - The left pane lists threads, integrations, automations, Project URLs, an
30
- expandable Settings section, and the Template box when that project has one.
30
+ - The left pane starts with Devboxes and its **New thread** header button,
31
+ followed by Automations and Project. Expand Project for Integrations,
32
+ Project URLs, Public links when active, sharing, and the Template box when
33
+ the project has one. The gear on the Project header opens Project settings,
34
+ including while the section is collapsed. Tool rows open list pages in the
35
+ detail pane; choose an integration or Project URL to open its settings.
36
+ Shared with me opens the account-wide list of saved teammate conversations.
37
+ Shared by me expands this project's shares and access requests. Sharing
38
+ rows appear when they have items. Collapsed Project and Template box controls
39
+ retain cues for activity, unread updates, or attention in their contents.
31
40
  Your account identity and a Help button stay pinned at the bottom.
32
41
  Once you've sent messages in three threads (not counting project setup
33
42
  threads), a **Code on the go!** banner appears above your account if you
34
43
  haven't signed in to the mobile app. Scan its QR code to download the mobile
35
44
  app, or select **X** to dismiss it for this account on this computer. Signing
36
45
  in on mobile will also hide the banner.
37
- - The detail pane shows the selected thread, Project settings, an integration,
38
- an automation editor, or the Template box page when available.
46
+ - The detail pane shows the selected thread, Project settings, a project tool
47
+ list or detail page, an automation editor, or the Template box page when
48
+ available.
39
49
  - The Terminal, Files, Git/Review, and Browser panes can be shown next to the
40
50
  agent pane; Files, Git/Review, and Browser can also pop out into
41
51
  near-full-window overlays.
@@ -117,11 +127,11 @@ Cmd; Windows and Linux use the Ctrl-based equivalents shown in parentheses.
117
127
 
118
128
  Threads:
119
129
 
120
- - New devbox + thread: **Cmd+N** (Ctrl+N)
130
+ - New thread: **Cmd+N** (Ctrl+N)
121
131
  - New thread on the Template box: **Cmd+Shift+N** (Ctrl+Shift+N)
122
132
  - Previous / next thread: **Cmd+Shift+[** / **Cmd+Shift+]** (Ctrl+Shift+[ /
123
- Ctrl+Shift+]). Navigation follows the visible sidebar order, including
124
- **Shared with me**.
133
+ Ctrl+Shift+]). Navigation follows the visible sidebar threads. Shared
134
+ conversations are opened from the **Shared with me** page.
125
135
  - Jump to one of your first nine visible threads: **Cmd+1** through **Cmd+9**
126
136
  (Ctrl+1 through Ctrl+9). The numbers follow the current sidebar order;
127
137
  collapsed threads and **Shared with me** do not take a slot.
@@ -188,7 +198,7 @@ Use the project selector in the titlebar to switch between projects on the same
188
198
  desktop app account. Threads and devboxes are shown for the selected project.
189
199
  Most projects have one Template box. A project created through a Team
190
200
  Template's **Member projects** mode has no personal Template box and omits that
191
- section without changing its normal thread and devbox workflow.
201
+ row without changing its normal thread and devbox workflow.
192
202
 
193
203
  Use **New project...** in the project selector to add another project. On
194
204
  macOS, **File > New Project...** does the same thing.
@@ -249,9 +259,9 @@ runtime has no live metrics.
249
259
 
250
260
  ## Project Settings
251
261
 
252
- Expand **Settings** near the bottom of the project thread list and open
253
- **Project settings** for settings that belong to the project rather than to a
254
- particular machine. This page contains **Project storage**, **Git**, **Agent
262
+ Choose the gear on the sidebar's **Project** header for
263
+ settings that belong to the project rather than to a particular box. This
264
+ page contains **Project storage**, **Git**, **Agent
255
265
  permissions for this project**, **Devbox lifecycle**, and **Agent settings**,
256
266
  including the project's preferred Git action, commit thread-link behavior,
257
267
  startup script, shared agent guidance, automatic waking of sleeping machines,
@@ -267,11 +277,11 @@ Changes apply to existing and new boxes. A running box may keep its current
267
277
  sleep deadline until its next activity; saving will not wake a sleeping box.
268
278
  Longer timeouts use more box-hours; active agents can still keep boxes awake.
269
279
 
270
- The same Settings section opens **Desktop app settings...** and **Configure
271
- agents...** in separate windows. Desktop app settings contains only preferences
272
- for the app and terminal on this computer. The account identity at the bottom
273
- of the left pane opens account, billing, team, update, and log-out actions
274
- without mixing those controls into project settings.
280
+ Open the account menu at the bottom of the left pane for **Desktop app
281
+ settings...** and **Configure agents...**. Desktop app settings contains
282
+ preferences for the app and terminal on this computer; Configure agents
283
+ manages Codex and Claude accounts and API keys. The menu also contains
284
+ keyboard shortcuts, account, billing, team, update, and log-out actions.
275
285
 
276
286
  ## Template box
277
287
 
@@ -281,11 +291,17 @@ the machine itself; open its terminal, inspect files or Git, or check whether
281
291
  it is awake. Team Template member projects omit the page and its thread,
282
292
  snapshot, repository, terminal, and power controls.
283
293
 
284
- Use the terminal button in the Template box header to replace the Template box
294
+ Under **Project**, select the **Template box** row's title to open its page.
295
+ The chevron expands its threads, including pinned and archived conversations.
296
+ Hover or focus the row for **New thread on Template box** and its **…** menu.
297
+ The menu contains terminal, snapshot, and sleep actions.
298
+
299
+ Choose **Open Template box terminal** from that menu to replace the Template box
285
300
  page with its terminal in the main pane. While it is there, Terminal is
286
301
  unavailable as the right-side pane, but Files, Git/Review, and Browser continue
287
- to work there normally. Use the same button again, or close the last terminal
288
- tab, to restore the Template box page.
302
+ to work there normally. Select the Template box title, choose **Restore
303
+ Template box details** from its menu, or close the last terminal tab to restore
304
+ its page.
289
305
 
290
306
  Work that should not change the Template box directly should usually start on a
291
307
  devbox. See `fork-workflows.md` for that workflow.
@@ -373,6 +389,27 @@ after it sleeps. Older app versions, Slack, and copied transcripts show the
373
389
  ordinary link. See `onbox-agent-tools.md` for the commands agents use to
374
390
  publish visuals.
375
391
 
392
+ Agents can also present images and videos, such as screenshots of a change or
393
+ a recording of a test, in their final reply. Each group of published links
394
+ appears as a row of up to four previews with the file captions below them;
395
+ when there are more than four files, the fourth slot shows how many more there
396
+ are and opens the first of them. Selecting a preview opens a viewer that shows
397
+ one file at a time in the agent's order. The arrow buttons or the Left and
398
+ Right arrow keys move between files and wrap at either end, Home and End jump
399
+ to the first and last file, the download button saves the current file, and
400
+ Escape closes the viewer. While a video has focus, the arrow keys control the
401
+ video instead. Videos never play automatically, and moving to another file
402
+ stops playback. Images open in the zoom viewer. A file that can't load shows
403
+ **Retry**, plus **Open** in the strip.
404
+
405
+ Published images and videos don't depend on the devbox, so they keep loading
406
+ after it sleeps or is deleted. Older app versions, Slack, and copied
407
+ transcripts show ordinary links to each file's boxes.dev page, which requires
408
+ signing in and offers a download. Images an
409
+ agent only looks at while it works fold with the rest of a finished turn's
410
+ activity, so they don't appear in the reply unless the agent presents them.
411
+ See `onbox-agent-tools.md` for the publishing command.
412
+
376
413
  Claude's active and recently finished subagents appear above the composer.
377
414
  Open an agent from that list or its launch card to read its transcript, and use
378
415
  **Back** or **Escape** to return to the parent thread and focus its composer.
@@ -386,8 +423,8 @@ logos** in **Desktop app settings > General > Thread list**. The logos appear
386
423
  at the right edge of thread rows and are off by default.
387
424
 
388
425
  Thread rows can show unread or attention state. When a thread completes, fails,
389
- or asks for input while the app is not focused, boxes.dev can request desktop
390
- attention and, depending on settings, show a desktop notification.
426
+ or asks for input while the app is not focused, boxes.dev can show a desktop
427
+ notification according to your notification settings.
391
428
 
392
429
  The menu for an eligible non-archived thread includes **Mark unread**. The
393
430
  thread stays unread until you open it again, and the same state appears in the
@@ -402,19 +439,39 @@ finishes. **Unmute notifications** turns them back on.
402
439
  Desktop completion notifications are controlled in **Desktop app settings >
403
440
  Notifications**:
404
441
 
405
- - **Never** turns completion notifications off.
442
+ - **Never** turns banners and sounds off for completed replies, failures, and
443
+ requests for input.
406
444
  - **Only when unfocused** is the default and notifies only after the workbench
407
445
  loses focus.
408
446
  - **Always** can also notify for an unselected thread while the workbench is
409
447
  focused. It never notifies for the thread currently being viewed while the
410
448
  workbench is focused.
411
449
 
450
+ **Play notification sounds** is on by default. Turn it off to keep banners
451
+ without sound. Update the desktop app if this control is missing. Agent replies
452
+ do not ring the terminal bell or bounce the Dock icon; terminal bells have
453
+ their own settings under **Terminal settings > Behavior > Bell**.
454
+
412
455
  Eligible controlled Codex completion notifications include the final-response
413
456
  preview when it is available and a generic completion preview during recovery;
414
457
  failures include a status preview. Selecting a notification opens its project
415
458
  and thread. Delivery also depends on the operating system's notification
416
459
  settings for boxes.dev.
417
460
 
461
+ **Account → Notifications → Quiet hours** sets a daily interval shared with
462
+ mobile and your other computers. Each device uses its own timezone. Use the
463
+ account menu's **Pause notifications for 1 hour** to silence agent alerts on
464
+ every device for this account until the same end time; **Resume notifications**
465
+ ends that pause early, while daily quiet hours still apply. The Account page
466
+ has the same pause and resume controls.
467
+
468
+ Quiet hours and pause cover replies, failures, input requests, and teammate-agent
469
+ alerts even while you use the desktop app. They preserve unread markers and
470
+ pending requests, and suppressed alerts do not replay later. Terminal bells
471
+ remain separately controlled. A notification already being prepared or delivered
472
+ may arrive after a preference changes. Desktop applies these once the app has
473
+ loaded the current web update; no desktop app update is needed.
474
+
418
475
  A selected thread that completes while the workbench is in the background
419
476
  remains unread until the workbench returns to the foreground. On macOS, it
420
477
  contributes to the Dock unread count when **Unread badge** is enabled. Desktop
@@ -512,6 +569,12 @@ choice. Profile reset is the separate destructive action.
512
569
  Browser can also pop out from the side pane into
513
570
  a near-full-window overlay and dock back into the workbench.
514
571
 
572
+ The mobile app's Browser shares these tabs and profile. Opening it on a phone
573
+ resizes the shared browser to the phone's screen, and with the default
574
+ streaming setting the pane keeps showing its last picture. Moving the pointer
575
+ into the pane, or focusing it, resizes the browser back to the pane. See
576
+ `mobile.md`.
577
+
515
578
  **Account → Advanced → Browser streaming** chooses how the Browser pane
516
579
  receives the remote page: **JPEG** (the default), **H.264 video**, **WebRTC
517
580
  via relay**, or **WebRTC direct**, which uses the relay when a direct
@@ -523,12 +586,13 @@ updated to support the option yet, or a WebRTC option can't get relay access,
523
586
  Browser keeps JPEG and shows a short notice.
524
587
 
525
588
  When a site opens a foreground page, Browser selects that page and scrolls its
526
- tab into view, including when the tab strip overflows. A shadow and right-arrow
527
- control at the strip's edge reveal more tabs without a horizontal-scroll
528
- gesture. When a large saved profile is restored, Browser makes one prepared
529
- page usable first while the remaining tabs finish opening in the background. If
530
- Browser startup or its process stops, the opening view is replaced by an error
531
- with a **Restart browser** action; restarting preserves the same profile data.
589
+ tab into view, including when the tab strip overflows. When the tabs don't fit,
590
+ arrow buttons on both sides of the strip scroll it left and right, and a shadow
591
+ marks each edge that has more tabs beyond it. When a large saved profile is
592
+ restored, Browser makes one prepared page usable first while the remaining tabs
593
+ finish opening in the background. If Browser startup or its process stops, the
594
+ opening view is replaced by an error with a **Restart browser** action;
595
+ restarting preserves the same profile data.
532
596
 
533
597
  The runtime has no security key or platform authenticator of its own. In the
534
598
  desktop app, Browser-pane passkey forwarding is off by default and can be
@@ -629,8 +693,18 @@ human guides at `https://boxes.dev/help`. It opens in the external browser and
629
693
  keeps the working conversation in the desktop app. The existing quick fixes
630
694
  and Send feedback action remain in the Help dialog.
631
695
 
632
- When a desktop update has downloaded, the titlebar can show a restart-to-update
633
- action and release notes link. The app menu also includes update actions.
696
+ When a desktop update has downloaded, the titlebar shows a **Click to update**
697
+ button. Clicking it restarts the app into the new version. The button turns from blue to yellow
698
+ after the update has waited a day, and to red after three days. It is grayed
699
+ out while project setup is reading files from this computer, because the app
700
+ can't restart then. Quitting the app also installs a downloaded update, without
701
+ reopening the app; the next launch runs the new version. The app menu also
702
+ includes update actions.
703
+
704
+ When boxes.dev needs a newer desktop app, the app keeps working until that
705
+ update has downloaded, then shows a screen asking you to restart to update. If
706
+ a required update fails to download, the titlebar shows a red **Retry update**
707
+ button.
634
708
 
635
709
  On macOS, the app clears recognized leftover update downloads and installation
636
710
  files from older releases when it starts. Files for the current release or a
@@ -446,7 +446,9 @@ Already-approved grants won't produce an update prompt. Email access uses the
446
446
  user's separate **Update connection** link in Account. Connected personal access
447
447
  that lacks email scopes or cannot publish check runs will link to **Disconnect
448
448
  personal access** instead. No guidance switches credentials, blocks, retries,
449
- or replays the original command. After approval, retry it explicitly.
449
+ or replays the original command. Because the link appears before the command
450
+ runs, retry the command explicitly after approval only if GitHub denied it. A
451
+ command that succeeded didn't need the update, so don't run it again.
450
452
  Other GitHub failures do not automatically start authorization. A command that
451
453
  needs a permission the App lacks fails with GitHub's `Resource not accessible
452
454
  by integration` error; see "GitHub CLI Command Is Denied" in
@@ -645,6 +647,11 @@ the meantime, its follow-up starts right away and includes the waiting
645
647
  comments. The agent replies to or resolves review conversations only
646
648
  when your instructions or the project's agent guidance tell it to.
647
649
 
650
+ While a Codex agent is working, its follow-up waits for the current turn to
651
+ finish. Later events join a waiting follow-up that already covers those kinds,
652
+ even if a follow-up for a different kind of event was queued more recently.
653
+ The agent reads the pull request's current state when the follow-up starts.
654
+
648
655
  GitHub does not announce new merge conflicts, so boxes.dev checks the pull
649
656
  request about ten minutes after its base branch changes, or an hour after the
650
657
  last conflict follow-up if that is later. When GitHub reports a
@@ -666,6 +673,11 @@ deleted threads will not receive it. Turning follow-ups off will also turn off
666
673
  the merge notice. Closing a pull request without merging will end follow-ups
667
674
  silently.
668
675
 
676
+ When a pull request closes or merges, boxes.dev also tries to cancel its waiting
677
+ automatic repairs. A repair already being sent to the agent or running can
678
+ finish. Your queued messages and follow-ups for other pull requests stay in
679
+ place.
680
+
669
681
  Only one agent thread per boxes.dev account can handle follow-ups for a pull
670
682
  request at a time. Turning them on from another thread will show the current
671
683
  thread and ask you to move the job. While that thread is still available,
@@ -26,7 +26,7 @@ Team Template.
26
26
 
27
27
  ## Creating A New Devbox + Thread
28
28
 
29
- Start from **New devbox + thread** in the desktop thread list. Choose the agent,
29
+ Start from **New thread** in the desktop thread list. Choose the agent,
30
30
  then send the first prompt. In an ordinary project, the devbox starts from the
31
31
  latest verified Template box snapshot. In a Team Template member project, it
32
32
  starts from the Team Template's current saved version.
@@ -355,7 +355,7 @@ threads return to the active list untouched. Preserving the transcripts does
355
355
  not wake the Template box or copy native transcript files onto it. After the
356
356
  selected devbox is destroyed, desktop opens the no-thread-selected state. It
357
357
  does not automatically create another draft or devbox; use
358
- **New devbox + thread** when more isolated work is needed.
358
+ **New thread** when more isolated work is needed.
359
359
 
360
360
  If a Codex or Claude turn is still working when destruction is confirmed,
361
361
  boxes.dev stops that turn before preserving the transcript. Other active agent