@boxes-dev/dvb-runtime 1.0.1115 → 1.0.1117
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/agent-init-guides/flow.md +7 -6
- package/dist/agent-init-guides/git-signing.md +1 -1
- package/dist/agent-init-guides/recovery.md +1 -1
- package/dist/agent-init-guides/running.md +6 -4
- package/dist/bin/dvb.mjs +1548 -915
- package/dist/bin/dvbd.mjs +926 -347
- package/dist/product-docs/references/billing-and-limits.md +5 -4
- package/dist/product-docs/references/desktop-workbench.md +38 -13
- package/dist/product-docs/references/files-git-and-review.md +17 -6
- package/dist/product-docs/references/fork-workflows.md +9 -0
- package/dist/product-docs/references/onbox-agent-tools.md +121 -10
- package/dist/product-docs/references/slack.md +11 -8
- package/dist/product-docs/references/team-template.md +9 -1
- package/dist/product-docs/references/threads-and-agents.md +103 -6
- package/dist/product-docs/references/troubleshooting.md +3 -3
- package/package.json +3 -3
|
@@ -66,7 +66,8 @@ but discards a blank draft, while Alt+Q explicitly discards after
|
|
|
66
66
|
confirmation. The Codex or Claude choice is shared for the project across the
|
|
67
67
|
terminal, desktop, and mobile. Model, reasoning, and speed choices are shared
|
|
68
68
|
per Template box or devbox. Those choices apply to the first turn and become
|
|
69
|
-
the defaults for new drafts on every surface
|
|
69
|
+
the defaults for new drafts on every surface, unless the user has pinned
|
|
70
|
+
models for new threads (see **Models For New Threads**).
|
|
70
71
|
|
|
71
72
|
The terminal composer can attach PNG/JPEG images to a Codex or Claude first
|
|
72
73
|
turn from a supported OS clipboard or by pasting an entire local image path.
|
|
@@ -290,6 +291,58 @@ project uses Tailscale, only the copied source box briefly disconnects and
|
|
|
290
291
|
receives a fresh identity after the snapshot; sibling devboxes stay connected,
|
|
291
292
|
and the destination devbox enrolls with its own identity.
|
|
292
293
|
|
|
294
|
+
## Transferring A Thread To A Teammate
|
|
295
|
+
|
|
296
|
+
Choose **Transfer to a teammate...** from a Codex or Claude thread's menu to
|
|
297
|
+
hand the thread and its work to a teammate. The thread moves to a new devbox
|
|
298
|
+
in the teammate's project with your changes applied, and the teammate
|
|
299
|
+
continues it with their own accounts and environment, such as their Claude or
|
|
300
|
+
Codex subscription, GitHub access, cloud sign-ins, and environment variables.
|
|
301
|
+
The conversation arrives unchanged. When the transfer finishes, your thread
|
|
302
|
+
is archived, and its devbox is destroyed when no other thread uses it.
|
|
303
|
+
|
|
304
|
+
Only the thread's owner can transfer it, and the thread must be idle. Restore
|
|
305
|
+
an archived thread before transferring it. The teammate needs a project that
|
|
306
|
+
starts from the same Team Template as yours or checks out the same GitHub
|
|
307
|
+
repository; teammates without one appear unavailable in the dialog. When a
|
|
308
|
+
teammate has more than one matching project, choose the one that should
|
|
309
|
+
receive the transfer.
|
|
310
|
+
|
|
311
|
+
When other threads with history share the devbox, the dialog offers **This
|
|
312
|
+
thread** or **All N threads on this devbox**. Transferring the devbox moves
|
|
313
|
+
every one of those threads, and all of their agents need to be idle.
|
|
314
|
+
|
|
315
|
+
After exporting the conversation, boxes.dev sends your agent a work package
|
|
316
|
+
request in the thread. Your Git work from the thread's repository is packaged
|
|
317
|
+
automatically: local commits, staged and unstaged edits, and new files that
|
|
318
|
+
Git doesn't ignore. Your agent adds anything else the work needs, such as
|
|
319
|
+
ignored local data or files elsewhere on the devbox like `/tmp`. Packaging
|
|
320
|
+
only reads your devbox; the agent doesn't change files, environment
|
|
321
|
+
variables, or project settings for it. Environment files stay behind, so the
|
|
322
|
+
teammate keeps their own values. In the rare case that the work added a new
|
|
323
|
+
variable the teammate needs, the agent sends just that variable, and the
|
|
324
|
+
teammate gets it only if they don't already have one by that name; their
|
|
325
|
+
values are never replaced. The request runs on your accounts and waits until your
|
|
326
|
+
thread is idle. If your agent doesn't package the work within 30 minutes, the
|
|
327
|
+
transfer stops and you can try again.
|
|
328
|
+
|
|
329
|
+
The transferred thread appears in the teammate's project right away, marked
|
|
330
|
+
**Transferring** while its devbox starts and the work is packaged and applied.
|
|
331
|
+
They can't send messages in it until it's ready. boxes.dev then checks out
|
|
332
|
+
your branch on their devbox at the commit you started from, applies your
|
|
333
|
+
changes, and marks the transferred threads unread. The teammate gets a
|
|
334
|
+
notification, and a dismissible notice in each thread says who sent it and
|
|
335
|
+
which branch has your changes. Files that already exist on their devbox, such
|
|
336
|
+
as environment files their project manages, are kept and listed in that
|
|
337
|
+
notice. If the changes can't be applied, for example because the starting
|
|
338
|
+
commit was removed from the remote, the notice gives the package's location so
|
|
339
|
+
their agent can apply it, and your threads and devbox are kept.
|
|
340
|
+
|
|
341
|
+
Your thread shows the transfer's progress. If it fails, choose **Try again**
|
|
342
|
+
in that notice. A transfer never destroys a Template box; transferring a
|
|
343
|
+
thread from one archives only the thread. Commits in your changes keep you as
|
|
344
|
+
their author.
|
|
345
|
+
|
|
293
346
|
## MCP Connections
|
|
294
347
|
|
|
295
348
|
Open **Integrations → MCPs** in the desktop app to manage remote MCP servers in
|
|
@@ -704,6 +757,8 @@ search.
|
|
|
704
757
|
|
|
705
758
|
On mobile, managed Codex and Claude Code conversations support both photos and
|
|
706
759
|
general files, including ZIP archives, from the composer attachment menu.
|
|
760
|
+
On iOS, you can also copy an image, touch and hold the reply box, and choose
|
|
761
|
+
**Paste** to add it as an attachment.
|
|
707
762
|
Mobile files can be up to 50 MiB each, with up to 100 MiB of files on one
|
|
708
763
|
message. During an active Codex turn, attachments can be sent with **Steer** but
|
|
709
764
|
cannot be added to a **Queue** follow-up.
|
|
@@ -818,6 +873,29 @@ thread, and later successful sends won't dismiss earlier warnings.
|
|
|
818
873
|
If a thread is blocked because the selected box is sleeping, not ready, or
|
|
819
874
|
missing auth, the composer shows the reason and any available repair action.
|
|
820
875
|
|
|
876
|
+
## Models For New Threads
|
|
877
|
+
|
|
878
|
+
On desktop and mobile, a user's new Codex and Claude threads in a project
|
|
879
|
+
start with the model, reasoning, and speed that user picked most recently for
|
|
880
|
+
that agent in the project, including a change made in an existing thread. To
|
|
881
|
+
keep new threads on one setup, choose **Pin for new threads** at the bottom
|
|
882
|
+
of the model menu on desktop or the model options on mobile. That pins the
|
|
883
|
+
current model, reasoning, and speed (fast mode for Claude; for Codex, also the
|
|
884
|
+
model provider connection) for that agent. Later changes in any thread will
|
|
885
|
+
apply only to that thread, and new threads will keep starting with the pin.
|
|
886
|
+
Codex and Claude have separate pins, each pin belongs to one user and one
|
|
887
|
+
project, and which agent a new thread uses still follows the last choice.
|
|
888
|
+
|
|
889
|
+
When the open thread or draft uses the pinned setup, the row reads **Pinned
|
|
890
|
+
for new threads** with **Unpin**; choosing it clears the pin, and the next pick
|
|
891
|
+
becomes the default again. When it uses something else, the row reads **Pin
|
|
892
|
+
for new threads**, and the pinned setup appears in a tooltip when hovering on
|
|
893
|
+
desktop and under the row on mobile; choosing it replaces the pin with the
|
|
894
|
+
current controls. **Project settings** has a
|
|
895
|
+
**Models for new threads** card on desktop and a row of the same name on
|
|
896
|
+
mobile, which list each pin and clear it with **Clear**. Automation editors do
|
|
897
|
+
not show the pin row.
|
|
898
|
+
|
|
821
899
|
## Codex Controls
|
|
822
900
|
|
|
823
901
|
If Codex stops with an error after receiving your message, the message stays in
|
|
@@ -862,9 +940,13 @@ Codex threads expose model controls in the composer footer:
|
|
|
862
940
|
On desktop or mobile, type `$` in a Codex reply box to choose from the skills
|
|
863
941
|
available to Codex on that machine. Each row shows where the skill comes from:
|
|
864
942
|
Project, Personal, Plugin, Account (a plugin installed through your ChatGPT
|
|
865
|
-
account or workspace), Admin, or Built-in.
|
|
866
|
-
|
|
867
|
-
|
|
943
|
+
account or workspace), Admin, or Built-in. On desktop, choosing a skill adds
|
|
944
|
+
an inline tag whose file path is available on hover. The message retains that
|
|
945
|
+
path, so Codex will load the selected skill even when another has the same
|
|
946
|
+
name. On mobile, choosing a skill adds `$name`, which needs to be unique on
|
|
947
|
+
the box for Codex to load the skill automatically. Skills the user
|
|
948
|
+
chooses most often are listed first (see the ordering note under **Claude
|
|
949
|
+
Controls**). Before the box connects, including in a new thread, the composer
|
|
868
950
|
shows the skills boxes.dev last read from a Codex thread in the same project,
|
|
869
951
|
so its list fills in once a started Codex thread in that project has been
|
|
870
952
|
opened; Account skills appear there only while the Codex account they came from
|
|
@@ -982,6 +1064,14 @@ list leaves out `/model` and `/fast`, which the model menu covers. On desktop, `
|
|
|
982
1064
|
`/model <model>` switches directly to a known model. Older supported model generations appear
|
|
983
1065
|
under **More models** in the picker.
|
|
984
1066
|
|
|
1067
|
+
The Codex `$` and Claude `/` lists put the skills and commands the user has
|
|
1068
|
+
chosen most often first, and recent choices count more than older ones, so a
|
|
1069
|
+
skill that stops being used gradually moves back down. Typed text still decides
|
|
1070
|
+
which entries match and puts names that start with it ahead of other matches;
|
|
1071
|
+
usage orders the entries within those. Choices are saved with
|
|
1072
|
+
the user's boxes.dev account, so the order is the same on desktop and mobile,
|
|
1073
|
+
and a skill with the same name in Codex and Claude shares one count.
|
|
1074
|
+
|
|
985
1075
|
`/clear`, `/new`, and `/reset` are unavailable in a Claude thread. The command
|
|
986
1076
|
list leaves them out, and desktop, mobile, the CLI, and other agents can't send
|
|
987
1077
|
them. Start a new thread to clear Claude's context. A message is refused only
|
|
@@ -1054,7 +1144,8 @@ Model, reasoning, and fast mode selections belong to the Claude thread. A new
|
|
|
1054
1144
|
selection remains associated with that thread while it is applied, and the
|
|
1055
1145
|
confirmed settings follow the thread when it is reopened or resumed on desktop
|
|
1056
1146
|
or mobile. Changing one thread does not change another existing thread; the
|
|
1057
|
-
last-used selection can still become the starting default for a new thread
|
|
1147
|
+
last-used selection can still become the starting default for a new thread
|
|
1148
|
+
unless the user has pinned one (see **Models For New Threads**).
|
|
1058
1149
|
|
|
1059
1150
|
On a connected managed Claude thread, the desktop and mobile composers
|
|
1060
1151
|
also offer these modes when the runtime supports switching them:
|
|
@@ -1358,7 +1449,7 @@ section, and archived threads. Pinned threads keep their own order. In the
|
|
|
1358
1449
|
activity orders, each row's time and date group show its last activity.
|
|
1359
1450
|
|
|
1360
1451
|
**Group devboxes started by agents**, below **Sort threads**, lists each devbox
|
|
1361
|
-
an agent started under the devbox that started it. It is
|
|
1452
|
+
an agent started under the devbox that started it. It is on by default and
|
|
1362
1453
|
saved on the account, so every computer and phone follows it. A slim row under
|
|
1363
1454
|
the parent shows whether any of those devboxes are working, unread, or need the
|
|
1364
1455
|
user, and selecting the row shows or hides them. On desktop the row starts
|
|
@@ -1433,6 +1524,10 @@ shared transcript does not select or wake the viewer's last Template box or
|
|
|
1433
1524
|
devbox. Merely browsing a teammate's work does not add it to **Shared with
|
|
1434
1525
|
me**.
|
|
1435
1526
|
|
|
1527
|
+
Shared and team views are for reading. To give a teammate work they can
|
|
1528
|
+
continue with their own accounts, transfer the thread to them instead; see
|
|
1529
|
+
**Transferring A Thread To A Teammate**.
|
|
1530
|
+
|
|
1436
1531
|
An owner can also share an eligible started Codex or Claude Code transcript
|
|
1437
1532
|
with anyone on their team who has the link. The share includes the live durable
|
|
1438
1533
|
conversation, status, commands, tool output, diffs, attachments, and images, so
|
|
@@ -1534,6 +1629,8 @@ The thread action menu can include:
|
|
|
1534
1629
|
- Copy personal deeplink, which reopens the thread in your own workbench and
|
|
1535
1630
|
does not give anyone else access.
|
|
1536
1631
|
- Move to new devbox for eligible Template box threads.
|
|
1632
|
+
- Transfer to a teammate, which moves the thread and its work to a new devbox
|
|
1633
|
+
in a teammate's project.
|
|
1537
1634
|
- New thread.
|
|
1538
1635
|
- Sleep now for eligible devbox threads.
|
|
1539
1636
|
- Destroy and archive for devbox-owning rows.
|
|
@@ -538,9 +538,9 @@ credentials automatically after a command fails.
|
|
|
538
538
|
|
|
539
539
|
To let `gh` use the user's own GitHub permissions, connect optional personal
|
|
540
540
|
access. In **Integrations → GitHub**, choose **Connect personal access** under
|
|
541
|
-
**GitHub CLI access**; in **Account** settings, choose **Connect
|
|
542
|
-
**Personal GitHub CLI access (optional)**. Alternatively, run
|
|
543
|
-
on the Template box or devbox. It will print a one-time code and a GitHub
|
|
541
|
+
**GitHub CLI access**; in **Account** settings, choose **Connect personal
|
|
542
|
+
access** under **Personal GitHub CLI access (optional)**. Alternatively, run
|
|
543
|
+
`gh auth login` on the Template box or devbox. It will print a one-time code and a GitHub
|
|
544
544
|
approval URL, then wait until the user approves with the GitHub account
|
|
545
545
|
connected to boxes.dev. An agent that runs it should give the user the code and
|
|
546
546
|
URL. After approval, managed `gh` will prefer personal access on all of the
|
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.1117",
|
|
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",
|
|
@@ -57,7 +57,7 @@
|
|
|
57
57
|
"@clack/core": "^1.0.0",
|
|
58
58
|
"@clack/prompts": "^1.0.0",
|
|
59
59
|
"cli-truncate": "^6.1.1",
|
|
60
|
-
"convex": "^1.
|
|
60
|
+
"convex": "^1.48.0",
|
|
61
61
|
"file-type": "^22.0.1",
|
|
62
62
|
"ink": "^7.1.1",
|
|
63
63
|
"jsonc-parser": "^3.3.1",
|
|
@@ -77,5 +77,5 @@
|
|
|
77
77
|
"e2b": "^2.18.0",
|
|
78
78
|
"ink-testing-library": "^4.0.0"
|
|
79
79
|
},
|
|
80
|
-
"devboxReleasedAt": "2026-11-
|
|
80
|
+
"devboxReleasedAt": "2026-11-09T06:42:54Z"
|
|
81
81
|
}
|