@boxes-dev/dvb-runtime 1.0.1076 → 1.0.1077
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/git-signing.md +10 -3
- package/dist/bin/dvb.mjs +587 -218
- package/dist/bin/dvbd.mjs +4 -4
- package/dist/product-docs/references/cli.md +9 -0
- package/dist/product-docs/references/desktop-workbench.md +21 -12
- package/dist/product-docs/references/files-git-and-review.md +96 -32
- package/dist/product-docs/references/fork-workflows.md +5 -2
- package/dist/product-docs/references/getting-started.md +3 -1
- package/dist/product-docs/references/index.md +1 -1
- package/dist/product-docs/references/linear.md +3 -3
- package/dist/product-docs/references/mobile.md +14 -10
- package/dist/product-docs/references/onbox-agent-tools.md +115 -10
- package/dist/product-docs/references/project-setup.md +24 -14
- package/dist/product-docs/references/security-and-data.md +1 -1
- package/dist/product-docs/references/slack.md +23 -22
- package/dist/product-docs/references/tailscale.md +2 -2
- package/dist/product-docs/references/team-template.md +33 -17
- package/dist/product-docs/references/template-box-environment.md +1 -1
- package/dist/product-docs/references/threads-and-agents.md +2 -2
- package/dist/product-docs/references/troubleshooting.md +3 -3
- package/package.json +2 -2
|
@@ -47,10 +47,11 @@ which has three steps:
|
|
|
47
47
|
once and expires within 30 minutes. The textbox automatically regenerates
|
|
48
48
|
the code after use and before it expires, so the user can copy a fresh
|
|
49
49
|
prompt if an earlier attempt fails.
|
|
50
|
-
3. **Get the desktop app**: the agent gives the user the
|
|
51
|
-
setup starts, and **Download for Mac now** is available right away.
|
|
52
|
-
|
|
53
|
-
|
|
50
|
+
3. **Get the desktop app**: the agent gives the user the desktop app link
|
|
51
|
+
once setup starts, and **Download for Mac now** is available right away.
|
|
52
|
+
Linux browsers see **Download for Linux now** instead. On Windows browsers
|
|
53
|
+
that boxes.dev can confidently identify, this step says the desktop app is
|
|
54
|
+
only available for Mac and Linux and links to the mobile app instead.
|
|
54
55
|
|
|
55
56
|
On a phone, the second step becomes **Continue on your computer**, with
|
|
56
57
|
actions to email, copy, or share a link to the page, and the desktop step is
|
|
@@ -380,12 +381,13 @@ keeps waiting; it can stop the command and check setup status.
|
|
|
380
381
|
one connected coding agent.
|
|
381
382
|
|
|
382
383
|
Once the setup thread starts on the Template box, `dvb agent-init run` tells
|
|
383
|
-
the agent where the user can follow it. On a Mac with the
|
|
384
|
-
installed, the agent offers to open it with
|
|
385
|
-
which opens the Template box on the setup
|
|
386
|
-
the agent gives the download link
|
|
387
|
-
|
|
388
|
-
|
|
384
|
+
the agent where the user can follow it. On a Mac or Linux computer with the
|
|
385
|
+
desktop app installed, the agent offers to open it with
|
|
386
|
+
`dvb agent-init open-desktop`, which opens the Template box on the setup
|
|
387
|
+
thread. Without the app, the agent gives the download link for that computer
|
|
388
|
+
(`https://boxes.dev/mac` or `https://boxes.dev/linux`), and on other
|
|
389
|
+
computers or over SSH, it points to the mobile app. When setup finishes on a
|
|
390
|
+
Mac or Linux computer with the desktop app installed, `dvb agent-init` opens the app on the setup thread, where the user
|
|
389
391
|
can read the setup agent's summary. Otherwise, the agent lists the same
|
|
390
392
|
choices. Either way, the agent also mentions `dvb agents <project>`, which
|
|
391
393
|
opens the Template box's agent threads in the terminal (`--workspace` keeps
|
|
@@ -432,9 +434,10 @@ desktop app, or switch from the mobile app. Claude API keys are unchanged.
|
|
|
432
434
|
|
|
433
435
|
Once a claude.ai login is saved, Configure agents and mobile Agent accounts
|
|
434
436
|
show **Allow claude.ai connectors**, which is on by default. Turning it off
|
|
435
|
-
keeps claude.ai connectors out of
|
|
436
|
-
and Slack runs that use the account; synced skills and plugins
|
|
437
|
-
|
|
437
|
+
keeps claude.ai connectors out of Claude the next time it starts, including in
|
|
438
|
+
automation and Slack runs that use the account; synced skills and plugins
|
|
439
|
+
still load. A Claude process that is already running keeps its connectors
|
|
440
|
+
until it restarts.
|
|
438
441
|
|
|
439
442
|
Each saved subscription row in desktop Configure agents shows a small bar for
|
|
440
443
|
the weekly limit's remaining usage. A 5-hour bar appears below it only when
|
|
@@ -892,7 +895,14 @@ for those repos. Setup verifies signed commits locally on the Template box, but
|
|
|
892
895
|
Git host "Verified" badges still require the public signing key to be registered
|
|
893
896
|
with the Git host.
|
|
894
897
|
|
|
895
|
-
In agent-driven setup,
|
|
898
|
+
In agent-driven setup, an explicit `gitSigning.mode: create` can also set up
|
|
899
|
+
signing when no selected repository signs locally. It uses local Git
|
|
900
|
+
`user.name` and `user.email`, with OpenPGP by default or SSH when `gpg.format`
|
|
901
|
+
is `ssh`; it does not require an existing signing key or change local signing
|
|
902
|
+
settings. OpenPGP creation requires GnuPG on the user's computer. Projects that
|
|
903
|
+
mix signed and unsigned repositories keep their existing signing scope.
|
|
904
|
+
|
|
905
|
+
`run` prints the public signing key and the host's
|
|
896
906
|
registration instructions. Retrieve them again with `dvb agent-init status`,
|
|
897
907
|
including after setup finishes. Private keys are never printed. Signing
|
|
898
908
|
identifies the signer of a commit; it does not grant pull or push access.
|
|
@@ -114,7 +114,7 @@ receive only Claude's current short-lived access, written where Claude Code
|
|
|
114
114
|
reads its own login. A claude.ai login also lets Claude use the connectors the
|
|
115
115
|
user added on claude.ai, such as Gmail, so an agent on a box can reach those
|
|
116
116
|
services; **Allow claude.ai connectors** in Configure agents or Agent accounts
|
|
117
|
-
turns that off
|
|
117
|
+
turns that off. The change takes effect the next time Claude starts.
|
|
118
118
|
|
|
119
119
|
Agent credentials should be treated like other development credentials. If a
|
|
120
120
|
user no longer wants an agent credential available in boxes.dev, they should
|
|
@@ -26,7 +26,7 @@ channels where the app is available and in 1:1 app DMs.
|
|
|
26
26
|
## Connect Slack
|
|
27
27
|
|
|
28
28
|
Open the desktop workbench's **Integrations** section and choose **Connect**
|
|
29
|
-
for Slack. Team admins can also connect Slack from **Team
|
|
29
|
+
for Slack. Team admins can also connect Slack from **Team settings**, or from
|
|
30
30
|
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.
|
|
@@ -57,7 +57,7 @@ You can link by:
|
|
|
57
57
|
identity** on the **Account** page when boxes.dev hasn't seen your Slack
|
|
58
58
|
account yet;
|
|
59
59
|
- opening the boxes.dev app DM in Slack and sending `connect`;
|
|
60
|
-
- following a connect link sent by a team admin from Team
|
|
60
|
+
- following a connect link sent by a team admin from Team settings.
|
|
61
61
|
|
|
62
62
|
If boxes.dev cannot match your Slack user, verify your boxes.dev email and try
|
|
63
63
|
again from Slack.
|
|
@@ -330,27 +330,28 @@ output, needs-input, and failed-run events.
|
|
|
330
330
|
## Shared Thread Previews
|
|
331
331
|
|
|
332
332
|
When someone posts a boxes.dev share link (`/t/...`) in Slack, boxes.dev adds
|
|
333
|
-
a preview
|
|
334
|
-
|
|
335
|
-
|
|
336
|
-
the
|
|
337
|
-
|
|
338
|
-
|
|
339
|
-
|
|
340
|
-
|
|
341
|
-
|
|
342
|
-
|
|
343
|
-
|
|
344
|
-
|
|
345
|
-
|
|
346
|
-
|
|
347
|
-
|
|
348
|
-
|
|
349
|
-
|
|
333
|
+
a preview to the message. The preview shows the thread's title, one message,
|
|
334
|
+
a line with the boxes.dev logo, "boxes.dev", the project, the status, and the
|
|
335
|
+
time of the last message, and an **Open in boxes.dev** button. The title and
|
|
336
|
+
the button open the link as posted. The message is a plain-text excerpt of
|
|
337
|
+
the agent's latest finished reply, or the first message until the agent has
|
|
338
|
+
replied; Slack folds an excerpt longer than four lines behind **Show more**. A
|
|
339
|
+
thread without a manual or generated title shows
|
|
340
|
+
**boxes.dev thread**. The status is **Working**, **Waiting for input**,
|
|
341
|
+
**Failed**, **Cold stored**, or **History only** while one applies, **Done**
|
|
342
|
+
for an idle thread that has a reply, and absent otherwise. Slack shows the
|
|
343
|
+
time relative to now, such as "5 minutes ago".
|
|
344
|
+
|
|
345
|
+
Everyone who can see the Slack message sees the same preview, including
|
|
346
|
+
workspace guests; there is no separate details view. boxes.dev updates posted
|
|
347
|
+
previews when a prompt is sent, a turn starts, finishes, fails, or is
|
|
348
|
+
interrupted, the agent asks for input, or the thread is renamed. Each share
|
|
349
|
+
link in a message gets its own preview, and Slack previews at most five links
|
|
350
|
+
per message.
|
|
350
351
|
|
|
351
352
|
A revoked or private share, a deleted thread, an owner whose account was
|
|
352
353
|
deleted or who left the team keeping the project, and another team's share all
|
|
353
|
-
show **This shared thread isn't available**, and posted
|
|
354
|
+
show **This shared thread isn't available**, and posted previews switch to it
|
|
354
355
|
within seconds. Previews also appear in DMs, group DMs, and private channels
|
|
355
356
|
without the app. boxes.dev adds no preview in conversations Slack reports as
|
|
356
357
|
shared with another organization.
|
|
@@ -361,7 +362,7 @@ them. The Slack integration home shows **Update available** and "Reinstall the
|
|
|
361
362
|
Slack app to turn on previews for shared thread links." Members instead see
|
|
362
363
|
that a team admin needs to reinstall it. A team admin needs to choose
|
|
363
364
|
**Reinstall** there, or **Reinstall Slack** from the Slack actions menu in
|
|
364
|
-
**Team
|
|
365
|
+
**Team settings**, and approve the request in Slack.
|
|
365
366
|
|
|
366
367
|
## Current Limits
|
|
367
368
|
|
|
@@ -389,7 +390,7 @@ If Slack says your user is not linked, use **Find my Slack account** or send
|
|
|
389
390
|
|
|
390
391
|
If a channel is not available, add `@boxes.dev` to the channel and run
|
|
391
392
|
**Check** from **Team connection** on the Slack integration home (or
|
|
392
|
-
**Recheck** in Team
|
|
393
|
+
**Recheck** in Team settings).
|
|
393
394
|
|
|
394
395
|
If a share link gets no preview, confirm the conversation isn't shared with
|
|
395
396
|
another organization and the Slack connection lists no missing permissions. See [Shared Thread Previews](#shared-thread-previews).
|
|
@@ -45,7 +45,7 @@ The setup sequence is:
|
|
|
45
45
|
|
|
46
46
|
The Tailscale admin returns the Tailnet ID, `tag:boxes-dev`, OAuth client ID,
|
|
47
47
|
and one-time-displayed OAuth client secret. The boxes.dev team admin enters all
|
|
48
|
-
four values from the project's Tailscale integration page or Team
|
|
48
|
+
four values from the project's Tailscale integration page or Team settings.
|
|
49
49
|
Both surfaces keep a separate connection form visible beneath four selectable
|
|
50
50
|
setup tabs, so an admin can move among the detailed Tag, Access, OAuth, and
|
|
51
51
|
Tailnet ID instructions without losing entered values. boxes.dev validates the
|
|
@@ -59,7 +59,7 @@ OAuth credential stays central.
|
|
|
59
59
|
|
|
60
60
|
The required read scopes let boxes.dev read the tailnet's full device and user
|
|
61
61
|
directories, access policy, and device posture attributes. Device mutations
|
|
62
|
-
and auth-key creation are restricted to the configured tag. Team
|
|
62
|
+
and auth-key creation are restricted to the configured tag. Team settings
|
|
63
63
|
discloses this access before the connection is saved.
|
|
64
64
|
|
|
65
65
|
## Who Can Enable It
|
|
@@ -51,7 +51,7 @@ a saved version or a project created from it.
|
|
|
51
51
|
|
|
52
52
|
### Removing A Team Member
|
|
53
53
|
|
|
54
|
-
An admin can remove another member from **Team
|
|
54
|
+
An admin can remove another member from **Team settings → Members** using the
|
|
55
55
|
member's menu. Select a remaining member as the work recipient, then choose
|
|
56
56
|
**Transfer**, **Delete**, or **Keep** for every project. Transfer preserves the
|
|
57
57
|
project's work under the recipient and records its original account. Delete
|
|
@@ -72,7 +72,7 @@ account can continue using its personal team and will not automatically rejoin
|
|
|
72
72
|
the former team through its email domain. Remove its paid seat in Billing and
|
|
73
73
|
finish pending project operations first. Team Template editing sessions must
|
|
74
74
|
be saved or discarded before removal. Admins cannot remove themselves.
|
|
75
|
-
An interrupted removal remains in Team
|
|
75
|
+
An interrupted removal remains in Team settings with progress and a retry
|
|
76
76
|
action; closing its dialog does not cancel it.
|
|
77
77
|
The dialog counts the remaining records before each start or retry, then
|
|
78
78
|
shows how many records have moved out of that total. A retry counts only the
|
|
@@ -99,13 +99,14 @@ here.
|
|
|
99
99
|
The collection and each template's detail page also work in a web browser, so
|
|
100
100
|
an admin can keep a template open beside the desktop workbench. In the desktop
|
|
101
101
|
app, **Open in browser** opens the current Team Templates page in the default
|
|
102
|
-
browser. On the website, **Team** in the header opens Team
|
|
102
|
+
browser. On the website, **Team** in the header opens Team settings, where
|
|
103
103
|
**Manage Team Templates** opens the collection. A browser can change everything
|
|
104
104
|
on the detail page except the editing session itself: creating a template,
|
|
105
105
|
GitHub setup, **Take control**, continuing an editing session, and **Resolve**
|
|
106
|
-
all need the desktop app on a Mac. In their place, a
|
|
107
|
-
|
|
108
|
-
phones, tablets,
|
|
106
|
+
all need the desktop app on a Mac or Linux computer. In their place, a
|
|
107
|
+
browser on a Mac or Linux computer shows **Open in desktop app**, which opens
|
|
108
|
+
the same template in the desktop app; phones, tablets, and Windows show a note
|
|
109
|
+
instead.
|
|
109
110
|
|
|
110
111
|
**Project settings** for a project made from a Team Template names that
|
|
111
112
|
template. A managed project shows the template it uses, and an independent
|
|
@@ -116,14 +117,28 @@ detail page.
|
|
|
116
117
|
Team members do not see the management submenu. To create a project from a
|
|
117
118
|
saved template, choose **New project...**, then **Start from a Team Template**.
|
|
118
119
|
|
|
119
|
-
Admins create a Team Template from this collection
|
|
120
|
-
|
|
121
|
-
|
|
122
|
-
|
|
123
|
-
|
|
124
|
-
|
|
125
|
-
|
|
126
|
-
|
|
120
|
+
Admins create a Team Template from this collection with **New Team
|
|
121
|
+
Template**, which offers two starting points.
|
|
122
|
+
|
|
123
|
+
**Create from an existing project** is the recommended path. It lists the
|
|
124
|
+
admin's unarchived projects whose Template box has finished setup, including
|
|
125
|
+
projects that still need GitHub access; managed projects have no Template box
|
|
126
|
+
and are not listed. Selecting a project opens an ordinary new-thread draft on
|
|
127
|
+
that project's Template box with `Create a Team Template from this project` in
|
|
128
|
+
the composer, using the project's default agent and settings. The admin can
|
|
129
|
+
change the agent, model, and reasoning effort before sending it, and the agent
|
|
130
|
+
doesn't start until it's sent. Opening the draft also turns on the box-wide **Create Team Templates** agent permission
|
|
131
|
+
(`create-team-templates`) for that Template box. The thread then follows **Create a Team Template from
|
|
132
|
+
this project** in [On-box agent tools](onbox-agent-tools.md), so the template
|
|
133
|
+
starts from clean GitHub clones and the admin reviews the spec before creation.
|
|
134
|
+
|
|
135
|
+
**Create from scratch** starts from GitHub: choose one or several existing
|
|
136
|
+
repositories, or create a new repository on GitHub, then review their
|
|
137
|
+
direct-child paths under `/home/boxes`. **Start empty** keeps the
|
|
138
|
+
clean-machine flow available. GitHub setup uses temporary boxes.dev GitHub App
|
|
139
|
+
access limited to the selected repositories while cloning them. It does not
|
|
140
|
+
require SSH-key registration or a desktop private-key transfer. An interrupted
|
|
141
|
+
setup can be continued from the template's card or detail page.
|
|
127
142
|
|
|
128
143
|
If you discard a GitHub-backed editing session before the first save, reopening
|
|
129
144
|
the template will recreate the originally selected repositories as clean
|
|
@@ -131,8 +146,9 @@ clones. Other unsaved files from the discarded session cannot be recovered.
|
|
|
131
146
|
|
|
132
147
|
The template's name and description can change later, but its machine size is
|
|
133
148
|
fixed after creation and is inherited by projects made from it. Creating and
|
|
134
|
-
preparing the entry does not create a usable saved version:
|
|
135
|
-
|
|
149
|
+
preparing the entry does not create a usable saved version: the machine must be
|
|
150
|
+
inspected and saved first, either by an admin in the editor or by the creating
|
|
151
|
+
agent after the admin asks it to save.
|
|
136
152
|
|
|
137
153
|
Open a template's detail page to inspect and administer it; members start
|
|
138
154
|
projects from the normal new-project flow instead. The admin page groups
|
|
@@ -320,7 +336,7 @@ personal or project connection is ready. Marking one **Recommended** lets the
|
|
|
320
336
|
owner choose **Finish without recommendations**. The saved requirement contains
|
|
321
337
|
no provider credentials, identities, automation settings, or machine state.
|
|
322
338
|
|
|
323
|
-
|
|
339
|
+
Box size is fixed for the Team Template lineage and is not a Project
|
|
324
340
|
default. Project creation offers no per-default overrides; members can change
|
|
325
341
|
the resulting ordinary project afterward.
|
|
326
342
|
|
|
@@ -86,7 +86,7 @@ settings card.
|
|
|
86
86
|
Successful additions and reviews on the Template box automatically create one
|
|
87
87
|
new Template snapshot. Future devboxes inherit that saved filesystem and repo
|
|
88
88
|
index; existing devboxes do not change. The completion dialog links to
|
|
89
|
-
**Devbox lifecycle → New devbox defaults → Startup
|
|
89
|
+
**Devbox lifecycle → New devbox defaults → Startup script** in case the new
|
|
90
90
|
repositories need install or startup commands, but it never changes the script
|
|
91
91
|
automatically.
|
|
92
92
|
|
|
@@ -576,7 +576,7 @@ steer at its next available opportunity; a message sent during a final response
|
|
|
576
576
|
may get a separate response afterward. Both actions support Claude's existing
|
|
577
577
|
attachments.
|
|
578
578
|
|
|
579
|
-
Desktop Settings has a separate **Claude
|
|
579
|
+
Desktop Settings has a separate **Claude replies** default. Enter will use
|
|
580
580
|
that action while Claude is working, and Cmd/Ctrl+Enter will use the alternate
|
|
581
581
|
action. On mobile, use the **Queue**/**Steer** control beside the composer.
|
|
582
582
|
An idle thread starts normally with either preference. Once Claude accepts a
|
|
@@ -974,7 +974,7 @@ The desktop thread list groups work by devboxes, automations, and, when the
|
|
|
974
974
|
project has one, Template-box threads.
|
|
975
975
|
|
|
976
976
|
Thread sections include pinned, recent, and archived chats. Template box pinned
|
|
977
|
-
threads can be reordered. Archived
|
|
977
|
+
threads can be reordered. Archived threads can be shown or hidden. Template box
|
|
978
978
|
threads may also support moving older archived transcripts to cold storage.
|
|
979
979
|
|
|
980
980
|
Rows show status indicators for draft, starting, active, unread, idle, archived,
|
|
@@ -469,7 +469,7 @@ the same block again.
|
|
|
469
469
|
|
|
470
470
|
## Slack Problems
|
|
471
471
|
|
|
472
|
-
For Slack-triggered automations, check Team
|
|
472
|
+
For Slack-triggered automations, check Team settings > Slack.
|
|
473
473
|
|
|
474
474
|
Common fixes:
|
|
475
475
|
|
|
@@ -478,7 +478,7 @@ Common fixes:
|
|
|
478
478
|
reinstall Slack.
|
|
479
479
|
- If known users or channels are stale, use the check/verification action.
|
|
480
480
|
- If a user cannot start or receive Slack-linked work, link that user's Slack
|
|
481
|
-
identity from Account settings or send a connect link from Team
|
|
481
|
+
identity from Account settings or send a connect link from Team settings.
|
|
482
482
|
- If attachments are missing, confirm the bot can access the channel and the
|
|
483
483
|
file is still available in Slack.
|
|
484
484
|
- If several Slack mentions start at once and some fail to launch, check awake
|
|
@@ -489,7 +489,7 @@ authorization, so a team admin should do it intentionally.
|
|
|
489
489
|
|
|
490
490
|
## Linear Problems
|
|
491
491
|
|
|
492
|
-
For Linear assignment-triggered automations, check Team
|
|
492
|
+
For Linear assignment-triggered automations, check Team settings > Linear.
|
|
493
493
|
|
|
494
494
|
Common fixes:
|
|
495
495
|
|
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.1077",
|
|
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-15T19:24:00Z"
|
|
81
81
|
}
|