@boxes-dev/dvb-runtime 1.0.1099 → 1.0.1100
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/bin/dvb.mjs +113 -64
- package/dist/bin/dvbd.mjs +6 -6
- package/dist/postgres-tools/SHA256SUMS +32 -8
- package/dist/postgres-tools/linux-arm64-el8/bin/pg_dump +0 -0
- package/dist/postgres-tools/linux-arm64-el8/bin/pg_restore +0 -0
- package/dist/postgres-tools/linux-arm64-el8/lib/libpq.so.5 +0 -0
- package/dist/postgres-tools/linux-arm64-el8/notices/PostgreSQL-COPYRIGHT.txt +23 -0
- package/dist/postgres-tools/linux-arm64-el9/bin/pg_dump +0 -0
- package/dist/postgres-tools/linux-arm64-el9/bin/pg_restore +0 -0
- package/dist/postgres-tools/linux-arm64-el9/lib/libpq.so.5 +0 -0
- package/dist/postgres-tools/linux-arm64-el9/notices/PostgreSQL-COPYRIGHT.txt +23 -0
- package/dist/postgres-tools/linux-arm64-ubuntu22.04/bin/pg_dump +0 -0
- package/dist/postgres-tools/linux-arm64-ubuntu22.04/bin/pg_restore +0 -0
- package/dist/postgres-tools/linux-arm64-ubuntu22.04/lib/libpq.so.5 +0 -0
- package/dist/postgres-tools/linux-x64-el8/bin/pg_dump +0 -0
- package/dist/postgres-tools/linux-x64-el8/bin/pg_restore +0 -0
- package/dist/postgres-tools/linux-x64-el8/lib/libpq.so.5 +0 -0
- package/dist/postgres-tools/linux-x64-el8/notices/PostgreSQL-COPYRIGHT.txt +23 -0
- package/dist/postgres-tools/linux-x64-el9/bin/pg_dump +0 -0
- package/dist/postgres-tools/linux-x64-el9/bin/pg_restore +0 -0
- package/dist/postgres-tools/linux-x64-el9/lib/libpq.so.5 +0 -0
- package/dist/postgres-tools/linux-x64-el9/notices/PostgreSQL-COPYRIGHT.txt +23 -0
- package/dist/postgres-tools/linux-x64-ubuntu22.04/bin/pg_dump +0 -0
- package/dist/postgres-tools/linux-x64-ubuntu22.04/bin/pg_restore +0 -0
- package/dist/postgres-tools/linux-x64-ubuntu22.04/lib/libpq.so.5 +0 -0
- package/dist/postgres-tools/linux-x64-ubuntu22.04/notices/PostgreSQL-and-Debian-copyright.txt +270 -0
- package/dist/postgres-tools/linux-x64-ubuntu24.04/notices/PostgreSQL-and-Debian-copyright.txt +270 -0
- package/dist/postgres-tools/release.json +306 -18
- package/dist/product-docs/references/billing-and-limits.md +3 -2
- package/dist/product-docs/references/convex.md +92 -0
- package/dist/product-docs/references/desktop-workbench.md +38 -23
- package/dist/product-docs/references/fork-workflows.md +6 -6
- package/dist/product-docs/references/getting-started.md +4 -4
- package/dist/product-docs/references/index.md +2 -0
- package/dist/product-docs/references/onbox-agent-tools.md +38 -15
- package/dist/product-docs/references/ports-terminal-and-runtime.md +4 -0
- package/dist/product-docs/references/project-setup.md +6 -3
- package/dist/product-docs/references/security-and-data.md +13 -3
- package/dist/product-docs/references/slack.md +42 -4
- package/dist/product-docs/references/team-template.md +4 -1
- package/dist/product-docs/references/threads-and-agents.md +7 -2
- package/package.json +2 -2
- /package/dist/postgres-tools/{linux-arm64 → linux-arm64-ubuntu22.04}/notices/PostgreSQL-and-Debian-copyright.txt +0 -0
- /package/dist/postgres-tools/{linux-arm64 → linux-arm64-ubuntu24.04}/bin/pg_dump +0 -0
- /package/dist/postgres-tools/{linux-arm64 → linux-arm64-ubuntu24.04}/bin/pg_restore +0 -0
- /package/dist/postgres-tools/{linux-arm64 → linux-arm64-ubuntu24.04}/lib/libpq.so.5 +0 -0
- /package/dist/postgres-tools/{linux-x64 → linux-arm64-ubuntu24.04}/notices/PostgreSQL-and-Debian-copyright.txt +0 -0
- /package/dist/postgres-tools/{linux-x64 → linux-x64-ubuntu24.04}/bin/pg_dump +0 -0
- /package/dist/postgres-tools/{linux-x64 → linux-x64-ubuntu24.04}/bin/pg_restore +0 -0
- /package/dist/postgres-tools/{linux-x64 → linux-x64-ubuntu24.04}/lib/libpq.so.5 +0 -0
|
@@ -199,9 +199,8 @@ Help:
|
|
|
199
199
|
|
|
200
200
|
- Show keyboard shortcuts: **Cmd+Shift+/** (Ctrl+Shift+/)
|
|
201
201
|
|
|
202
|
-
This opens
|
|
203
|
-
and every customizable shortcut with its current binding. **
|
|
204
|
-
Keyboard shortcuts** at the bottom of the sidebar opens the same dialog.
|
|
202
|
+
This opens Settings → Keyboard shortcuts, which lists the fixed history keys
|
|
203
|
+
and every customizable shortcut with its current binding. **Settings > Keyboard shortcuts** at the bottom of the sidebar opens the same dialog.
|
|
205
204
|
Controls that have a shortcut, such as the pane toggles in the titlebar, also
|
|
206
205
|
show their binding in the hover
|
|
207
206
|
tooltip. The dynamic thread-number shortcuts always follow sidebar order and
|
|
@@ -210,7 +209,7 @@ are not customizable.
|
|
|
210
209
|
### Customizing Shortcuts
|
|
211
210
|
|
|
212
211
|
Workbench shortcuts with a Rebind control can be changed. Open the dialog
|
|
213
|
-
(**Cmd+Shift+/**, **
|
|
212
|
+
(**Cmd+Shift+/**, **Settings > Keyboard shortcuts**, or **Customize** in
|
|
214
213
|
the search modal footer), then click Rebind on a shortcut and press the new
|
|
215
214
|
combo.
|
|
216
215
|
Bindings must include Cmd or Ctrl, cannot use Alt, and cannot collide with
|
|
@@ -258,7 +257,7 @@ machine you last used. Return to one of your own threads connected to a box or,
|
|
|
258
257
|
available, the Template box when you want box controls and Files,
|
|
259
258
|
Git/Review, Terminal, Browser, or Ports.
|
|
260
259
|
|
|
261
|
-
The app menu also includes **Project settings**, **
|
|
260
|
+
The app menu also includes **Project settings**, **Settings...**,
|
|
262
261
|
**Configure agents...**, **Sign Out**, update actions, and **Show Workbench**.
|
|
263
262
|
Configure agents can save multiple Codex and Claude accounts or API keys and
|
|
264
263
|
choose one active credential for each agent across all devboxes. The File menu
|
|
@@ -294,20 +293,36 @@ startup script, shared agent guidance, automatic waking of sleeping machines,
|
|
|
294
293
|
other new-devbox defaults, and the Claude and Codex settings kept on every box
|
|
295
294
|
(see `threads-and-agents.md`). Opening it does not select or wake a machine.
|
|
296
295
|
|
|
297
|
-
To change the automatic idle-sleep timeout, open **
|
|
298
|
-
→ Sleep timeout** and choose 5, 15, 30, or 60 minutes, or **Team default**.
|
|
299
|
-
Team admins can set the default in **Team
|
|
296
|
+
To change the automatic idle-sleep timeout, open **Settings
|
|
297
|
+
→ General → Sleep timeout** and choose 5, 15, 30, or 60 minutes, or **Team default**.
|
|
298
|
+
Team admins can set the default in **Settings → Team and members → Sleep timeout**; without
|
|
300
299
|
a custom setting it is five minutes. Your choice overrides the team default
|
|
301
300
|
for your Template boxes and devboxes, including managed projects.
|
|
302
301
|
Changes apply to existing and new boxes. A running box may keep its current
|
|
303
302
|
sleep deadline until its next activity; saving will not wake a sleeping box.
|
|
304
303
|
Longer timeouts use more box-hours; active agents can still keep boxes awake.
|
|
305
304
|
|
|
306
|
-
Open the account menu
|
|
307
|
-
|
|
308
|
-
|
|
309
|
-
|
|
310
|
-
|
|
305
|
+
Open **Settings…** from the account menu, or press Cmd+, (Ctrl+,), for one
|
|
306
|
+
pane with a category sidebar. General, Notifications, Agents, Connections,
|
|
307
|
+
Browser, Terminal, Keyboard shortcuts, and Account contain personal and device
|
|
308
|
+
preferences. Labels distinguish **On this computer** and **Across devices**.
|
|
309
|
+
Team admins also see Team and members and Integrations; Billing & usage
|
|
310
|
+
retains its existing permissions. Opening Settings preserves the current
|
|
311
|
+
thread, draft, and terminal. Compound forms keep their own Save actions, and
|
|
312
|
+
leaving an edited form asks before discarding its changes.
|
|
313
|
+
|
|
314
|
+
**Related settings** links to the selected project's existing Project settings
|
|
315
|
+
and its associated Team Template, including an independent project's recorded
|
|
316
|
+
source. Without a project or source template, the links open the project list
|
|
317
|
+
or template collection. Back returns to the originating section. Opening a
|
|
318
|
+
link does not start an editing machine. At narrow widths, a section selector
|
|
319
|
+
replaces the sidebar and both links remain visible.
|
|
320
|
+
|
|
321
|
+
An older desktop client shows **Open desktop preferences** for settings whose
|
|
322
|
+
editor is unavailable in its bridge. Its native settings window remains
|
|
323
|
+
usable until the app is updated, and remains available while signed out.
|
|
324
|
+
The account menu retains account switching, notification pause, updates, and
|
|
325
|
+
log out; usage and Help stay beside it.
|
|
311
326
|
|
|
312
327
|
## Template box
|
|
313
328
|
|
|
@@ -446,7 +461,7 @@ finished agents leave it after your next message. The inspector is read-only.
|
|
|
446
461
|
Older conversations may not have a subagent list.
|
|
447
462
|
|
|
448
463
|
To distinguish Claude and Codex threads at a glance, turn on **Show agent
|
|
449
|
-
logos** in **
|
|
464
|
+
logos** in **Settings > General**. The logos appear
|
|
450
465
|
at the right edge of thread rows and are off by default.
|
|
451
466
|
|
|
452
467
|
Thread rows can show unread or attention state. When a thread completes, fails,
|
|
@@ -469,8 +484,7 @@ finished turns don't notify you or mark it unread; requests for input still
|
|
|
469
484
|
do. **Mark unread** on a muted thread lasts until you open it or its next turn
|
|
470
485
|
finishes. **Unmute notifications** turns them back on.
|
|
471
486
|
|
|
472
|
-
Desktop completion notifications are controlled in **
|
|
473
|
-
Notifications**:
|
|
487
|
+
Desktop completion notifications are controlled in **Settings > Notifications**:
|
|
474
488
|
|
|
475
489
|
- **Never** turns banners and sounds off for completed replies, failures, and
|
|
476
490
|
requests for input.
|
|
@@ -483,7 +497,7 @@ Notifications**:
|
|
|
483
497
|
**Play notification sounds** is on by default. Turn it off to keep banners
|
|
484
498
|
without sound. Update the desktop app if this control is missing. Agent replies
|
|
485
499
|
do not ring the terminal bell or bounce the Dock icon; terminal bells have
|
|
486
|
-
their own settings under **
|
|
500
|
+
their own settings under **Settings > Terminal > Bell**.
|
|
487
501
|
|
|
488
502
|
Eligible controlled Codex completion notifications include the final-response
|
|
489
503
|
preview when it is available and a generic completion preview during recovery;
|
|
@@ -491,7 +505,7 @@ failures include a status preview. Selecting a notification opens its project
|
|
|
491
505
|
and thread. Delivery also depends on the operating system's notification
|
|
492
506
|
settings for boxes.dev.
|
|
493
507
|
|
|
494
|
-
**
|
|
508
|
+
**Settings → Notifications → Quiet hours** sets a daily interval shared with
|
|
495
509
|
mobile and your other computers. Each device uses its own timezone. Use the
|
|
496
510
|
account menu's **Pause notifications for 1 hour** to silence agent alerts on
|
|
497
511
|
every device for this account until the same end time; **Resume notifications**
|
|
@@ -618,7 +632,7 @@ If the stream can't connect after a second attempt, the pane shows
|
|
|
618
632
|
WebRTC streaming shows that it needs an update, and a page whose video stops
|
|
619
633
|
shows **Browser stopped updating** with **Try again**.
|
|
620
634
|
|
|
621
|
-
**
|
|
635
|
+
**Settings → Browser → Chrome window** shows the box's whole Chrome window in
|
|
622
636
|
Browser, with Chrome's own tabs, address bar, menus, and page dialogs in place
|
|
623
637
|
of the pane's address bar, navigation buttons, and tab strip. It is off by
|
|
624
638
|
default and saved to the account, and it applies to the desktop and mobile
|
|
@@ -655,7 +669,7 @@ does not restart a disconnected browser.
|
|
|
655
669
|
|
|
656
670
|
The box has no security key or platform authenticator of its own. In the
|
|
657
671
|
desktop app, Browser-pane passkey forwarding is off by default and can be
|
|
658
|
-
enabled under **
|
|
672
|
+
enabled under **Settings > Browser > Allow sites to use a passkey
|
|
659
673
|
on this computer**. The first eligible passkey request can also ask whether to
|
|
660
674
|
enable forwarding and warns that a compromised sandbox could spoof the
|
|
661
675
|
requesting site shown in later passkey confirmation windows. Once enabled,
|
|
@@ -669,7 +683,7 @@ Coding agents cannot use passkeys or cause the confirmation window to open.
|
|
|
669
683
|
Passkey forwarding accepts only recent user input from the Browser pane. Ask
|
|
670
684
|
the user to complete the passkey flow themselves; the resulting Browser profile
|
|
671
685
|
session remains shared with the agent afterwards. If the user disabled passkey
|
|
672
|
-
forwarding, they can re-enable it under **
|
|
686
|
+
forwarding, they can re-enable it under **Settings > Browser**.
|
|
673
687
|
|
|
674
688
|
Users can also review specific page elements from the Browser. Select the
|
|
675
689
|
review control to enter a focused **Reviewing** mode, hover to preview a target,
|
|
@@ -714,13 +728,14 @@ terminal notification settings.
|
|
|
714
728
|
|
|
715
729
|
## Team Settings
|
|
716
730
|
|
|
717
|
-
Team admins can open **
|
|
731
|
+
Team admins can open **Settings → Team and members** from the account menu to review current
|
|
718
732
|
members and change another member between **Admin** and **Member**. An admin's
|
|
719
733
|
own role is read-only there, so another team admin must change it. Invitations
|
|
720
734
|
remain for new accounts; if an email is already on the team, manage that person
|
|
721
735
|
in the **Members** section instead.
|
|
722
736
|
|
|
723
|
-
|
|
737
|
+
**Settings → Integrations** shows **Static egress IP**, Tailscale, Slack,
|
|
738
|
+
and Linear. This optional feature gives the
|
|
724
739
|
team a stable public IPv4 to allowlist at an external database or service. It
|
|
725
740
|
is visible but off by default; use **Talk to us** to request enablement. Once
|
|
726
741
|
enabled, all team members can copy the current static IP and read the configured
|
|
@@ -415,12 +415,12 @@ warns about uncommitted changes, changed files, and local-only commits when that
|
|
|
415
415
|
information is available. It also names the pull requests whose automatic
|
|
416
416
|
follow-ups the devbox's threads handle. Destroying the devbox stops those
|
|
417
417
|
follow-ups, and the pull request shows them as paused until a restored or
|
|
418
|
-
other thread turns them on again.
|
|
419
|
-
|
|
420
|
-
|
|
421
|
-
|
|
422
|
-
|
|
423
|
-
|
|
418
|
+
other thread turns them on again. As soon as the destroy starts, the devbox's
|
|
419
|
+
threads move to **Devboxes** → **Archived threads** on desktop and to
|
|
420
|
+
**Archived threads** at the end of the project on mobile, on every device,
|
|
421
|
+
while the cold-storage archive finishes in the background. If archiving fails,
|
|
422
|
+
the threads return to the active list untouched. Once the devbox is gone, its
|
|
423
|
+
threads are grouped there under the destroyed devbox's name.
|
|
424
424
|
Archived automation runs stay in their automation's **Archived** group on
|
|
425
425
|
desktop, with their threads directly beneath the run's devbox. `dvb agents`
|
|
426
426
|
shows the threads in its archived section throughout. Preserving the
|
|
@@ -111,16 +111,16 @@ Use devbox threads for normal coding tasks.
|
|
|
111
111
|
## Agent Auth After Setup
|
|
112
112
|
|
|
113
113
|
Setup asks you to connect at least one coding agent. You can connect or repair
|
|
114
|
-
agent auth later from
|
|
115
|
-
|
|
114
|
+
agent auth later from **Settings → Agents** in the desktop account menu.
|
|
115
|
+
The macOS **Configure agents...** command opens the same section. The mobile app has the same controls under
|
|
116
116
|
**Settings → Agent accounts**.
|
|
117
117
|
|
|
118
118
|
Codex can be connected with ChatGPT login or an API key. Claude Code can be
|
|
119
|
-
connected with Claude login or an API key.
|
|
119
|
+
connected with Claude login or an API key. Settings → Agents can keep multiple
|
|
120
120
|
accounts or API keys for each agent; choose the active credential with its
|
|
121
121
|
radio control. That choice is global across your devboxes, and Codex and Claude
|
|
122
122
|
can use different active accounts. If a thread cannot start because an agent is
|
|
123
|
-
not authenticated, open
|
|
123
|
+
not authenticated, open Settings → Agents, reconnect or choose another saved
|
|
124
124
|
credential, and then start or retry the thread.
|
|
125
125
|
|
|
126
126
|
## First Useful Task
|
|
@@ -111,6 +111,8 @@ Use this terminology consistently:
|
|
|
111
111
|
- `vercel.md`: connecting Vercel once for the Vercel CLI on every box, the
|
|
112
112
|
managed login file, `vercel login` and `vercel logout` on a box, SAML team
|
|
113
113
|
sign-in, reconnecting, and disconnecting.
|
|
114
|
+
- `convex.md`: connecting a Convex team to this project's boxes, expiring native
|
|
115
|
+
CLI credentials, existing personal logins, renewal, and removing access.
|
|
114
116
|
- `tailscale.md`: team-managed tailnet setup, Tailscale-policy-based project
|
|
115
117
|
eligibility, tagged ephemeral project machines, stock CLI behavior, ordinary
|
|
116
118
|
snapshot identity rotation, native cleanup, incident removal, and version-one
|
|
@@ -1326,10 +1326,10 @@ dvb-onbox threads read \
|
|
|
1326
1326
|
```
|
|
1327
1327
|
|
|
1328
1328
|
This returns a bounded preview of the durable boxes.dev transcript, thread
|
|
1329
|
-
status, and older-page cursor. Long messages are marked
|
|
1330
|
-
briefly lag the live runtime. Pending Codex and Claude
|
|
1331
|
-
runtime state and do not appear as transcript messages
|
|
1332
|
-
accepts them as turns.
|
|
1329
|
+
status, latest stop metadata, and older-page cursor. Long messages are marked
|
|
1330
|
+
as shortened. It can briefly lag the live runtime. Pending Codex and Claude
|
|
1331
|
+
queue entries remain runtime state and do not appear as transcript messages
|
|
1332
|
+
until the provider accepts them as turns.
|
|
1333
1333
|
|
|
1334
1334
|
List and observe that same source-scoped child pool without waking a child
|
|
1335
1335
|
devbox:
|
|
@@ -1355,12 +1355,22 @@ dvb-onbox threads events <delegated-thread-id> \
|
|
|
1355
1355
|
shows other project threads, including children created by a different source
|
|
1356
1356
|
box. To find other threads in the project, use `threads list --scope project`
|
|
1357
1357
|
from [Read Other Threads](#read-other-threads), which needs only **Read other
|
|
1358
|
-
threads**.
|
|
1358
|
+
threads**. Delegated list and read results include `lastStopReason`,
|
|
1359
|
+
`lastStopAt` (Unix milliseconds), and `lastStopTurnId`. These describe the
|
|
1360
|
+
latest lifecycle event if it is a completion, interruption, or failure;
|
|
1361
|
+
otherwise they are null. A later event can replace or clear them. `idle`
|
|
1362
|
+
describes activity, not successful completion. Muting does not hide this
|
|
1363
|
+
metadata.
|
|
1364
|
+
|
|
1365
|
+
`threads result` returns the complete stored final response for one
|
|
1359
1366
|
exact terminal turn and automatically assembles its transport pages. Use it instead
|
|
1360
1367
|
of asking the child to summarize a shortened `threads read` preview. When
|
|
1361
|
-
`threads wait` omits `--turn`, it snapshots the current active turn once.
|
|
1362
|
-
|
|
1363
|
-
|
|
1368
|
+
`threads wait` omits `--turn`, it snapshots the current active turn once. If
|
|
1369
|
+
there is no active turn, it returns `idle` with any available latest stop
|
|
1370
|
+
metadata as context. That stop can belong to an earlier assignment, so compare
|
|
1371
|
+
its turn ID with the work you are checking. A completed wait includes that
|
|
1372
|
+
same complete response as `output.text`; Ctrl+C stops only the local wait.
|
|
1373
|
+
`threads events` emits durable lifecycle events with
|
|
1364
1374
|
an opaque resume cursor on every JSONL row. With no turn, cursor, or
|
|
1365
1375
|
`--from-start`, it follows only events created after the command starts. An
|
|
1366
1376
|
exact-turn stream ends after needs-input or a terminal event.
|
|
@@ -1371,8 +1381,15 @@ deleted, and controls return `thread_not_found`. Retrying its original start wit
|
|
|
1371
1381
|
reports `child_thread_deleted` and keeps the original child ID; it does not
|
|
1372
1382
|
create another thread or recover the deleted transcript.
|
|
1373
1383
|
|
|
1374
|
-
|
|
1375
|
-
`threads list`, directly with `result`, `wait`, and `events`.
|
|
1384
|
+
Save a message's `turnId` from `threads read`, or an active turn ID from
|
|
1385
|
+
`threads list`, and use it directly with `result`, `wait`, and `events`. If the
|
|
1386
|
+
turn stopped before the first check, use `lastStopTurnId` to inspect its result.
|
|
1387
|
+
If that ID is null, find the assignment in `threads read` and use its saved
|
|
1388
|
+
message's `turnId`.
|
|
1389
|
+
Check `data.status` and the exact result before considering the assignment
|
|
1390
|
+
complete or sending a continuation; `ok: true` only means the lookup succeeded.
|
|
1391
|
+
Keep each assignment's turn ID even after a retry, because a successful later
|
|
1392
|
+
turn can replace the latest stop metadata. These observations
|
|
1376
1393
|
also accept the transcript turn keys returned by older versions. For `steer`
|
|
1377
1394
|
and `interrupt`, use the child's current `activeTurnId`.
|
|
1378
1395
|
|
|
@@ -1681,16 +1698,22 @@ shared. If any file cannot be transferred, the message will not be delivered.
|
|
|
1681
1698
|
Attachments cannot be sent to a teammate's thread; send a link they can open
|
|
1682
1699
|
instead.
|
|
1683
1700
|
|
|
1684
|
-
Keys reuse the same receipt on the same source
|
|
1685
|
-
invocations. After a retryable failure
|
|
1686
|
-
|
|
1687
|
-
|
|
1688
|
-
|
|
1701
|
+
Keys reuse the same receipt on the same source devbox, including across CLI
|
|
1702
|
+
invocations. After a retryable failure, repeat the command with the same key
|
|
1703
|
+
and identical arguments. Keep only one call outstanding for each key. A
|
|
1704
|
+
retryable failure does not by itself prove that an earlier or overlapping call
|
|
1705
|
+
with that key never delivered the message. Successful sends, permanent
|
|
1706
|
+
failures, and uncertain delivery outcomes keep their recorded result;
|
|
1707
|
+
repeating the command does not send them again.
|
|
1689
1708
|
Changing the recipient, message, attachments, or idle-only policy under that
|
|
1690
1709
|
key fails with `idempotency_key_reused`. Use a new key for each distinct message.
|
|
1691
1710
|
If delivery was skipped because the recipient was busy, use a new key if you
|
|
1692
1711
|
later decide to send it again.
|
|
1693
1712
|
|
|
1713
|
+
If the error reports that a devbox is out of disk space, free space on the
|
|
1714
|
+
named source or recipient devbox before retrying. Waiting alone will not free
|
|
1715
|
+
space. Reuse the original key and arguments after cleanup.
|
|
1716
|
+
|
|
1694
1717
|
`credits_depleted` means billing blocked the recipient's devbox before the
|
|
1695
1718
|
message was delivered. If you're a team admin, add credits in **Billing**;
|
|
1696
1719
|
otherwise, ask a team admin to add them. Then send the message again with a
|
|
@@ -31,6 +31,10 @@ that protection sooner. When the limit expires, normal idle sleep can resume;
|
|
|
31
31
|
the limit does not terminate the command. You can still sleep the machine
|
|
32
32
|
yourself.
|
|
33
33
|
|
|
34
|
+
Claude's background shell commands in the chat view have a separate execution
|
|
35
|
+
limit: 30 minutes by default, up to two hours. When that limit expires, Claude
|
|
36
|
+
stops the command and receives a notification.
|
|
37
|
+
|
|
34
38
|
A boxes.dev update can restart Claude, which stops its running background
|
|
35
39
|
commands. boxes.dev will then send the agent a message in the thread that lists
|
|
36
40
|
the stopped commands, so it can check their work and restart any it still
|
|
@@ -832,9 +832,12 @@ to the recommended defaults.
|
|
|
832
832
|
Packaged desktop and CLI setup include `pg_dump` for approved Postgres database
|
|
833
833
|
copies. Setup continues to prefer a usable `pg_dump` already on `PATH`, then
|
|
834
834
|
uses the included client when the host command is missing or is older than the
|
|
835
|
-
source server.
|
|
836
|
-
|
|
837
|
-
|
|
835
|
+
source server. On Linux, the included client runs on Ubuntu 22.04 and newer,
|
|
836
|
+
Debian 12 and newer, Fedora, Arch, openSUSE Tumbleweed, and RHEL 8 and 9 and
|
|
837
|
+
their rebuilds such as Rocky Linux and AlmaLinux. On other distributions it may
|
|
838
|
+
not start, and setup then asks for `pg_dump` on `PATH`. If the included payload
|
|
839
|
+
is unavailable, or the Postgres server is newer than the included client, setup
|
|
840
|
+
explains how to update or reinstall boxes.dev or use a compatible host client. The user can also skip that database
|
|
838
841
|
if its local data is not essential. MySQL copies still require `mysqldump` on
|
|
839
842
|
`PATH`. If a MySQL dump fails, setup explains how to use a client from the same
|
|
840
843
|
MySQL or MariaDB family and major or LTS release as the local server. The user
|
|
@@ -127,9 +127,12 @@ Slack, Linear, and GitHub integrations are authorized through their own OAuth
|
|
|
127
127
|
flows. Their tokens are stored encrypted by boxes.dev and used to perform the
|
|
128
128
|
integration actions the user or team enabled.
|
|
129
129
|
|
|
130
|
-
Disconnecting Slack stops
|
|
131
|
-
|
|
132
|
-
|
|
130
|
+
Disconnecting Slack stops Slack triggers, automation posts, and agent access to
|
|
131
|
+
Slack for the team. Data stored for the Slack connection is deleted within
|
|
132
|
+
14 business days, as it is when the app is uninstalled from Slack. The team's
|
|
133
|
+
boxes.dev threads and saved automation settings remain. See the
|
|
134
|
+
[privacy policy](https://boxes.dev/privacy#slack-retention) for retention details and how
|
|
135
|
+
to request deletion.
|
|
133
136
|
|
|
134
137
|
Disconnecting Linear stops future Linear assignment triggers for the team.
|
|
135
138
|
Existing boxes.dev threads remain.
|
|
@@ -378,6 +381,13 @@ one member deletes their account.
|
|
|
378
381
|
|
|
379
382
|
Account deletion is permanent and cannot be undone.
|
|
380
383
|
|
|
384
|
+
Copies of data deleted from active systems may remain in routine backups held
|
|
385
|
+
by boxes.dev or its service providers until normal backup rotation removes
|
|
386
|
+
them, unless the law requires longer retention. Retained copies remain
|
|
387
|
+
protected and may be used only for recovery, security, or legal compliance.
|
|
388
|
+
See `https://boxes.dev/delete-account` and `https://boxes.dev/privacy` for the
|
|
389
|
+
deletion and retention policies.
|
|
390
|
+
|
|
381
391
|
If a user cannot access their account, they can email hi@boxes.dev from the
|
|
382
392
|
email address on the account with the subject "Delete my boxes.dev account."
|
|
383
393
|
|
|
@@ -31,6 +31,21 @@ the **Account** step of first-run desktop setup when their team has no Slack
|
|
|
31
31
|
workspace yet. Slack opens an authorization screen; choose the workspace and
|
|
32
32
|
allow the app.
|
|
33
33
|
|
|
34
|
+
An install can also start in Slack. **Add to Slack** on `boxes.dev/slack`
|
|
35
|
+
opens Slack's authorization screen without a boxes.dev sign-in. After the
|
|
36
|
+
workspace approves the app, a boxes.dev page asks the person to sign in or
|
|
37
|
+
create an account, and a team admin chooses **Connect** to attach the
|
|
38
|
+
workspace to their team. They need to finish in the same browser within an
|
|
39
|
+
hour of approving the app in Slack. The success page lists the next steps,
|
|
40
|
+
including getting the desktop app and setting up a project for someone new to
|
|
41
|
+
boxes.dev.
|
|
42
|
+
|
|
43
|
+
When a new connection finishes either way, the app DMs the Slack user who
|
|
44
|
+
approved it with getting-started steps and links to the Slack help article and
|
|
45
|
+
support. A reinstall while the workspace is still connected, for example to add
|
|
46
|
+
permissions, sends no DM; a reinstall after an uninstall, a disconnect, or a
|
|
47
|
+
connection that needed a reinstall does.
|
|
48
|
+
|
|
34
49
|
After Slack redirects back, the Slack integration home continues through the
|
|
35
50
|
remaining setup steps: link your identity, create your automation, and activate
|
|
36
51
|
it. Team admins can expand **Team connection** there to inspect
|
|
@@ -38,9 +53,14 @@ permissions, known users, known channels, administrative activity, and
|
|
|
38
53
|
technical details. The same team-level information remains available in Team
|
|
39
54
|
Settings.
|
|
40
55
|
|
|
41
|
-
Disconnecting Slack stops
|
|
42
|
-
Slack
|
|
43
|
-
|
|
56
|
+
Disconnecting Slack stops Slack triggers, automation posts, and agent access to
|
|
57
|
+
Slack for the team. Data stored for the Slack connection is deleted within
|
|
58
|
+
14 business days. Uninstalling the app from the Slack workspace, or revoking
|
|
59
|
+
its bot token, does the same.
|
|
60
|
+
|
|
61
|
+
The team's boxes.dev threads and saved automation settings remain. See the
|
|
62
|
+
[privacy policy](https://boxes.dev/privacy#slack-retention) for retention details and how
|
|
63
|
+
to request deletion.
|
|
44
64
|
|
|
45
65
|
## Link Your Slack Identity
|
|
46
66
|
|
|
@@ -59,6 +79,12 @@ You can link by:
|
|
|
59
79
|
- opening the boxes.dev app DM in Slack and sending `connect`;
|
|
60
80
|
- following a connect link sent by a team admin from Team settings.
|
|
61
81
|
|
|
82
|
+
Until your Slack identity is linked, the app answers any mention or app DM from
|
|
83
|
+
you, including `help`, with a DM containing a connect link, the next setup
|
|
84
|
+
steps, and links to the Slack help article and support. The connect link works
|
|
85
|
+
whatever email your Slack profile uses; **Find my Slack account** matches your
|
|
86
|
+
boxes.dev email.
|
|
87
|
+
|
|
62
88
|
If boxes.dev cannot match your Slack user, verify your boxes.dev email and try
|
|
63
89
|
again from Slack.
|
|
64
90
|
|
|
@@ -269,10 +295,19 @@ unqualified follow-ups in that Slack thread go to the newest run.
|
|
|
269
295
|
|
|
270
296
|
Use Slack controls in the linked thread:
|
|
271
297
|
|
|
272
|
-
- `@boxes.dev !help`
|
|
298
|
+
- `@boxes.dev help` or `@boxes.dev !help` explains how to follow up, stop, and
|
|
299
|
+
cancel in that thread. It does not reach the agent.
|
|
273
300
|
- `@boxes.dev !stop` requests that the active agent turn stop.
|
|
274
301
|
- `@boxes.dev !cancel` cancels queued Slack follow-ups when possible.
|
|
275
302
|
|
|
303
|
+
Outside a linked thread, `help` or `!help` (mentioned, or sent alone in an app
|
|
304
|
+
DM) lists what the sender can start there: whether a plain request reaches
|
|
305
|
+
their Default behavior, and the named commands they may run. A bare `help`
|
|
306
|
+
never starts an agent; `help me with this bug` is an ordinary request. `!stop`
|
|
307
|
+
and `!cancel` outside a linked thread reply that they work only in the thread
|
|
308
|
+
where an agent started. `connect` from a sender whose Slack account is already
|
|
309
|
+
linked replies with that and the same help.
|
|
310
|
+
|
|
276
311
|
If the linked devbox is sleeping, boxes.dev may queue the follow-up while the
|
|
277
312
|
box wakes. If capacity is full, Slack replies with guidance when follow-up
|
|
278
313
|
confirmations are enabled.
|
|
@@ -394,6 +429,9 @@ the workspace.
|
|
|
394
429
|
|
|
395
430
|
## Troubleshooting
|
|
396
431
|
|
|
432
|
+
To see what you can start in a conversation, mention `@boxes.dev help` there or
|
|
433
|
+
send `help` in the app DM.
|
|
434
|
+
|
|
397
435
|
If **Connect Slack** is missing, ask a boxes.dev team admin to connect the
|
|
398
436
|
workspace.
|
|
399
437
|
|
|
@@ -89,7 +89,10 @@ compute; the former team's payment method and credits remain on that team.
|
|
|
89
89
|
## Finding And Managing Team Templates
|
|
90
90
|
|
|
91
91
|
Team admins can open **Team Templates** from the desktop project selector or
|
|
92
|
-
from **
|
|
92
|
+
from **Settings → Team and members → Manage Team Templates**. The global
|
|
93
|
+
settings pane's **Related settings → Team Template settings** link opens the
|
|
94
|
+
selected project's associated template, or the collection when there is no
|
|
95
|
+
source template. The project-selector submenu
|
|
93
96
|
links directly to each non-archived template and includes **New Team
|
|
94
97
|
Template...** and **View all Team Templates**. The collection shows each named
|
|
95
98
|
template separately, including its description, machine size, latest saved
|
|
@@ -1012,6 +1012,9 @@ returns to the CLI. For Claude Code, returning to GUI closes the native
|
|
|
1012
1012
|
terminal writer; the confirmation warns that unsent terminal input will be
|
|
1013
1013
|
lost and identifies any saved GUI draft that will reappear.
|
|
1014
1014
|
|
|
1015
|
+
While writing a prompt in either agent's desktop CLI view, press
|
|
1016
|
+
**Shift+Enter** to add a new line or **Enter** to send.
|
|
1017
|
+
|
|
1015
1018
|
Opening Claude Code in the CLI switches directly while its GUI agent is idle.
|
|
1016
1019
|
It requires confirmation if the GUI agent is working or another client owns
|
|
1017
1020
|
the terminal attachment. The transition can interrupt the current Claude turn
|
|
@@ -1087,8 +1090,10 @@ to finish or use the runtime controls if the whole runtime is stuck.
|
|
|
1087
1090
|
The desktop thread list groups work by devboxes, automations, and, when the
|
|
1088
1091
|
project has one, Template-box threads.
|
|
1089
1092
|
|
|
1090
|
-
Thread sections include pinned and recent chats.
|
|
1091
|
-
|
|
1093
|
+
Thread sections include pinned and recent chats. On desktop, drag pinned
|
|
1094
|
+
threads or devboxes to rearrange them within their **Pinned** section. The order
|
|
1095
|
+
will sync across devices. A grouped devbox moves with its threads. Template
|
|
1096
|
+
box threads may also support moving older archived
|
|
1092
1097
|
transcripts to cold storage.
|
|
1093
1098
|
|
|
1094
1099
|
Archived chats list with the machine they ran on. On desktop, the Template box
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@boxes-dev/dvb-runtime",
|
|
3
|
-
"version": "1.0.
|
|
3
|
+
"version": "1.0.1100",
|
|
4
4
|
"description": "Runtime for the boxes.dev CLI. Install @boxes-dev/dvb to use the CLI.",
|
|
5
5
|
"homepage": "https://boxes.dev",
|
|
6
6
|
"type": "module",
|
|
@@ -77,5 +77,5 @@
|
|
|
77
77
|
"e2b": "^2.18.0",
|
|
78
78
|
"ink-testing-library": "^4.0.0"
|
|
79
79
|
},
|
|
80
|
-
"devboxReleasedAt": "2026-10-
|
|
80
|
+
"devboxReleasedAt": "2026-10-21T20:43:36Z"
|
|
81
81
|
}
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|