@boxes-dev/dvb-runtime 1.0.1127 → 1.0.1131

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.
Files changed (59) hide show
  1. package/dist/bin/dvb.mjs +336 -197
  2. package/dist/bin/dvbd.mjs +23 -12
  3. package/dist/postgres-tools/SHA256SUMS +39 -39
  4. package/dist/postgres-tools/darwin-universal/bin/pg_dump +0 -0
  5. package/dist/postgres-tools/darwin-universal/bin/pg_restore +0 -0
  6. package/dist/postgres-tools/darwin-universal/lib/libcom_err.3.0.dylib +0 -0
  7. package/dist/postgres-tools/darwin-universal/lib/libcrypto.3.dylib +0 -0
  8. package/dist/postgres-tools/darwin-universal/lib/libgssapi_krb5.2.2.dylib +0 -0
  9. package/dist/postgres-tools/darwin-universal/lib/libk5crypto.3.1.dylib +0 -0
  10. package/dist/postgres-tools/darwin-universal/lib/libkrb5.3.3.dylib +0 -0
  11. package/dist/postgres-tools/darwin-universal/lib/libkrb5support.1.1.dylib +0 -0
  12. package/dist/postgres-tools/darwin-universal/lib/liblz4.1.11.1.dylib +0 -0
  13. package/dist/postgres-tools/darwin-universal/lib/libpq.5.dylib +0 -0
  14. package/dist/postgres-tools/darwin-universal/lib/libssl.3.dylib +0 -0
  15. package/dist/postgres-tools/darwin-universal/lib/{libz.1.3.2.dylib → libz.1.4.dylib} +0 -0
  16. package/dist/postgres-tools/darwin-universal/lib/libzstd.1.dylib +0 -0
  17. package/dist/postgres-tools/darwin-universal/notices/PostgreSQL.txt +1 -1
  18. package/dist/postgres-tools/darwin-universal/notices/THIRD_PARTY_NOTICES.txt +87 -1
  19. package/dist/postgres-tools/linux-arm64-el8/bin/pg_dump +0 -0
  20. package/dist/postgres-tools/linux-arm64-el8/bin/pg_restore +0 -0
  21. package/dist/postgres-tools/linux-arm64-el8/lib/libpq.so.5 +0 -0
  22. package/dist/postgres-tools/linux-arm64-el9/bin/pg_dump +0 -0
  23. package/dist/postgres-tools/linux-arm64-el9/bin/pg_restore +0 -0
  24. package/dist/postgres-tools/linux-arm64-el9/lib/libpq.so.5 +0 -0
  25. package/dist/postgres-tools/linux-arm64-ubuntu22.04/bin/pg_dump +0 -0
  26. package/dist/postgres-tools/linux-arm64-ubuntu22.04/bin/pg_restore +0 -0
  27. package/dist/postgres-tools/linux-arm64-ubuntu22.04/lib/libpq.so.5 +0 -0
  28. package/dist/postgres-tools/linux-arm64-ubuntu24.04/bin/pg_dump +0 -0
  29. package/dist/postgres-tools/linux-arm64-ubuntu24.04/bin/pg_restore +0 -0
  30. package/dist/postgres-tools/linux-arm64-ubuntu24.04/lib/libpq.so.5 +0 -0
  31. package/dist/postgres-tools/linux-x64-el8/bin/pg_dump +0 -0
  32. package/dist/postgres-tools/linux-x64-el8/bin/pg_restore +0 -0
  33. package/dist/postgres-tools/linux-x64-el8/lib/libpq.so.5 +0 -0
  34. package/dist/postgres-tools/linux-x64-el9/bin/pg_dump +0 -0
  35. package/dist/postgres-tools/linux-x64-el9/bin/pg_restore +0 -0
  36. package/dist/postgres-tools/linux-x64-el9/lib/libpq.so.5 +0 -0
  37. package/dist/postgres-tools/linux-x64-ubuntu22.04/bin/pg_dump +0 -0
  38. package/dist/postgres-tools/linux-x64-ubuntu22.04/bin/pg_restore +0 -0
  39. package/dist/postgres-tools/linux-x64-ubuntu22.04/lib/libpq.so.5 +0 -0
  40. package/dist/postgres-tools/linux-x64-ubuntu24.04/bin/pg_dump +0 -0
  41. package/dist/postgres-tools/linux-x64-ubuntu24.04/bin/pg_restore +0 -0
  42. package/dist/postgres-tools/linux-x64-ubuntu24.04/lib/libpq.so.5 +0 -0
  43. package/dist/postgres-tools/release.json +95 -95
  44. package/dist/product-docs/references/agent-tools.md +8 -2
  45. package/dist/product-docs/references/automations.md +37 -8
  46. package/dist/product-docs/references/aws.md +9 -6
  47. package/dist/product-docs/references/billing-and-limits.md +41 -23
  48. package/dist/product-docs/references/cli.md +18 -0
  49. package/dist/product-docs/references/desktop-workbench.md +42 -14
  50. package/dist/product-docs/references/files-git-and-review.md +31 -12
  51. package/dist/product-docs/references/managed-environment-files.md +24 -1
  52. package/dist/product-docs/references/mobile.md +22 -9
  53. package/dist/product-docs/references/onbox-agent-tools.md +77 -6
  54. package/dist/product-docs/references/security-and-data.md +12 -0
  55. package/dist/product-docs/references/slack.md +20 -8
  56. package/dist/product-docs/references/threads-and-agents.md +92 -45
  57. package/dist/product-docs/references/ui-references.md +5 -3
  58. package/package.json +2 -2
  59. package/dist/postgres-tools/darwin-universal/lib/liblz4.1.10.0.dylib +0 -0
@@ -114,9 +114,12 @@ command runs its next command with the old settings, so press Enter once first.
114
114
  Values the user set in the shell stay unchanged. Existing Codex and Claude
115
115
  sessions keep current work running, then pick up AWS before their next turn:
116
116
  boxes.dev refreshes their idle agent process after its work drains. This also
117
- applies to Claude sessions opened from mobile. Programs that are already running,
118
- including ones started from a terminal, keep the environment they started
119
- with. Devbox startup and teardown scripts and Template box maintenance scripts
117
+ applies to Claude sessions opened from mobile. For Codex, that work includes
118
+ commands still running in a background terminal, such as a dev server, so the
119
+ refresh never stops them. Until they end, Codex threads that were already open
120
+ keep the earlier AWS settings, while new Codex threads use the current ones.
121
+ Programs that are already running, including ones started from a terminal,
122
+ keep the environment they started with. Devbox startup and teardown scripts and Template box maintenance scripts
120
123
  receive the same defaults as a new terminal.
121
124
 
122
125
  For a connected project, boxes.dev manages an AWS profile named `boxes-dev` on
@@ -204,9 +207,9 @@ merges those unrelated settings without replacing the current AWS config or
204
207
  overwriting boxes.dev-managed profile sections.
205
208
 
206
209
  Profile names starting with `boxes-` in `~/.aws/config` belong to boxes.dev.
207
- During each sync and before an agent starts, boxes.dev restores those sections
208
- from the project's AWS settings and removes managed names that are no longer
209
- configured. This also repairs edits that strip or damage the ownership comments,
210
+ During each sync, which runs at least once a minute, boxes.dev restores those
211
+ sections from the project's AWS settings and removes managed names that are no
212
+ longer configured. This also repairs edits that strip or damage the ownership comments,
210
213
  change a helper command, or duplicate a managed section. Other profiles,
211
214
  comments, and settings are preserved, including aliases such as `oro-staging`
212
215
  that call a managed profile's helper. Change managed access through the AWS page;
@@ -96,10 +96,21 @@ checkout, choose a paid plan, or add a payment method from billing.
96
96
  Paid plans apply to assigned paid seats. Team admins can assign and remove paid
97
97
  seats from Billing on the website. A paid plan keeps at least one paid seat, so
98
98
  the last paid seat offers Cancel plan instead of Remove seat. To stop paying, a
99
- team admin needs to select Cancel plan there or at the bottom of Billing on the
100
- website. Cancellation takes effect at the end of the billing period, and the
99
+ team admin needs to select Cancel plan there, at the bottom of Billing on the
100
+ website, or under **Renewal** in the desktop app's **Settings → Billing &
101
+ usage**. Cancellation takes effect at the end of the billing period, and the
101
102
  plan and its seats stay active until then. Keep plan undoes a scheduled
102
- cancellation.
103
+ cancellation and needs a card on file, because the plan will renew.
104
+
105
+ A team admin can remove the team's saved card with **Remove card**, under
106
+ **Payment** on the website or **Payment method** in the desktop app. While the
107
+ plan is set to renew, boxes.dev refuses and asks the admin to cancel the plan
108
+ first. Once the plan is cancelled or set to end on a date, removing the card
109
+ removes every saved card from the team's billing account, turns off
110
+ auto-reload, and leaves the plan active until its end date. On a trial that
111
+ requires a card, trial compute stops until a card is added again. The admin can
112
+ add a card again anytime. Adding or updating the card makes it the card that
113
+ renewals and auto-reload charge.
103
114
 
104
115
  Paid seats receive the plan's included box-hours each billing period. If usage
105
116
  goes beyond the included amount, boxes.dev uses prepaid overage credits when
@@ -113,22 +124,28 @@ If a team member is not a team admin, billing controls usually show status and
113
124
  tell the member to contact a team admin.
114
125
 
115
126
  New teams that sign up at boxes.dev/conductor will receive one month of Pro
116
- free. The account that creates the team will get the first Pro seat, including
117
- 300 box-hours each month. Extra usage will require prepaid credits. Pro will
118
- end when the offer does unless a team admin chooses **Keep plan** in Billing;
119
- continuing will use the normal Pro price. The offer does not replace an
120
- existing account's or team's billing.
121
-
122
- The three-month Pro offers at boxes.dev/launch-yc and boxes.dev/alien are
123
- closed to new teams. boxes.dev/launch-yc shows the homepage with a notice that
124
- the offer has ended and that new users can still sign up for the free trial,
125
- and boxes.dev/alien opens the homepage. Teams that already claimed one keep it
126
- on the same terms. The boxes.dev/launch-yc offer
127
- required a card, which is not charged automatically for extra usage or to renew
128
- Pro. Each card could claim it for only one team. If the offer didn't attach
129
- when the team was created, or boxes.dev later can't accept the card used for
130
- it, a banner will ask the user to add a card to claim Pro until the original
131
- offer would have ended.
127
+ free, and new teams that sign up at boxes.dev/launch-yc until November 21,
128
+ 2026 will receive three months. The account that creates the team will get the
129
+ first Pro seat, including 300 box-hours each month. Extra usage will require
130
+ prepaid credits. Pro will end when the offer does unless a team admin chooses
131
+ **Turn on renewal** in Billing, which needs a card on file; Pro will then renew
132
+ at the normal Pro price. The offer does not replace an existing account's or
133
+ team's billing.
134
+
135
+ Only boxes.dev/launch-yc asks for a card, to prevent abuse of the offer.
136
+ Choose **Continue without a card** to take the smaller trial with 20 free
137
+ box-hours instead. The card is not charged automatically for extra usage or to
138
+ renew Pro, and a team admin can remove it in Billing at any time; Pro stays
139
+ active until the offer ends. Each card can claim the offer for only one team,
140
+ and the card's bank needs to confirm its security code. If the bank doesn't, the user can add a
141
+ different card or continue with the trial. If the offer didn't attach when the
142
+ team was created, or boxes.dev later can't accept the card used for it, a
143
+ banner will ask the user to add a card to claim Pro until the original offer
144
+ would have ended.
145
+
146
+ The three-month Pro offer at boxes.dev/alien is closed to new teams, and that
147
+ address opens the homepage. Teams that already claimed it keep it on the same
148
+ terms.
132
149
 
133
150
  ## Overage Credits
134
151
 
@@ -246,15 +263,16 @@ hi@boxes.dev for a higher-limit use case.
246
263
  ## Billing Surfaces
247
264
 
248
265
  Users can manage billing in the web app at Team Billing. The desktop app also
249
- has **Settings → Billing & usage** for usage history, payment method, plan,
250
- prepaid credits, and credit balance. **Manage billing** in the sidebar's usage
266
+ has **Settings → Billing & usage** for usage history, payment method, plan and
267
+ renewal, prepaid credits, and credit balance. **Manage billing** in the sidebar's usage
251
268
  popover opens that section at usage history. The Stripe portal opens in the browser for hosted Stripe
252
269
  account management.
253
270
 
254
271
  Common team-admin actions:
255
272
 
256
- - Add or update the team payment method.
257
- - Choose, switch, or cancel a paid plan.
273
+ - Add, update, or remove the team's card.
274
+ - Choose, switch, or cancel a paid plan, keep a cancelled plan, or turn on
275
+ renewal for a plan that is set to end, such as a signup offer.
258
276
  - Assign or remove paid seats.
259
277
  - Buy prepaid usage credits.
260
278
  - Configure auto-reload.
@@ -514,6 +514,17 @@ empty thread and defaults to deletion when reopening is available. Deletion
514
514
  also removes a devbox created for that thread. Choosing keep preserves the row;
515
515
  an abrupt disconnect also preserves it without prompting.
516
516
 
517
+ Before the native terminal opens, Ctrl+C will cancel an accepted empty startup
518
+ and clean up its thread. A devbox you selected with `--devbox` will be kept.
519
+ If startup has not returned a thread yet or cleanup cannot finish, open
520
+ `dvb agents` to review the saved state and retry cleanup if needed.
521
+
522
+ Deleting an empty first thread on a previously standalone devbox will keep the
523
+ other threads, their histories, and the devbox's name and folder. Another thread
524
+ will take its place as the group's anchor. If only unsent drafts or no threads
525
+ remain, the box will return to the standalone inventory and its thread-group
526
+ name and folder will be cleared.
527
+
517
528
  Claude startup prompts, such as configuration, trust, or sign-in screens,
518
529
  open in Claude's native terminal as soon as it is available. The shared thread
519
530
  may still appear to be starting until Claude finishes establishing its
@@ -781,6 +792,13 @@ Destroying a machine removes the remote managed environment and clears local
781
792
  state for that machine. It does not just put the machine to sleep. The command
782
793
  requires confirmation unless you explicitly pass the force flag.
783
794
 
795
+ Plain destroy will refuse a devbox with attached threads, including archived
796
+ threads and runs grouped under an automation. Use
797
+ `dvb devboxes destroy --project <project> --target <devbox> --archive-threads --wait --yes`
798
+ to save their histories and destroy the devbox together.
799
+ If the devbox only has unsent drafts, discard those drafts in `dvb agents`
800
+ before destroying it.
801
+
784
802
  ## JSON Output
785
803
 
786
804
  Many CLI commands support `--json`. Use JSON mode when scripting so commands
@@ -224,21 +224,27 @@ Terminal and Browser tabs (while that pane is focused):
224
224
  With a thread selected, Cmd+W (Ctrl+Shift+W on Windows and Linux) closes its
225
225
  view and shows **No thread selected**. Reopen it from the sidebar or choose
226
226
  Back; its draft and any running work stay with the thread. A focused terminal
227
- keeps this shortcut for closing its current tab. To archive a thread,
228
- right-click it and choose **Archive**.
227
+ keeps this shortcut for closing its current tab, and Files with focus uses it
228
+ to close the selected file tab. To archive a thread, right-click it and choose
229
+ **Archive**.
229
230
 
230
231
  Files (while the Files pane has focus):
231
232
 
232
233
  - Go to line in the open file: **Ctrl+G** on every platform, matching VS
233
234
  Code. macOS uses Control here, not Cmd. A focused terminal keeps Ctrl+G for
234
235
  the shell.
236
+ - Previous / next tab: **Cmd+Option+Left** / **Cmd+Option+Right**
237
+ (Ctrl+Shift+Tab / Ctrl+Tab). These keys are fixed, not customizable, and
238
+ wrap at either end.
239
+ - Close the selected tab: **Cmd+W** (Ctrl+Shift+W). Files has no new-tab
240
+ shortcut; open files from the tree or file search.
235
241
 
236
242
  Help:
237
243
 
238
244
  - Show keyboard shortcuts: **Cmd+Shift+/** (Ctrl+Shift+/)
239
245
 
240
- This opens Settings → Keyboard shortcuts, which lists the fixed history keys
241
- and every customizable shortcut with its current binding. **Settings > Keyboard shortcuts** at the bottom of the sidebar opens the same dialog.
246
+ This opens Settings → Keyboard shortcuts, which lists the fixed history and
247
+ Files tab keys and every customizable shortcut with its current binding. **Settings > Keyboard shortcuts** at the bottom of the sidebar opens the same dialog.
242
248
  Controls that have a shortcut, such as the pane toggles in the titlebar, also
243
249
  show their binding in the hover
244
250
  tooltip. The dynamic thread-number shortcuts always follow sidebar order and
@@ -321,7 +327,9 @@ action instead.
321
327
 
322
328
  Three small CPU, memory, and disk meters show live utilization for the selected
323
329
  box. CPU and memory fill colors highlight elevated load. The disk meter
324
- turns yellow below 2 GiB free and red below 1 GiB free. Hover the meters for
330
+ turns yellow below 2 GiB free and red below 1 GiB free. Below 1 GiB free, a
331
+ **Low disk space** label also appears beside the meters, and their tooltip
332
+ warns that agents can't start once the disk fills up. Hover the meters for
325
333
  exact resource details, or click them to open an Activity Monitor-style view of
326
334
  processes on the box. Empty tracks remain visible while the selected
327
335
  box has no live metrics.
@@ -672,7 +680,9 @@ can't use it (Browser API calls return HTTP 403 `agent_browser_disabled`), and
672
680
  each box keeps its tabs and sign-ins. The
673
681
  Browser pane supports ordinary page interaction, file chooser
674
682
  prompts, downloads into the box, permission prompts, browser dialogs, and
675
- profile reset. **Restart browser** asks for confirmation, then opens one blank
683
+ profile reset. **Restart browser** (in the toolbar's **…** menu, with
684
+ **Reset browser profile**, **Copy selected text**, **Copy page URL**, **Open in
685
+ external browser**, and **Show downloads**) asks for confirmation, then opens one blank
676
686
  tab while preserving sign-ins and saved profile data. Check **Restore open
677
687
  tabs** in that confirmation to reload the current tabs instead; the choice
678
688
  starts unchecked each time. Machines awaiting the browser update retain the
@@ -681,8 +691,9 @@ choice. Profile reset is the separate destructive action.
681
691
  Browser can also pop out from the side pane into
682
692
  a near-full-window overlay and dock back into the workbench.
683
693
 
684
- In the desktop Browser toolbar, select **Show downloads**, then **Open** beside a
685
- completed file to open it in the file viewer. Files stay on the selected box;
694
+ In the desktop Browser, choose **Show downloads** from the **…** menu, then
695
+ **Open** beside a completed file to open it in the file viewer. A dot on the
696
+ **…** button marks downloads in progress. Files stay on the selected box;
686
697
  use Files to download a copy to your computer. When an automation tool chooses
687
698
  another download folder, Browser retains its own named copy without moving the
688
699
  tool's file. A large download can stay in progress while that copy finishes.
@@ -695,11 +706,28 @@ box's `~/Downloads` folder. Use **Open** to find the retained file, then delete
695
706
  it in Files when no longer needed; delete the other copy too if one remains in
696
707
  `~/Downloads`.
697
708
 
698
- The mobile app's Browser shares these tabs and profile. Opening it on a phone
709
+ The mobile app's Browser shares these tabs and profile, and everyone viewing a
710
+ box's Browser shares one page size. By default the page takes the size of the
711
+ Browser view the user opened or used most recently. Opening Browser on a phone
699
712
  resizes the shared browser to the phone's screen, and the pane keeps showing
700
713
  its last picture. Moving the pointer into the pane, or focusing it, resizes the
701
- browser back to the pane. See
702
- `mobile.md`.
714
+ browser back to the pane. See `mobile.md`.
715
+
716
+ The page size button after the address field opens a menu with **Match this
717
+ pane** and **Fixed at 1280 × 800**. A fixed size keeps every tab at that size
718
+ (1280 × 800 by default) whether or not anyone is watching. The pane scales the
719
+ page down to fit, with bars around it, and the button stays highlighted. While
720
+ the page is scaled down, the same menu offers **Scale to fit** (with the
721
+ percentage) and **Actual size (100%)**, which shows the page at 100% in that
722
+ pane with scrollbars for moving around it; the mouse wheel still scrolls the
723
+ page. Zoom is the user's own view and doesn't change the page size. **Match
724
+ this pane** returns the page to the pane's size. Agents can turn a fixed size
725
+ on or off and set other sizes from 100 × 100 up to 1920 × 1200, for example
726
+ when a site's phone layout gets in the way of a task or to test a page at a
727
+ phone's size. With Chrome window on, a size narrower than 500 pixels shows a
728
+ 500-pixel-wide page because Chrome's window can't be narrower. The mobile app
729
+ shows a fixed page scaled to fit the phone, and its **…** menu has the same
730
+ choice; see `mobile.md`.
703
731
 
704
732
  Browser streams the remote page as WebRTC video on desktop and mobile. It
705
733
  connects directly to the box when it can and otherwise through a relay, which
@@ -717,9 +745,9 @@ default and saved to the account, and it applies to the desktop and mobile
717
745
  Browser alike; the mobile app shows it under **Settings → Advanced**. Changing
718
746
  the setting restarts the box's browser the next
719
747
  time Browser connects (an open Browser reconnects right away) and reopens its
720
- tabs with sign-ins and profile data intact. The pane keeps **Review page
721
- elements**, downloads, pop-out, and a More menu with **Copy page URL**, **Open
722
- in external browser**, **Restart browser**, and **Reset browser profile**.
748
+ tabs with sign-ins and profile data intact. The pane keeps the page size
749
+ button, **Review page elements**, pop-out, and the **…** menu, without **Copy
750
+ selected text** since Chrome copies its own selection.
723
751
 
724
752
  In Chrome window, pages a site opens with `window.open`, such as sign-in
725
753
  pop-ups, open as tabs in the same window. The site can still talk to the page
@@ -7,15 +7,34 @@ Template box. When a devbox thread is selected, they inspect that devbox.
7
7
 
8
8
  ## Files Pane
9
9
 
10
- Open Files from the desktop titlebar. The pane has a file tree on the left and
11
- a preview pane on the right.
12
-
13
- While the desktop workbench remains open, Files remembers the last open file
14
- separately for each Template box or devbox. Threads on the same machine share
15
- that file, while switching to another machine restores the file last opened
16
- there. Closing the Files pane, opening a directory, or deleting the open file
17
- clears that machine's remembered file. Restarting or reloading the desktop
18
- workbench starts again from the file tree.
10
+ Open Files from the desktop titlebar. When Files is expanded, the file tree
11
+ sits beside the open file. When it is docked beside the thread, the pane shows
12
+ either the tree or the open file.
13
+
14
+ Each file opened in Files gets a tab in the pane header, and opening a file
15
+ that already has a tab selects that tab. Tabs belong to the Template box or
16
+ devbox: threads on the same box share them, and switching to another box shows
17
+ the tabs opened there. Tabs last while the desktop workbench stays open.
18
+ Hiding or closing the Files pane keeps them; reloading or restarting the
19
+ desktop app closes them and starts again from the file tree.
20
+
21
+ Click a tab to switch files. While Files has focus, **Cmd+Option+Left** and
22
+ **Cmd+Option+Right** (Ctrl+Shift+Tab and Ctrl+Tab on Windows and Linux) move
23
+ to the previous or next tab, wrapping at either end; these keys are fixed
24
+ rather than customizable. Close a tab with its X, a middle-click, or **Cmd+W**
25
+ (Ctrl+Shift+W) while Files has focus. Closing the selected tab selects the tab
26
+ to its right, or the one to its left when it was last; closing the last tab
27
+ shows the file tree. Right-click a tab for Close, Close other tabs, Close all
28
+ tabs, and Copy path. When two open files share a name, their tabs add the
29
+ parent folder name. Renaming or moving an open file updates its tab, and
30
+ deleting it closes the tab. Switching tabs reloads the file from the box;
31
+ while Files stays open, each file keeps its scroll position, cursor, and undo
32
+ history.
33
+
34
+ When Files is docked, the file tree button at the start of the tab row shows
35
+ the tree in place of the open file, and no tab appears selected while the tree
36
+ shows. Press the button again or click a tab to return to a file. When Files is
37
+ expanded, the tree stays beside the file and the tabs sit above the file.
19
38
 
20
39
  The file tree can open:
21
40
 
@@ -31,9 +50,9 @@ their name, so a PDF or image saved with the wrong extension still opens in the
31
50
  right preview. For images, click the preview to open a
32
51
  full-screen, zoomable view (scroll or use the toolbar to zoom, drag to pan); the
33
52
  full-screen Files window zooms the image in place instead. Clicking an image
34
- file link in a thread opens Files and also opens that full-screen image view.
35
- Files that cannot be previewed inline, including images, videos, and PDFs over
36
- 100 MB, open in a download-only view.
53
+ file link in a thread opens Files and also opens that full-screen image view,
54
+ without adding a tab. Files that cannot be previewed inline, including images,
55
+ videos, and PDFs over 100 MB, open in a download-only view.
37
56
 
38
57
  Supported text files can also be edited directly in Files. Changes auto-save
39
58
  after you stop typing and before file switches, pane close, or pop-out changes.
@@ -73,9 +73,16 @@ choose for each one:
73
73
 
74
74
  - **Manage**: save the value centrally and move the assignment into the managed
75
75
  section;
76
- - **Keep local**: leave the assignment in the file's local tail; or
76
+ - **Keep in file**: leave the assignment in the file's local tail; or
77
77
  - **Remove**: remove that recognized assignment when management starts.
78
78
 
79
+ If the file sets the same name more than once, every assignment except the last
80
+ starts as **Remove**, with a note saying the name is set again later. Tools
81
+ that read dotenv files use the last value, and once management starts the
82
+ file keeps a single managed copy of the name. Before saving, the editor checks
83
+ the names of every row it will manage and names the first one that is blank,
84
+ not a valid variable name, or used twice in the file.
85
+
79
86
  Comments, blank lines, shell expressions, multiline constructs, and anything
80
87
  else the importer does not recognize stay local. The file must still match the
81
88
  version that was reviewed when the import is applied. If it changed, boxes.dev
@@ -86,6 +93,22 @@ If the file does not exist, boxes.dev creates it. If it is too large or is not
86
93
  valid UTF-8, automatic import is skipped and the complete existing file is
87
94
  preserved below the new managed section.
88
95
 
96
+ A dotenv file that is only on the user's own computer can be brought in from
97
+ the file editor, for a new file or one already managed. **Add from a file…**
98
+ opens the computer's file picker, and a file dropped on the variable list does
99
+ the same. Pasting text that contains `NAME=value` lines into a variable's name
100
+ field also fills rows; text without such a line pastes normally. The desktop
101
+ app reads the file locally and fills the editor as if the values had been
102
+ typed: a name already in the editor takes the file's value, and other names
103
+ become new rows. Nothing is stored until the user saves. Lines are recognized
104
+ by the same single-line rules as the import above, a name set more than once
105
+ uses its last value, and the editor reports how many variables were added or
106
+ updated and lists skipped lines by line number, never by content. Files over
107
+ 2 MiB and files that are not UTF-8 text are refused. In the macOS file picker,
108
+ ⇧⌘. shows hidden files such as `.env`. In a Team Template, every new row from
109
+ a local file starts unclassified, and Save stays unavailable until the admin
110
+ chooses **Team value** or **Member value** for each.
111
+
89
112
  When a team admin adds a file to a Team Template, boxes.dev checks the retained
90
113
  source box for the latest saved release. Before the first release, it checks
91
114
  that admin's current Team Template editing session, and the editor says which of
@@ -241,8 +241,11 @@ of the form to move between questions. Tapping an option answers the question
241
241
  and moves to the next one; for a written answer, type it and tap **Continue**.
242
242
  The answers are sent from the last question (Claude first returns to any
243
243
  question still unanswered). Unfinished Codex answers stay in place when you
244
- scroll away and back. If Codex finishes its turn before
245
- you send an asynchronous answer, your edited answer returns to the composer.
244
+ scroll away and back. If Codex finishes its turn before you send an asynchronous
245
+ answer, your edited answer returns to the composer. Text sent from the reply box
246
+ while a question is waiting answers the question shown, like a written answer,
247
+ and options you already chose in a Codex form are sent with it. Attachments stay
248
+ in the reply box for your next message.
246
249
 
247
250
  A pending Codex question or form can appear before the phone connects to the
248
251
  agent. You can read it while connecting, but its response controls become
@@ -433,23 +436,33 @@ sites, and profile, and agents on the box use it too. If the box's browser
433
436
  isn't running yet, opening Browser starts it. The menu leaves out **Browser**
434
437
  while the project's Browser is turned off in Project settings.
435
438
 
436
- Opening Browser on a phone resizes that shared browser to the phone's page
437
- area, so sites use their narrow-screen layout. It is a size change only: sites
438
- still see a desktop browser, with desktop scrollbars and no touch events. The
439
- desktop pane and agent screenshots also get the phone size while it lasts.
439
+ By default, opening Browser on a phone resizes that shared browser to the
440
+ phone's page area, so sites use their narrow-screen layout. It is a size
441
+ change only: sites still see a desktop browser, with desktop scrollbars and no
442
+ touch events. The desktop pane and agent screenshots also get the phone size
443
+ while it lasts.
440
444
  With the default streaming setting, the desktop pane keeps showing its last
441
445
  picture. Moving the pointer into the desktop pane, or focusing it, resizes the
442
446
  browser back to the pane. On the phone, the first touch after that resizes it
443
447
  to the phone again and does nothing else.
444
448
 
449
+ The desktop app, the phone, or an agent can set a fixed page size instead.
450
+ Every tab then keeps that size (1280 × 800 unless an agent chose another), and
451
+ the phone shows the page scaled to fit its page area with gray bars around it.
452
+ Opening Browser or touching the page doesn't resize it. Taps on the bars do
453
+ nothing, but a drag that starts on them still scrolls the page. In the bottom
454
+ toolbar, **… → Fit page to screen** turns the fixed size off for everyone
455
+ viewing the box's Browser, and **… → Fixed page size** turns it back on (see
456
+ `desktop-workbench.md`).
457
+
445
458
  Tap to click and drag with one finger to scroll. Tapping a text field opens
446
459
  the keyboard; tapping elsewhere on the page closes it. While the keyboard is
447
460
  open, the page keeps its size and shifts up to keep the tapped field in view.
448
461
  The keyboard button in the bottom toolbar opens or closes the keyboard for
449
462
  fields that don't open it themselves. The address field opens a URL or domain
450
- in the current tab. The toolbar also has back, forward, reload, and a tab
451
- count that opens **Tabs**, where you can switch tabs, open a **New tab**, or
452
- **Close tab**.
463
+ in the current tab. The toolbar also has back, forward, reload, **…** for the
464
+ page size choice, and a tab count that opens **Tabs**, where you can switch
465
+ tabs, open a **New tab**, or **Close tab**.
453
466
 
454
467
  Touch and hold a text field to open the phone's **Copy**, **Paste**, and
455
468
  **Select all** menu. After **Select all**, choose **Copy** to copy the field's
@@ -306,7 +306,9 @@ start from the Template box's saved checkout.
306
306
 
307
307
  Inspect `origin` to identify the source Team Template and saved version, the
308
308
  captured `projectConfigurationInput`, and its `configurationSource` when
309
- recorded. These show what was copied when the project was created. Compare
309
+ recorded. These show what was copied when the project was created. Its MCP
310
+ connections list each server's `host` without the rest of the URL, because a
311
+ URL's path or query can hold a secret. Compare
310
312
  those inputs with `team-template settings get` to explain inherited settings;
311
313
  changing template defaults will not replace an existing project's copy. Agent
312
314
  Guidance is the exception for a project the Team Template manages
@@ -891,8 +893,11 @@ default Slack or Linear receiver.
891
893
  `--idempotency-key` to get the original run back. Errored automations and
892
894
  default Slack and Linear receivers fail with `run_not_available`; launch
893
895
  rejections fail with `run_rejected` and a `reasonCode`.
894
- - `delete` works only while the automation has no runs. Otherwise it fails
895
- with `automation_has_runs`; pause it instead.
896
+ - `delete` deletes the automation and its run history. Threads and devboxes
897
+ its runs started are kept, without the automation's devbox cleanup, and
898
+ move into the user's Devboxes list. Check with the user before deleting one
899
+ with many live devboxes. To stop runs and keep the history, pause it
900
+ instead.
896
901
 
897
902
  ### Read runs
898
903
 
@@ -1060,7 +1065,8 @@ The request values are `create-devboxes-and-threads`,
1060
1065
  `read-team-threads`, `control-created-threads`, `control-project-threads`,
1061
1066
  `control-user-threads`, `message-agents`, `message-teammates-agents`, `edit-template-box`,
1062
1067
  `edit-team-template`, `edit-project-settings`, `edit-personal-environment`,
1063
- `edit-automations`, `edit-tailscale-integration`, and `edit-google-cloud-integration`.
1068
+ `edit-automations`, `edit-tailscale-integration`, `edit-google-cloud-integration`,
1069
+ and `use-computer`.
1064
1070
  Add `--json` for a stable structured result.
1065
1071
 
1066
1072
  The command creates one request for the exact managed thread and source box,
@@ -1147,6 +1153,67 @@ The permission command never retries the blocked operation itself. After **Deny*
1147
1153
  or expiry, continue without the operation and do not ask again in the same
1148
1154
  task. Do not request title permission for optional housekeeping.
1149
1155
 
1156
+ ## Computer Access
1157
+
1158
+ Computer access lets an agent ask the boxes.dev desktop app on the user's Mac
1159
+ to run a command there or copy a file or folder from it to the agent's box.
1160
+ Use the `boxes-computer-access` skill for the `dvb-onbox computer` commands,
1161
+ request wording, waiting, output, and results. This section explains how the
1162
+ user controls it, for answering their questions.
1163
+
1164
+ It's in a gradual rollout to teams. When it isn't available for the user's
1165
+ team, the desktop app's Settings has no **Computer access** section and
1166
+ `dvb-onbox computer status` says computer access is not available for the
1167
+ account.
1168
+
1169
+ - **Turning it on.** The user opens **Settings → Computer access** in the
1170
+ desktop app on macOS, selects **Turn on…**, and confirms. It works on one
1171
+ computer at a time; turning it on on another Mac moves it there.
1172
+ - **Which boxes can ask.** **Computer access** in a devbox's or project's
1173
+ Agent permissions is **Off** unless the user chooses **Ask each time** or
1174
+ **Always allow**. Devboxes follow the project unless they have their own
1175
+ value. An agent can request the `use-computer` permission in its thread.
1176
+ Team admins choose **Allowed**, **Ask every time** (no Always allow or
1177
+ Allow for 3 hours), or **Off** under
1178
+ **Computer access** in the team's settings. Threads started by automations
1179
+ and the project coordinator can't use computer access.
1180
+ - **Approving.** While the user is in the desktop app, a request appears as a
1181
+ card in the top-right corner of its window, styled like a thread's
1182
+ permission card: the command or path, the agent's reason, **Deny**,
1183
+ **Allow** (this request only), and **Allow for 3 hours**. Allow for 3 hours runs the
1184
+ request and sets only the source devbox to run without asking for 3 hours;
1185
+ the dropdown shows it as **Allow all until** its end time. **Details** shows
1186
+ the thread, folder, timeout, and source devbox and project, with **Turn off
1187
+ for this devbox** and **Always allow this devbox…**. Nothing on the card
1188
+ changes the project's setting. When the user is in another app, they get a
1189
+ notification and a Dock bounce, and the card appears when they switch to
1190
+ boxes.dev. The thread also shows the waiting request with **Deny**.
1191
+ - **Always allow.** A project or devbox set to **Always allow** runs commands
1192
+ and copies without asking, including while the Mac is locked, after the
1193
+ user confirms it once on that computer. Settings lists them with
1194
+ **Remove**.
1195
+ - **Locked Mac and phone approval.** A request that needs approval while the
1196
+ Mac is locked returns `away`, unless the user paired a phone: in the mobile
1197
+ app, **Settings → Computer access → Phone approval**, then **Allow** in the
1198
+ Mac's window after checking the 4-digit code matches. Only the paired phone
1199
+ can approve, with Face ID, Touch ID, or the passcode. Pairing another phone
1200
+ replaces it, signing out on the phone ends it, and **Turn off phone
1201
+ approval** on the phone or **Turn off** in the desktop app's Settings stops
1202
+ it. Phone approval needs a recent mobile app build.
1203
+ - **Pause and Turn off.** **Pause** in desktop Settings stops requests, and
1204
+ agents get `paused` until the user selects **Resume**. **Turn off** also
1205
+ erases the computer's Always allow confirmations and phone pairing, and
1206
+ asks first when either is saved.
1207
+ - **Interrupted runs.** If the desktop app quits while a command runs, it
1208
+ stops the command, and the request ends as `failed` with a message that the
1209
+ command may have run only partly: as soon as the app starts again, or two
1210
+ minutes after the command's timeout if it doesn't.
1211
+ - **Copies.** A copy is saved on the box under `~/computer-files/` or at the
1212
+ requested path, up to 100 MB and 10,000 files. Keychains, browser profiles,
1213
+ and the desktop app's data can't be copied, and folders such as `~/.ssh`
1214
+ show a warning first. On a Template box, devboxes made from its next
1215
+ snapshot will have the copy too.
1216
+
1150
1217
  ## Current Thread Title
1151
1218
 
1152
1219
  A managed Codex or Claude agent can inspect the canonical boxes.dev title of
@@ -1322,7 +1389,8 @@ happens:
1322
1389
  - The agent runs `clear-request`.
1323
1390
 
1324
1391
  Requests from archived or deleted threads stop showing. A request carries no
1325
- text, so the agent should still say in its reply what the user needs to do.
1392
+ text, so the agent should say in its reply what the user needs to do in the
1393
+ Browser, without pointing the user to the dot.
1326
1394
  Both commands act on the managed thread that runs them, take no thread ID, and
1327
1395
  need no permission. With `--json`, they print
1328
1396
  `{"schemaVersion": 1, "ok": true, "operation": "request"}` or
@@ -1831,7 +1899,10 @@ of asking the child to summarize a shortened `threads read` preview. When
1831
1899
  there is no active turn, it returns `idle` with any available latest stop
1832
1900
  metadata as context, or `failed` if the child failed to start. That stop can belong to an earlier assignment, so compare
1833
1901
  its turn ID with the work you are checking. A completed wait includes that
1834
- same complete response as `output.text`; Ctrl+C stops only the local wait.
1902
+ same complete response as `output.text`. A timed-out wait includes the
1903
+ current `threads read` transcript, which ends with a notice when a running
1904
+ Codex turn keeps compacting without freeing much of its context window. Ctrl+C
1905
+ stops only the local wait.
1835
1906
  `threads events` emits durable lifecycle events with
1836
1907
  an opaque resume cursor on every JSONL row. With no turn, cursor, or
1837
1908
  `--from-start`, it follows only events created after the command starts. An
@@ -366,6 +366,10 @@ mobile Settings. On the web, selecting **Delete account…** first reveals the
366
366
  projects that will be deleted, with a descendant devbox count beside each one.
367
367
  The confirmation phrase is `DELETE`.
368
368
 
369
+ A team always keeps an admin. If the user is the team's only admin and other
370
+ people are on the team, they need to choose a teammate as the new admin before
371
+ deleting; boxes.dev makes that teammate an admin when the deletion starts.
372
+
369
373
  Account deletion deletes:
370
374
 
371
375
  - The user's boxes.dev account and authentication records.
@@ -380,6 +384,14 @@ Account deletion deletes:
380
384
  Team-owned Team Templates and other members' projects remain with the team when
381
385
  one member deletes their account.
382
386
 
387
+ Billing records such as invoices are kept. If nobody else is left on the team,
388
+ the team's plan ends immediately, with no final charge and no refund for the
389
+ rest of the billing period, and saved cards are removed. If teammates remain
390
+ and the user had a paid seat, the seat comes off the team's plan and the next
391
+ invoice reflects it; if it was the team's only paid seat, the plan ends instead
392
+ and the team's cards stay. Unused prepaid credits are not refunded
393
+ automatically.
394
+
383
395
  Account deletion is permanent and cannot be undone.
384
396
 
385
397
  Copies of data deleted from active systems may remain in routine backups held
@@ -340,6 +340,12 @@ To start a new teammate-owned run from an already linked Slack thread,
340
340
  explicitly name the teammate again: `@boxes.dev @Ananya <request>`. Later
341
341
  unqualified follow-ups in that Slack thread go to the newest run.
342
342
 
343
+ A follow-up sent while the agent is working joins its current turn as a steer,
344
+ and an idle agent starts a new turn. If the project owner chose **Queue** in
345
+ **Account → Agent replies**, a follow-up will wait for the current turn to
346
+ finish instead. Slash commands always wait, and so do follow-ups to Claude on a
347
+ devbox whose software doesn't support steering yet.
348
+
343
349
  Use Slack controls in the linked thread:
344
350
 
345
351
  - `@boxes.dev help` or `@boxes.dev !help` explains how to follow up, stop, and
@@ -376,7 +382,7 @@ Limits and rules:
376
382
  verified ordinary internal members of the connected Slack workspace are
377
383
  allowed even if the uploader cannot run the automation;
378
384
  - files from external Slack users, including Slack Connect users and guests,
379
- require the requester's approval for each file;
385
+ require the requester's approval;
380
386
  - files from bots/apps, deleted users, and unverifiable uploaders are omitted;
381
387
  - deleted, restricted, unsupported, oversized, or technically failed files are
382
388
  omitted.
@@ -385,13 +391,19 @@ An omitted file does not stop an otherwise valid request or linked follow-up.
385
391
  boxes.dev continues with every file that imported successfully and tells the
386
392
  agent which intended input was not delivered. It also explains the omission
387
393
  in Slack when attachment warnings are enabled.
388
- For an external user's file, boxes.dev will show **Upload file** and **Skip**
389
- in a private Slack message visible only to the person who triggered the
390
- request. Only upload files you trust: they may contain malware or malicious
391
- instructions. The agent will start with the available text and files;
392
- **Upload file** will send that file to the same agent thread as a follow-up,
393
- and **Skip** will leave it out. Approval applies only to that file and request.
394
- These private prompts also appear when public attachment warnings are off.
394
+ When a request includes files from external users, boxes.dev will show one
395
+ private Slack message, visible only to the person who triggered the request,
396
+ with **Upload file** (or **Upload files**) and **Skip**. One choice applies to
397
+ all of that request's external files. Only upload files you trust: they may
398
+ contain malware or malicious instructions. The message changes to show the
399
+ choice as soon as it is clicked.
400
+
401
+ A new request will wait up to 10 seconds for the choice before the agent
402
+ starts. Files approved in that time will be in the agent's first message.
403
+ Files approved later will be sent to the agent together, joining its current
404
+ turn if it is still working. **Skip** will leave the files out. Approval
405
+ applies only to that request. These private prompts also appear when public
406
+ attachment warnings are off.
395
407
 
396
408
  Slack's private prompts are temporary and may disappear after a reload or
397
409
  not arrive while you are inactive. Approval cannot grant access to files