@boxes-dev/dvb-runtime 1.0.1050 → 1.0.1052
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 +32 -8
- package/dist/bin/dvb.mjs +28382 -27504
- package/dist/bin/dvbd.mjs +14 -6
- package/dist/product-docs/references/cli.md +21 -9
- package/dist/product-docs/references/desktop-workbench.md +14 -10
- package/dist/product-docs/references/mobile.md +9 -8
- package/dist/product-docs/references/onbox-agent-tools.md +6 -3
- package/dist/product-docs/references/project-setup.md +82 -36
- package/dist/product-docs/references/remote-assistants.md +3 -2
- package/dist/product-docs/references/slack.md +65 -14
- package/dist/product-docs/references/team-template.md +17 -5
- package/package.json +2 -2
package/dist/bin/dvbd.mjs
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
#!/usr/bin/env node
|
|
2
2
|
|
|
3
|
-
!function(){try{var e="undefined"!=typeof window?window:"undefined"!=typeof global?global:"undefined"!=typeof globalThis?globalThis:"undefined"!=typeof self?self:{},n=(new e.Error).stack;n&&(e._sentryDebugIds=e._sentryDebugIds||{},e._sentryDebugIds[n]="
|
|
3
|
+
!function(){try{var e="undefined"!=typeof window?window:"undefined"!=typeof global?global:"undefined"!=typeof globalThis?globalThis:"undefined"!=typeof self?self:{},n=(new e.Error).stack;n&&(e._sentryDebugIds=e._sentryDebugIds||{},e._sentryDebugIds[n]="a9afcb43-4806-5154-9842-36529ed47771")}catch(e){}}();
|
|
4
4
|
import { createRequire as __dvbCreateRequire } from "node:module";
|
|
5
5
|
import { dirname as __dvbDirname } from "node:path";
|
|
6
6
|
import { fileURLToPath as __dvbFileURLToPath } from "node:url";
|
|
@@ -64612,9 +64612,9 @@ var init_sentry = __esm({
|
|
|
64612
64612
|
uncaughtExceptionMonitorInstalled = false;
|
|
64613
64613
|
currentDevboxSentryUser = null;
|
|
64614
64614
|
readBuildMetadata = () => {
|
|
64615
|
-
const rawPackageVersion = "1.0.
|
|
64616
|
-
const rawGitSha = "
|
|
64617
|
-
const rawSentryRelease = "boxes-dev-dvb@1.0.
|
|
64615
|
+
const rawPackageVersion = "1.0.1052";
|
|
64616
|
+
const rawGitSha = "6e5360aed3f79e9b0b4d34adaaea7b174277c4d7";
|
|
64617
|
+
const rawSentryRelease = "boxes-dev-dvb@1.0.1052+6e5360aed3f79e9b0b4d34adaaea7b174277c4d7";
|
|
64618
64618
|
const packageVersion = typeof rawPackageVersion === "string" ? rawPackageVersion : void 0;
|
|
64619
64619
|
const gitSha = typeof rawGitSha === "string" ? rawGitSha : void 0;
|
|
64620
64620
|
const sentryRelease = typeof rawSentryRelease === "string" ? rawSentryRelease : void 0;
|
|
@@ -66631,10 +66631,18 @@ var init_desktopInitAssets = __esm({
|
|
|
66631
66631
|
}
|
|
66632
66632
|
});
|
|
66633
66633
|
|
|
66634
|
+
// ../../../../shared/devboxCore/dist/setupFinalResponsePrompt.js
|
|
66635
|
+
var init_setupFinalResponsePrompt = __esm({
|
|
66636
|
+
"../../../../shared/devboxCore/dist/setupFinalResponsePrompt.js"() {
|
|
66637
|
+
"use strict";
|
|
66638
|
+
}
|
|
66639
|
+
});
|
|
66640
|
+
|
|
66634
66641
|
// ../../../../shared/devboxCore/dist/remoteSetupPrompt.js
|
|
66635
66642
|
var init_remoteSetupPrompt = __esm({
|
|
66636
66643
|
"../../../../shared/devboxCore/dist/remoteSetupPrompt.js"() {
|
|
66637
66644
|
"use strict";
|
|
66645
|
+
init_setupFinalResponsePrompt();
|
|
66638
66646
|
}
|
|
66639
66647
|
});
|
|
66640
66648
|
|
|
@@ -66813,7 +66821,7 @@ var init_packageVersion = __esm({
|
|
|
66813
66821
|
return path8.join(process.cwd(), "dvb");
|
|
66814
66822
|
};
|
|
66815
66823
|
readEmbeddedPackageVersion = () => {
|
|
66816
|
-
const raw = "1.0.
|
|
66824
|
+
const raw = "1.0.1052";
|
|
66817
66825
|
return trimVersion(raw);
|
|
66818
66826
|
};
|
|
66819
66827
|
readNearestPackageMetadata = (basePath) => {
|
|
@@ -79960,4 +79968,4 @@ smol-toml/dist/index.js:
|
|
|
79960
79968
|
*)
|
|
79961
79969
|
*/
|
|
79962
79970
|
|
|
79963
|
-
//# debugId=
|
|
79971
|
+
//# debugId=a9afcb43-4806-5154-9842-36529ed47771
|
|
@@ -4,9 +4,11 @@ The boxes.dev CLI is `dvb`. It is useful when you prefer terminal workflows,
|
|
|
4
4
|
need direct shell access, want to copy a file into a machine, or want to manage
|
|
5
5
|
machine lifecycle from scripts.
|
|
6
6
|
|
|
7
|
-
|
|
8
|
-
|
|
9
|
-
|
|
7
|
+
Most new users set up their first project by giving the setup prompt from the
|
|
8
|
+
boxes.dev website to a coding agent on their computer, which installs and
|
|
9
|
+
signs in the CLI (see Set Up A Project). CLI sign-in is separate from desktop
|
|
10
|
+
sign-in: if you sign in on desktop and later run CLI commands, the CLI may ask
|
|
11
|
+
you to sign in again.
|
|
10
12
|
|
|
11
13
|
For exact flags, run `dvb --help` or `dvb <command> --help`.
|
|
12
14
|
|
|
@@ -53,10 +55,11 @@ Never install or run `dvb` on a boxes.dev machine: it can destabilize or
|
|
|
53
55
|
permanently break that machine, and boxes.dev is not responsible for recovering
|
|
54
56
|
a machine knowingly modified this way.
|
|
55
57
|
|
|
56
|
-
Production installs
|
|
58
|
+
Production installs of the standalone build, which includes its own runtime,
|
|
59
|
+
for macOS or Linux on x64 or arm64:
|
|
57
60
|
|
|
58
61
|
```bash
|
|
59
|
-
npm install -g @boxes-dev/
|
|
62
|
+
npm install -g @boxes-dev/cli
|
|
60
63
|
```
|
|
61
64
|
|
|
62
65
|
or:
|
|
@@ -65,6 +68,9 @@ or:
|
|
|
65
68
|
curl -fsSL https://boxes.dev/install.sh | sh
|
|
66
69
|
```
|
|
67
70
|
|
|
71
|
+
With Node.js 22 or newer, `npm install -g @boxes-dev/dvb` installs a build
|
|
72
|
+
that uses the local Node.js runtime instead.
|
|
73
|
+
|
|
68
74
|
## Sign In And Agent Setup
|
|
69
75
|
|
|
70
76
|
Use:
|
|
@@ -75,7 +81,9 @@ dvb setup
|
|
|
75
81
|
|
|
76
82
|
This signs the CLI into boxes.dev and configures coding agents for CLI-created
|
|
77
83
|
or CLI-managed work. It can also be used later to repair or update CLI agent
|
|
78
|
-
auth.
|
|
84
|
+
auth. Someone setting up their first project doesn't need it: the setup
|
|
85
|
+
prompt signs the CLI in, and `dvb agent-init accounts` connects their coding
|
|
86
|
+
agents.
|
|
79
87
|
|
|
80
88
|
Use `dvb setup --agents` when you only need to revisit coding-agent auth. For
|
|
81
89
|
Codex auth on managed machines, use this command on your own computer instead of
|
|
@@ -92,14 +100,18 @@ Useful account commands:
|
|
|
92
100
|
|
|
93
101
|
## Set Up A Project
|
|
94
102
|
|
|
95
|
-
The
|
|
96
|
-
|
|
103
|
+
The default project setup path has a coding agent working in the local
|
|
104
|
+
repository run:
|
|
97
105
|
|
|
98
106
|
```bash
|
|
99
107
|
dvb agent-init
|
|
100
108
|
```
|
|
101
109
|
|
|
102
|
-
The
|
|
110
|
+
The setup prompt on the website's **Get started** page adds a login code
|
|
111
|
+
(`dvb agent-init --login-code <code>`) so the CLI signs in without a separate
|
|
112
|
+
browser sign-in. The command gives the agent a read-only investigation and
|
|
113
|
+
planning workflow, and `dvb agent-init accounts` opens a browser page where
|
|
114
|
+
the user connects Codex or Claude Code before launch.
|
|
103
115
|
The agent prepares a manifest with you, checks it, and asks for explicit
|
|
104
116
|
approval before `dvb agent-init run` uploads files or creates a Template box.
|
|
105
117
|
The current version-3 manifest also lets the agent design startup and teardown
|
|
@@ -341,8 +341,8 @@ terminal bell can request attention without adding an unread thread.
|
|
|
341
341
|
## Search Your Threads
|
|
342
342
|
|
|
343
343
|
Press **Cmd+F** (Ctrl+F), or choose the search button (a magnifying glass)
|
|
344
|
-
beside the back button, to open thread search. It searches the
|
|
345
|
-
own Codex and Claude threads across all of your projects, including archived
|
|
344
|
+
beside the back button, to open thread search. It searches the titles and
|
|
345
|
+
text of your own Codex and Claude threads across all of your projects, including archived
|
|
346
346
|
threads, threads on sleeping machines,
|
|
347
347
|
and threads kept in cold storage. Searching never wakes a machine.
|
|
348
348
|
|
|
@@ -351,17 +351,21 @@ words in that order. Straight and curly double quotes work. Capitalization
|
|
|
351
351
|
and punctuation do not need to match; words outside quotes help pick the best
|
|
352
352
|
matches.
|
|
353
353
|
|
|
354
|
-
|
|
355
|
-
updates, tool activity and output, and attachments are not included. A
|
|
356
|
-
|
|
354
|
+
Message search covers your messages and each agent's final replies. Progress
|
|
355
|
+
updates, tool activity and output, and attachments are not included. A
|
|
356
|
+
thread's new title is searchable as soon as it changes. A new message becomes
|
|
357
|
+
searchable a few seconds after the agent's reply finishes,
|
|
357
358
|
and the thread's earlier messages stay searchable while the agent is still
|
|
358
359
|
working. A deleted thread leaves the results as soon as you delete it.
|
|
359
360
|
|
|
360
|
-
Results show one row per thread for up to 30 threads,
|
|
361
|
-
|
|
362
|
-
|
|
363
|
-
|
|
364
|
-
|
|
361
|
+
Results show one row per thread for up to 30 threads, best match first. A
|
|
362
|
+
thread ranks higher when its title contains every search word, when several
|
|
363
|
+
of its messages match, and when it was active recently. The last word also
|
|
364
|
+
matches the start of a title word, so titles match while you type. Each row
|
|
365
|
+
shows the thread title, how long ago the thread was last active, and a
|
|
366
|
+
highlighted excerpt labeled with who wrote the matching message. A thread
|
|
367
|
+
found by its title alone shows no excerpt. Archived threads have an archive
|
|
368
|
+
icon, and each row names its project when the results come from more than one project. Use
|
|
365
369
|
the arrow keys and **Enter**, or click a row, to open that thread in its
|
|
366
370
|
project.
|
|
367
371
|
|
|
@@ -56,10 +56,11 @@ twice.
|
|
|
56
56
|
## Thread List
|
|
57
57
|
|
|
58
58
|
Tap **Search messages in all threads** above the list on Home or in a project to
|
|
59
|
-
search your messages and the final replies in your own Codex and
|
|
60
|
-
threads across all projects. Results include archived and cold-stored
|
|
61
|
-
conversations
|
|
62
|
-
|
|
59
|
+
search the titles, your messages, and the final replies in your own Codex and
|
|
60
|
+
Claude threads across all projects. Results include archived and cold-stored
|
|
61
|
+
conversations and list the best matches first, favoring threads whose title
|
|
62
|
+
contains every search word and threads that were active recently. Message
|
|
63
|
+
matches show highlighted excerpts. Tap a result to open the thread. Searching does not wake a machine.
|
|
63
64
|
Team admins can also find matches from their Team Template editing threads;
|
|
64
65
|
open those threads in the desktop app.
|
|
65
66
|
|
|
@@ -312,10 +313,10 @@ Mobile settings include:
|
|
|
312
313
|
in the browser.
|
|
313
314
|
|
|
314
315
|
Someone opening your invite link can sign up with Google in their phone
|
|
315
|
-
browser. After signing up on a phone, they will see that
|
|
316
|
-
|
|
317
|
-
the
|
|
318
|
-
|
|
316
|
+
browser. After signing up on a phone, they will see that their coding agent
|
|
317
|
+
will set up the project on the computer where their code lives, with actions
|
|
318
|
+
to email, copy, or share a link to the setup page. Signing up on a computer
|
|
319
|
+
continues straight to the web app's **Get started** page.
|
|
319
320
|
|
|
320
321
|
Thread text size defaults to **Medium** for transcript and message text on this
|
|
321
322
|
device. Choose **Compact**, **Medium**, or **Large** in **Settings → Appearance**.
|
|
@@ -875,7 +875,8 @@ They may lag active work and shorten long messages. They do not wake boxes,
|
|
|
875
875
|
mark threads read, claim links, or expose full tool logs. Without `--scope`,
|
|
876
876
|
the existing `list` and `read` commands still select delegated children only.
|
|
877
877
|
|
|
878
|
-
To find your own threads by what was said in them, search
|
|
878
|
+
To find your own threads by title or by what was said in them, search
|
|
879
|
+
instead of listing:
|
|
879
880
|
|
|
880
881
|
```bash
|
|
881
882
|
dvb-onbox threads search --scope user --query "flaky deploy" --json
|
|
@@ -884,8 +885,8 @@ dvb-onbox threads read --scope user --thread <id> --cursor <readCursor> --turns
|
|
|
884
885
|
```
|
|
885
886
|
|
|
886
887
|
Search uses the same index as thread search in the desktop and mobile apps. It
|
|
887
|
-
covers your messages and the agents' final replies in your
|
|
888
|
-
Claude threads, including archived ones. Commentary, tool activity,
|
|
888
|
+
covers thread titles, your messages, and the agents' final replies in your
|
|
889
|
+
own Codex and Claude threads, including archived ones. Commentary, tool activity,
|
|
889
890
|
attachments, and Team Template editing threads are not included. It accepts only the `project` and `user` scopes,
|
|
890
891
|
which need the same permission levels as listing them. Put a phrase in double
|
|
891
892
|
quotes to require those words together in that order.
|
|
@@ -897,6 +898,8 @@ conversation at the match, run `threads read` with the same scope, the
|
|
|
897
898
|
thread's `id`, and `readCursor` as `--cursor`: the page ends with the matching
|
|
898
899
|
turn, and its returned cursor continues to older messages. If the thread's history has been rebuilt since it was
|
|
899
900
|
indexed, the read reports `cursor_expired`; read it without a cursor instead.
|
|
901
|
+
When only the thread's title matched, those four `match` fields are null, so
|
|
902
|
+
read that thread without a cursor.
|
|
900
903
|
A new message becomes searchable a few seconds after the agent's reply
|
|
901
904
|
finishes.
|
|
902
905
|
|
|
@@ -19,32 +19,45 @@ through a guided wizard. Both upload local project state and start a setup
|
|
|
19
19
|
thread on the Template box. That thread applies the setup plan, installs
|
|
20
20
|
missing project dependencies, checks important app entrypoints, and writes a
|
|
21
21
|
setup summary or follow-up list when it finishes.
|
|
22
|
+
|
|
23
|
+
The setup thread's final reply explains what was validated and introduces the
|
|
24
|
+
Template box, snapshots, **New devbox + thread**, and additional threads on an
|
|
25
|
+
existing devbox. It also explains how to get started with Slack, Linear,
|
|
26
|
+
automations, and agent delegation and messaging. You can keep talking in that
|
|
27
|
+
thread for help with setup or using boxes.dev. The reply can arrive before
|
|
28
|
+
boxes.dev finishes saving the first snapshot; wait for setup to finish before
|
|
29
|
+
starting your first devbox.
|
|
30
|
+
|
|
22
31
|
**Create from GitHub** is the fallback for a repository the user does not have
|
|
23
32
|
locally: it clones one or more selected repositories into a new Template box,
|
|
24
33
|
without env files, secrets, or untracked local work, and leaves environment
|
|
25
34
|
setup to the user.
|
|
26
35
|
|
|
27
|
-
Signing in on the website before any project exists lands on
|
|
28
|
-
|
|
29
|
-
|
|
30
|
-
|
|
31
|
-
|
|
32
|
-
|
|
33
|
-
|
|
34
|
-
|
|
35
|
-
|
|
36
|
-
|
|
37
|
-
|
|
38
|
-
**
|
|
39
|
-
**Download for Mac
|
|
40
|
-
|
|
41
|
-
|
|
42
|
-
|
|
43
|
-
|
|
44
|
-
|
|
45
|
-
|
|
46
|
-
|
|
47
|
-
|
|
36
|
+
Signing in on the website before any project exists lands on **Get started**,
|
|
37
|
+
which has three steps:
|
|
38
|
+
|
|
39
|
+
1. **Connect GitHub**, which is optional and shows as done once GitHub is
|
|
40
|
+
connected.
|
|
41
|
+
2. **Set up your project with your coding agent**: a ready-made prompt to
|
|
42
|
+
paste into Codex or Claude Code in the project folder, which has the agent
|
|
43
|
+
run the agent-driven terminal setup. The prompt includes a login code that
|
|
44
|
+
signs the agent's CLI in to the same boxes.dev account. Each code works
|
|
45
|
+
once and expires within 30 minutes, and the page always shows a current
|
|
46
|
+
one.
|
|
47
|
+
3. **Get the desktop app**: the agent gives the user the Mac app link once
|
|
48
|
+
setup starts, and **Download for Mac now** is available right away. On
|
|
49
|
+
Windows and Linux browsers that boxes.dev can confidently identify, this
|
|
50
|
+
step says the desktop app is Mac-only and links to the mobile app instead.
|
|
51
|
+
|
|
52
|
+
On a phone, the second step becomes **Continue on your computer**, with
|
|
53
|
+
actions to email, copy, or share a link to the page, and the desktop step is
|
|
54
|
+
left out. The first project is set up by the coding agent; **Create from
|
|
55
|
+
GitHub** is offered when the user adds a later project.
|
|
56
|
+
|
|
57
|
+
When a user copies the prompt, the page confirms the copy and can show when
|
|
58
|
+
the CLI connects, prepares the project, waits for launch approval, and starts
|
|
59
|
+
launching. The coding agent still owns the setup work, and `dvb agent-init
|
|
60
|
+
status` remains the source for its exact next action.
|
|
48
61
|
|
|
49
62
|
After setup, the website's **Projects** page lists projects and their last-used
|
|
50
63
|
activity. Choose a project name or **Open in desktop app** to continue in the
|
|
@@ -272,10 +285,42 @@ client remains preferred. Missing database variables, authentication problems,
|
|
|
272
285
|
missing MySQL clients, and PostgreSQL servers newer than the available client
|
|
273
286
|
are reported before the full bundle is built.
|
|
274
287
|
|
|
275
|
-
The
|
|
276
|
-
|
|
277
|
-
|
|
278
|
-
|
|
288
|
+
The prompt from **Get started**, the website's **New project** page, or the
|
|
289
|
+
desktop app's **Set up with your coding agent** card has the agent run `dvb
|
|
290
|
+
agent-init --login-code <code>`, which signs the CLI in without another
|
|
291
|
+
browser sign-in. If the code has expired or was already used, the CLI keeps an
|
|
292
|
+
existing CLI sign-in when it has one. Otherwise, `dvb agent-init login` opens
|
|
293
|
+
Google sign-in in the browser, prints the link, and waits for the user to
|
|
294
|
+
finish. Over SSH,
|
|
295
|
+
the browser can't reach the CLI, so the agent asks the user to copy a fresh
|
|
296
|
+
prompt instead.
|
|
297
|
+
|
|
298
|
+
Next, `dvb agent-init accounts` opens **Connect your accounts** in the
|
|
299
|
+
browser. There the user connects Codex, Claude Code, or both, and can connect
|
|
300
|
+
GitHub and Slack. Codex and Claude Code use their normal browser sign-in,
|
|
301
|
+
which returns to the CLI on the user's computer, and **Use an API key** saves
|
|
302
|
+
a key instead. **Done** becomes available once a coding agent is connected,
|
|
303
|
+
and the command waits until the user chooses it. Over SSH, the command prints
|
|
304
|
+
a link for the user to open and exits: on that page, Codex shows a one-time
|
|
305
|
+
code to enter on ChatGPT, Claude Code asks for the code Claude shows, and the
|
|
306
|
+
user tells the agent when they're done. **Use a code instead** switches a
|
|
307
|
+
local page to the same code flows for setups where browser sign-in can't
|
|
308
|
+
reach the CLI, such as a container. `dvb agent-init check` requires at least
|
|
309
|
+
one connected coding agent.
|
|
310
|
+
|
|
311
|
+
Once the setup thread starts on the Template box, `dvb agent-init run` tells
|
|
312
|
+
the agent where the user can follow it. On a Mac with the desktop app
|
|
313
|
+
installed, the agent offers to open it with `dvb agent-init open-desktop`,
|
|
314
|
+
which opens the Template box on the setup thread. On a Mac without the app,
|
|
315
|
+
the agent gives the download link, and on other computers or over SSH, it
|
|
316
|
+
points to the mobile app. When setup finishes, the agent lists the same
|
|
317
|
+
choices along with `dvb agents <project>`, which opens the Template box's
|
|
318
|
+
agent threads in the terminal (`--workspace` keeps the thread list beside the
|
|
319
|
+
open agent).
|
|
320
|
+
|
|
321
|
+
Launch requires the same billing activation as desktop setup. The machine
|
|
322
|
+
created this way is a normal Template box: it appears in the desktop app,
|
|
323
|
+
supports devboxes, and behaves identically from then on.
|
|
279
324
|
|
|
280
325
|
## Agent Auth
|
|
281
326
|
|
|
@@ -385,13 +430,14 @@ creation until a project is deleted or billing changes allow another project.
|
|
|
385
430
|
|
|
386
431
|
## Create From GitHub
|
|
387
432
|
|
|
388
|
-
|
|
389
|
-
|
|
390
|
-
|
|
391
|
-
|
|
392
|
-
|
|
393
|
-
first-project flow
|
|
394
|
-
copying their local development
|
|
433
|
+
After a user has set up their first project, **Create from GitHub** is
|
|
434
|
+
available when they add another one: under **New project** on the logged-in
|
|
435
|
+
website, including from a mobile browser, and under **Other setup options** in
|
|
436
|
+
the desktop app, marked **Manual setup** because it suits only repositories
|
|
437
|
+
that need little setup. Choose it and connect a GitHub account. The website's
|
|
438
|
+
**Get started** page and the desktop first-project flow leave this option out
|
|
439
|
+
so they can guide new users through copying their local development
|
|
440
|
+
environment instead.
|
|
395
441
|
Connecting first authorizes the user's GitHub identity. If the boxes.dev GitHub
|
|
396
442
|
App is not installed yet, setup then makes installation the required next step:
|
|
397
443
|
choose the personal account or organization that owns the repositories and
|
|
@@ -838,10 +884,10 @@ support.
|
|
|
838
884
|
|
|
839
885
|
To upload another local project, use **New project...** in the titlebar project
|
|
840
886
|
selector or **File > New Project...** in the desktop app. On the website,
|
|
841
|
-
**New project**
|
|
842
|
-
|
|
843
|
-
|
|
844
|
-
|
|
887
|
+
**New project** offers the coding-agent prompt and **Create from GitHub**. For
|
|
888
|
+
a repository that is not on the user's computer, **Create from GitHub** clones
|
|
889
|
+
another GitHub-backed ordinary project instead, with the same manual
|
|
890
|
+
environment setup afterwards. Each ordinary project made through
|
|
845
891
|
these paths gets its own setup flow and Template box. A Team Template's
|
|
846
892
|
**Member projects** path is the exception: it creates an independent project
|
|
847
893
|
without a personal Template box and uses the Team Template's current saved
|
|
@@ -7,8 +7,9 @@ teammate's shared threads or Team Template administration.
|
|
|
7
7
|
|
|
8
8
|
## Connect and choose access
|
|
9
9
|
|
|
10
|
-
Add the boxes.dev plugin or remote MCP connection
|
|
11
|
-
|
|
10
|
+
Add the boxes.dev plugin or a remote MCP connection to
|
|
11
|
+
`https://api.boxes.dev/mcp` in your assistant, then follow its authorization
|
|
12
|
+
link. Sign in to boxes.dev and check the requesting
|
|
12
13
|
domain, return address, account and requested permissions. A client name marked unverified is
|
|
13
14
|
supplied by the client, not an endorsement from boxes.dev.
|
|
14
15
|
|
|
@@ -87,11 +87,13 @@ the main thread list alongside other devbox threads.
|
|
|
87
87
|
|
|
88
88
|
To start your own thread, mention `@boxes.dev` and write your request. Under
|
|
89
89
|
**Who else can trigger a new thread?**, choose **No one** (the default),
|
|
90
|
-
**Teammates I choose**,
|
|
91
|
-
belongs to you: teammates cannot give themselves
|
|
92
|
-
be an active member of the same boxes.dev team
|
|
93
|
-
connected Slack workspace. They can start a
|
|
94
|
-
mentioning `@boxes.dev @YourName`, followed by
|
|
90
|
+
**Teammates I choose**, **Any teammate with Slack connected**, or **Teammates
|
|
91
|
+
and bots**. This setting belongs to you: teammates cannot give themselves
|
|
92
|
+
access. Anyone you allow must be an active member of the same boxes.dev team
|
|
93
|
+
with a linked identity in the connected Slack workspace. They can start a
|
|
94
|
+
thread in your workspace by mentioning `@boxes.dev @YourName`, followed by
|
|
95
|
+
their request. **Teammates and bots** also lets bots in the connected Slack
|
|
96
|
+
workspace start threads the same way; see [Requests From Bots](#requests-from-bots).
|
|
95
97
|
|
|
96
98
|
## Create A Slack Named Command Automation
|
|
97
99
|
|
|
@@ -120,7 +122,9 @@ shared with another organization is always a choice you make. When you choose
|
|
|
120
122
|
and a shared channel is marked **External** there.
|
|
121
123
|
|
|
122
124
|
For named commands, choose who can run it. The owner can always run it; you can
|
|
123
|
-
also allow chosen teammates or any teammate with Slack connected.
|
|
125
|
+
also allow chosen teammates or any teammate with Slack connected. **Me,
|
|
126
|
+
teammates, and bots** allows any teammate with Slack connected plus bots in the
|
|
127
|
+
connected Slack workspace; see [Requests From Bots](#requests-from-bots).
|
|
124
128
|
|
|
125
129
|
## Running From Slack
|
|
126
130
|
|
|
@@ -175,6 +179,41 @@ agent's final answer back into the same Slack thread or DM.
|
|
|
175
179
|
To return to the original Slack conversation from the desktop workbench, click
|
|
176
180
|
the Slack icon beside the thread title. Hover over it to see **Open Slack thread**.
|
|
177
181
|
|
|
182
|
+
### Requests From Bots
|
|
183
|
+
|
|
184
|
+
Bots and apps installed in the connected Slack workspace, such as a signup or
|
|
185
|
+
alerting bot, can start an automation whose access setting is **Me, teammates,
|
|
186
|
+
and bots** (named commands) or **Teammates and bots** (the default receiver).
|
|
187
|
+
Every other setting ignores bots.
|
|
188
|
+
|
|
189
|
+
A bot has no boxes.dev account, so its message has to name the owner:
|
|
190
|
+
|
|
191
|
+
- For a named command, the bot uses the full command with the owner's name,
|
|
192
|
+
such as `@boxes.dev !ananya/onboarding New signup: sam@example.com`. The
|
|
193
|
+
automation editor shows the exact command. A bot's `!onboarding` without the
|
|
194
|
+
owner's name, or a plain `@boxes.dev` request, does nothing.
|
|
195
|
+
- For a default receiver, the bot mentions the owner after `@boxes.dev`, as a
|
|
196
|
+
teammate would: `@boxes.dev @Ananya <request>`.
|
|
197
|
+
|
|
198
|
+
A bot that posts through the Slack API writes each mention as `<@MEMBER_ID>`
|
|
199
|
+
using the Slack member IDs of the boxes.dev app and the owner.
|
|
200
|
+
|
|
201
|
+
The run belongs to the automation owner and uses the owner's project, devbox,
|
|
202
|
+
credentials, and usage. The agent is told that a Slack bot sent the request
|
|
203
|
+
and that instructions inside bot messages can come from people outside the
|
|
204
|
+
team. Anyone who can make an allowed bot post in Slack, for example by
|
|
205
|
+
submitting a form the bot relays, can send requests with the owner's access,
|
|
206
|
+
so allow bots only on automations you are comfortable exposing that way.
|
|
207
|
+
|
|
208
|
+
boxes.dev never starts work from its own messages, deleted bots, or bots that
|
|
209
|
+
belong to another organization in a Slack Connect channel. The location
|
|
210
|
+
setting still applies. When boxes.dev does not accept a bot's message, it
|
|
211
|
+
posts no help or rejection reply. Once a bot starts a run, started messages
|
|
212
|
+
and final replies follow the automation's activity settings, and the owner
|
|
213
|
+
does not get the teammate DM. An allowed bot can send follow-ups in the linked
|
|
214
|
+
thread by mentioning `@boxes.dev` again, and boxes.dev replies to those
|
|
215
|
+
follow-ups as it does for people. Files that bots post are never imported.
|
|
216
|
+
|
|
178
217
|
## Choose What Appears In Slack
|
|
179
218
|
|
|
180
219
|
In the automation editor, **What should boxes.dev post in the Slack thread?**
|
|
@@ -188,13 +227,23 @@ checkboxes. For quiet customer channels, choose **None** under **Slack Connect**
|
|
|
188
227
|
are enabled. Leave it off for a short status and link. It starts off for Slack
|
|
189
228
|
Connect. Turning off the parent reply keeps the full-response choice for later.
|
|
190
229
|
|
|
230
|
+
**Messages the agent is asked to post** lets the agent post its own messages in
|
|
231
|
+
the Slack thread with `boxes-slack reply`, such as updates during long work.
|
|
232
|
+
It starts off for both audiences and is separate from the end-of-run reply
|
|
233
|
+
rows. The agent posts only when the request or the automation's instructions
|
|
234
|
+
ask it to, and it does not repeat a final reply that boxes.dev already posts.
|
|
235
|
+
This matters for threads that keep working after the Slack request, because
|
|
236
|
+
boxes.dev posts automatic replies only for turns that start from Slack.
|
|
237
|
+
|
|
191
238
|
The location menu still decides where new runs can start. The Slack Connect
|
|
192
239
|
column appears when that location can include shared channels; hiding the
|
|
193
240
|
column keeps its saved choices. Attachment warnings can remain on even when
|
|
194
241
|
started messages or follow-up confirmations are off.
|
|
195
242
|
|
|
196
243
|
Changes apply to new Slack threads. Existing linked threads keep the choices
|
|
197
|
-
they started with
|
|
244
|
+
they started with, except for agent messages: the current setting applies each
|
|
245
|
+
time an agent posts, so turning it off also stops agents in existing threads.
|
|
246
|
+
These settings control automatic activity for this
|
|
198
247
|
automation; help and replies before boxes.dev can identify an automation are
|
|
199
248
|
separate. Turning activity off does not send replacement DMs. The existing DM
|
|
200
249
|
to an owner when a teammate starts work in their workspace is unchanged.
|
|
@@ -207,10 +256,10 @@ mention stay in Slack and are not sent to the agent.
|
|
|
207
256
|
|
|
208
257
|
Anyone allowed to run the automation can send follow-ups in its linked Slack
|
|
209
258
|
threads, including threads the owner started. Each follow-up reaches the agent
|
|
210
|
-
with a note naming its sender
|
|
211
|
-
|
|
212
|
-
|
|
213
|
-
credentials out of its replies. A run a teammate starts carries the same note
|
|
259
|
+
with a note naming its sender; for a bot, the note says a bot sent it. When the
|
|
260
|
+
sender is a teammate or a bot, that note also names the project owner, says the
|
|
261
|
+
work runs in the owner's project with the owner's credentials, and asks the
|
|
262
|
+
agent to keep the owner's secrets and credentials out of its replies. A run a teammate starts carries the same note
|
|
214
263
|
in its first prompt.
|
|
215
264
|
|
|
216
265
|
To start a new teammate-owned run from an already linked Slack thread,
|
|
@@ -287,9 +336,11 @@ current Slack integration. A member of another organization in a shared channel
|
|
|
287
336
|
cannot start a thread, send a follow-up, be assigned work, or have their files
|
|
288
337
|
imported.
|
|
289
338
|
|
|
290
|
-
|
|
291
|
-
|
|
292
|
-
|
|
339
|
+
In Slack-triggered runs, the agent can read the triggering Slack thread and
|
|
340
|
+
direct Slack links the user provides. When **Messages the agent is asked to
|
|
341
|
+
post** is on for that conversation, it can also post to the triggering Slack
|
|
342
|
+
thread, and nowhere else. It does not receive Slack tokens and cannot browse
|
|
343
|
+
the workspace.
|
|
293
344
|
|
|
294
345
|
## Troubleshooting
|
|
295
346
|
|
|
@@ -89,11 +89,23 @@ 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
|
-
**Manage team**. The project-selector submenu
|
|
93
|
-
non-archived template and includes **New Team
|
|
94
|
-
Templates**. The collection shows each named
|
|
95
|
-
its description, machine size, latest saved
|
|
96
|
-
admins can also reveal archived templates
|
|
92
|
+
from **Manage team** → **Manage Team Templates**. The project-selector submenu
|
|
93
|
+
links directly to each non-archived template and includes **New Team
|
|
94
|
+
Template...** and **View all Team Templates**. The collection shows each named
|
|
95
|
+
template separately, including its description, machine size, latest saved
|
|
96
|
+
version, and editing status. Team admins can also reveal archived templates
|
|
97
|
+
here.
|
|
98
|
+
|
|
99
|
+
The collection and each template's detail page also work in a web browser, so
|
|
100
|
+
an admin can keep a template open beside the desktop workbench. In the desktop
|
|
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 Settings, where
|
|
103
|
+
**Manage Team Templates** opens the collection. A browser can change everything
|
|
104
|
+
on the detail page except the editing session itself: creating a template,
|
|
105
|
+
GitHub setup, **Take control**, continuing an editing session, and **Resolve**
|
|
106
|
+
all need the desktop app on a Mac. In their place, a browser on a Mac shows
|
|
107
|
+
**Open in desktop app**, which opens the same template in the desktop app;
|
|
108
|
+
phones, tablets, Windows, and Linux show a note instead.
|
|
97
109
|
|
|
98
110
|
**Project settings** for a project made from a Team Template names that
|
|
99
111
|
template. A managed project shows the template it uses, and an independent
|
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.1052",
|
|
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",
|
|
@@ -79,5 +79,5 @@
|
|
|
79
79
|
"e2b": "^2.18.0",
|
|
80
80
|
"ink-testing-library": "^4.0.0"
|
|
81
81
|
},
|
|
82
|
-
"devboxReleasedAt": "2026-10-
|
|
82
|
+
"devboxReleasedAt": "2026-10-03T19:33:55Z"
|
|
83
83
|
}
|