@boxes-dev/dvb-runtime 1.0.1026 → 1.0.1028
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 +5 -3
- package/dist/agent-init-guides/git-ssh.md +4 -3
- package/dist/bin/dvb.mjs +250 -47
- package/dist/bin/dvbd.mjs +6 -6
- package/dist/product-docs/references/cli.md +3 -1
- package/dist/product-docs/references/desktop-workbench.md +28 -4
- package/dist/product-docs/references/fork-workflows.md +11 -0
- package/dist/product-docs/references/getting-started.md +2 -1
- package/dist/product-docs/references/linear.md +3 -1
- package/dist/product-docs/references/managed-environment-files.md +21 -3
- package/dist/product-docs/references/mobile.md +51 -5
- package/dist/product-docs/references/onbox-agent-tools.md +133 -13
- package/dist/product-docs/references/project-setup.md +37 -15
- package/dist/product-docs/references/slack.md +16 -4
- package/dist/product-docs/references/threads-and-agents.md +2 -1
- package/dist/product-docs/references/troubleshooting.md +6 -2
- package/package.json +2 -2
package/dist/bin/dvbd.mjs
CHANGED
|
@@ -96328,8 +96328,8 @@ var init_otel = __esm({
|
|
|
96328
96328
|
return trimmed && trimmed.length > 0 ? trimmed : void 0;
|
|
96329
96329
|
};
|
|
96330
96330
|
readBuildMetadata = () => {
|
|
96331
|
-
const rawPackageVersion = "1.0.
|
|
96332
|
-
const rawGitSha = "
|
|
96331
|
+
const rawPackageVersion = "1.0.1028";
|
|
96332
|
+
const rawGitSha = "ecb8f0fdfaad3f4c2d389ec6fc4ee49de0b175d9";
|
|
96333
96333
|
const packageVersion = typeof rawPackageVersion === "string" ? rawPackageVersion : void 0;
|
|
96334
96334
|
const gitSha = typeof rawGitSha === "string" ? rawGitSha : void 0;
|
|
96335
96335
|
return { packageVersion, gitSha };
|
|
@@ -128624,9 +128624,9 @@ var init_sentry = __esm({
|
|
|
128624
128624
|
uncaughtExceptionMonitorInstalled = false;
|
|
128625
128625
|
currentDevboxSentryUser = null;
|
|
128626
128626
|
readBuildMetadata2 = () => {
|
|
128627
|
-
const rawPackageVersion = "1.0.
|
|
128628
|
-
const rawGitSha = "
|
|
128629
|
-
const rawSentryRelease = "boxes-dev-dvb@1.0.
|
|
128627
|
+
const rawPackageVersion = "1.0.1028";
|
|
128628
|
+
const rawGitSha = "ecb8f0fdfaad3f4c2d389ec6fc4ee49de0b175d9";
|
|
128629
|
+
const rawSentryRelease = "boxes-dev-dvb@1.0.1028+ecb8f0fdfaad3f4c2d389ec6fc4ee49de0b175d9";
|
|
128630
128630
|
const packageVersion = typeof rawPackageVersion === "string" ? rawPackageVersion : void 0;
|
|
128631
128631
|
const gitSha = typeof rawGitSha === "string" ? rawGitSha : void 0;
|
|
128632
128632
|
const sentryRelease = typeof rawSentryRelease === "string" ? rawSentryRelease : void 0;
|
|
@@ -130826,7 +130826,7 @@ var init_packageVersion = __esm({
|
|
|
130826
130826
|
return path8.join(process.cwd(), "dvb");
|
|
130827
130827
|
};
|
|
130828
130828
|
readEmbeddedPackageVersion = () => {
|
|
130829
|
-
const raw = "1.0.
|
|
130829
|
+
const raw = "1.0.1028";
|
|
130830
130830
|
return trimVersion(raw);
|
|
130831
130831
|
};
|
|
130832
130832
|
readNearestPackageMetadata = (basePath) => {
|
|
@@ -271,7 +271,9 @@ preview clears unread only after the exact ready content is rendered. Loading,
|
|
|
271
271
|
unavailable, and stale content do not clear it.
|
|
272
272
|
|
|
273
273
|
Use `p` to pin or unpin an eligible Template-box thread or devbox anchor, `r`
|
|
274
|
-
to rename a thread, and `x` to archive or restore it. On
|
|
274
|
+
to rename a thread, and `x` to archive or restore it. On a devbox group row,
|
|
275
|
+
`r` renames the devbox instead, and empty input returns the group to its first
|
|
276
|
+
thread's title. On an archived
|
|
275
277
|
cold-storage thread, `x` opens the available restore choice. Ordinary projects
|
|
276
278
|
can use the current Template box or a new devbox; Team Template member projects
|
|
277
279
|
restore only to a new devbox. Empty rename input
|
|
@@ -35,7 +35,31 @@ Git/Review, and Browser. The app menu can show or hide the Agent pane. At least
|
|
|
35
35
|
one main area stays visible. A new devbox starts with no aux pane open. The
|
|
36
36
|
Template box and each devbox then remember their last aux-pane choice
|
|
37
37
|
independently, so returning to a runtime restores its previous pane. Pane widths
|
|
38
|
-
can be resized.
|
|
38
|
+
can be resized. Showing Terminal reattaches the runtime's open terminal
|
|
39
|
+
sessions, or starts one if it has none, and closing the last terminal tab
|
|
40
|
+
closes the pane.
|
|
41
|
+
|
|
42
|
+
## Accounts
|
|
43
|
+
|
|
44
|
+
The desktop app can stay signed in to more than one boxes.dev account, such as
|
|
45
|
+
a personal account and a work account. Open the account menu at the bottom of
|
|
46
|
+
the left pane to see the other signed-in accounts, and click one to switch. The
|
|
47
|
+
workbench reloads as that account and opens its last project; there is no new
|
|
48
|
+
sign-in. **Add another account** opens Google sign-in in your browser while the
|
|
49
|
+
current account stays open, then switches to the new account once sign-in
|
|
50
|
+
finishes.
|
|
51
|
+
|
|
52
|
+
**Log out** (or **Sign Out** in the app menu) signs out only the current
|
|
53
|
+
account. If another account is still signed in, the app switches to it, and
|
|
54
|
+
deleting the current account from the Account page does the same. When an
|
|
55
|
+
account's session expires, the sign-in screen offers **Continue as** buttons
|
|
56
|
+
for the accounts that are still signed in. A newly added account that has no
|
|
57
|
+
project yet opens first-run setup; the account email at the top right of the
|
|
58
|
+
setup screen offers the same switch, add, and log out choices.
|
|
59
|
+
|
|
60
|
+
Desktop notifications, the unread count, ports, and terminals follow the
|
|
61
|
+
account that is open. Switching accounts requires a current desktop app
|
|
62
|
+
version; older versions do not show the other accounts.
|
|
39
63
|
|
|
40
64
|
## Right-Click Menus
|
|
41
65
|
|
|
@@ -208,8 +232,8 @@ snapshot, repository, terminal, and power controls.
|
|
|
208
232
|
Use the terminal button in the Template box header to replace the Template box
|
|
209
233
|
page with its terminal in the main pane. While it is there, Terminal is
|
|
210
234
|
unavailable as the right-side pane, but Files, Git/Review, and Browser continue
|
|
211
|
-
to work there normally. Use the same button again
|
|
212
|
-
page.
|
|
235
|
+
to work there normally. Use the same button again, or close the last terminal
|
|
236
|
+
tab, to restore the Template box page.
|
|
213
237
|
|
|
214
238
|
Work that should not change the Template box directly should usually start on a
|
|
215
239
|
devbox. See `fork-workflows.md` for that workflow.
|
|
@@ -427,7 +451,7 @@ Invalid policy never authorizes a new path.
|
|
|
427
451
|
|
|
428
452
|
## Updates And Feedback
|
|
429
453
|
|
|
430
|
-
Open Help in the desktop sidebar, then **Help center**, for the
|
|
454
|
+
Open Help in the desktop sidebar, then **Help center**, for the public
|
|
431
455
|
human guides at `https://boxes.dev/help`. It opens in the external browser and
|
|
432
456
|
keeps the working conversation in the desktop app. The existing quick fixes
|
|
433
457
|
and Send feedback action remain in the Help dialog.
|
|
@@ -167,6 +167,17 @@ runtime state.
|
|
|
167
167
|
This is useful for asking a second question about work already in that devbox,
|
|
168
168
|
or for continuing with another agent without creating another machine.
|
|
169
169
|
|
|
170
|
+
In the thread list, a devbox with more than one thread appears as a group
|
|
171
|
+
titled with its first thread's title. To label the devbox separately, choose
|
|
172
|
+
**Rename devbox** from the group's menu in the desktop or mobile app, or press
|
|
173
|
+
`r` on the group row in `dvb agents`. Renaming the devbox does not change any
|
|
174
|
+
thread title, and renaming a thread does not change the devbox name. A named
|
|
175
|
+
devbox keeps its group row even when all but one of its threads are archived.
|
|
176
|
+
Saving an empty name returns the group to the first thread's title, and a
|
|
177
|
+
devbox with one remaining thread goes back to a single thread row. Teammates
|
|
178
|
+
who can see the devbox's threads see the same name, but only the owner can
|
|
179
|
+
rename it.
|
|
180
|
+
|
|
170
181
|
Secondary threads on a devbox can be archived without destroying the devbox. The
|
|
171
182
|
devbox row and original devbox thread still own devbox lifecycle actions;
|
|
172
183
|
archiving a secondary thread only hides that child thread from the active devbox
|
|
@@ -110,7 +110,8 @@ Use devbox threads for normal coding tasks.
|
|
|
110
110
|
|
|
111
111
|
Setup asks you to connect at least one coding agent. You can connect or repair
|
|
112
112
|
agent auth later from the desktop app. On macOS, open the boxes.dev app menu and
|
|
113
|
-
choose **Configure agents...**.
|
|
113
|
+
choose **Configure agents...**. The mobile app has the same controls under
|
|
114
|
+
**Settings → Agent accounts**.
|
|
114
115
|
|
|
115
116
|
Codex can be connected with ChatGPT login or an API key. Claude Code can be
|
|
116
117
|
connected with Claude login or an API key. Configure agents can keep multiple
|
|
@@ -61,7 +61,9 @@ Linear.
|
|
|
61
61
|
|
|
62
62
|
After the workspace is connected and your Linear identity is linked, open the
|
|
63
63
|
desktop workbench's **Integrations** section and choose **Create automation**
|
|
64
|
-
for Linear. boxes.dev creates your **Default behavior** in a paused state
|
|
64
|
+
for Linear. boxes.dev creates your **Default behavior** in a paused state,
|
|
65
|
+
using the project's new-thread agent, or the coding agent you set up if you use
|
|
66
|
+
only one, with that agent's saved model and reasoning level. Use
|
|
65
67
|
**Configure** to choose Codex or Claude Code and edit the automation prompt,
|
|
66
68
|
then choose **Activate**. The integration home also shows recent runs and one
|
|
67
69
|
clear recovery action when the workspace, identity, or default behavior needs
|
|
@@ -121,18 +121,36 @@ template does not share its value objects.
|
|
|
121
121
|
A Team Template-managed project follows the current Team Template definitions
|
|
122
122
|
and Team values. Each member's values belong only to that member's exact
|
|
123
123
|
project. Members can replace, remove, reveal, copy, or export their own project
|
|
124
|
-
values
|
|
125
|
-
|
|
124
|
+
values. Team admins cannot read member values.
|
|
125
|
+
|
|
126
|
+
A member can also add their own variables in **Project settings → Environment
|
|
127
|
+
files**: in a file the Team Template manages, or in a new file of their own
|
|
128
|
+
with **Add a file**. They reach all of that member's devboxes in the project
|
|
129
|
+
and nobody else's. When a member's file and a Team Template file use the same
|
|
130
|
+
path, both share one managed section, with the team's rows first. A member
|
|
131
|
+
cannot add a name the Team Template already sets in that file. If the team adds
|
|
132
|
+
that name later, the team's row wins and the member's variable is left out of
|
|
133
|
+
the file until the member renames or removes it. A member's own file cannot use
|
|
134
|
+
a path the Team Template uses for a member file.
|
|
126
135
|
|
|
127
136
|
If an admin changes where a Member value will be written by renaming it or
|
|
128
137
|
moving its file, boxes.dev omits the old saved value. The member must review the
|
|
129
138
|
new destination and choose **Use saved value here**, or enter a replacement.
|
|
130
139
|
Other managed values continue syncing while that one is unresolved.
|
|
131
140
|
|
|
141
|
+
## Agent Commands
|
|
142
|
+
|
|
143
|
+
Coding agents can list, set, and remove a project's variables with
|
|
144
|
+
`dvb-onbox env`, and a team admin's agent can define Team and Member values with
|
|
145
|
+
`dvb-onbox team-template env`. Agents on devboxes need a 3-hour permission for
|
|
146
|
+
their thread, and no command returns saved values. See
|
|
147
|
+
[Environment variables](onbox-agent-tools.md#environment-variables).
|
|
148
|
+
|
|
132
149
|
## Sync And Outages
|
|
133
150
|
|
|
134
151
|
Managed files reconcile when a Template box or devbox starts or wakes, when a
|
|
135
|
-
change is observed, and during periodic retry
|
|
152
|
+
saved change is observed (usually within seconds), and during a periodic retry
|
|
153
|
+
about once a minute. Changing a value does not wake a
|
|
136
154
|
paused machine. A failure in one file does not stop other files from updating.
|
|
137
155
|
|
|
138
156
|
If boxes.dev, its key service, or the network is temporarily unavailable, an
|
|
@@ -24,6 +24,16 @@ website, which works entirely from a phone.
|
|
|
24
24
|
The app remembers the last project you opened and can take you back there on the
|
|
25
25
|
next launch.
|
|
26
26
|
|
|
27
|
+
The app can stay signed in to more than one boxes.dev account. In Settings, tap
|
|
28
|
+
**Add account with Google** (or **Add account with Apple** on iPhone) to sign
|
|
29
|
+
in another account; the current account stays open until the new one is ready,
|
|
30
|
+
and closing the sign-in window changes nothing. Settings lists the other
|
|
31
|
+
signed-in accounts under **Signed in as**, and tapping one switches to it
|
|
32
|
+
without signing in again. **Sign out** signs out only the current account and
|
|
33
|
+
opens the next signed-in account, if any. If an account's session ends, the
|
|
34
|
+
sign-in screen offers **Continue as** buttons for the accounts that are still
|
|
35
|
+
signed in.
|
|
36
|
+
|
|
27
37
|
If the app cannot finish checking your account because it cannot reach
|
|
28
38
|
boxes.dev, it shows **Can’t connect** and keeps trying automatically. Restore
|
|
29
39
|
your internet connection or use **Try again**; you do not need to force-quit
|
|
@@ -176,6 +186,8 @@ at the right, matching desktop. Sleeping devboxes show a timestamp in that
|
|
|
176
186
|
space. From a devbox row or devbox group you can:
|
|
177
187
|
|
|
178
188
|
- start another thread on the same devbox;
|
|
189
|
+
- rename the devbox from its group, so the group shows that name instead of
|
|
190
|
+
its first thread's title;
|
|
179
191
|
- pin or unpin the devbox;
|
|
180
192
|
- put the devbox to sleep when it is idle;
|
|
181
193
|
- destroy the devbox when you are finished.
|
|
@@ -229,13 +241,22 @@ while the app is running. Older installed notification links continue to open
|
|
|
229
241
|
through the owning project. The mobile app icon badge can show unread thread
|
|
230
242
|
count for the signed-in device.
|
|
231
243
|
|
|
244
|
+
When several accounts are signed in, the phone receives notifications from all
|
|
245
|
+
of them. A notification for an account other than the one open appears even
|
|
246
|
+
while the app is in use, and tapping it switches to that account before opening
|
|
247
|
+
the thread. The app icon badge counts unread threads across the signed-in
|
|
248
|
+
accounts. An account starts receiving notifications on a phone after it has
|
|
249
|
+
been opened there once.
|
|
250
|
+
|
|
232
251
|
Use mobile settings to turn the unread badge on or off.
|
|
233
252
|
|
|
234
253
|
## Settings
|
|
235
254
|
|
|
236
255
|
Mobile settings include:
|
|
237
256
|
|
|
238
|
-
- account sign-in and sign-out
|
|
257
|
+
- account sign-in and sign-out, adding another account, and switching between
|
|
258
|
+
signed-in accounts;
|
|
259
|
+
- **Agent accounts**, for the Codex and Claude accounts your devboxes use;
|
|
239
260
|
- billing usage summary;
|
|
240
261
|
- an invite link and QR code you can share with someone who wants to try
|
|
241
262
|
boxes.dev (the same link is on the Account page in the web app);
|
|
@@ -243,8 +264,8 @@ Mobile settings include:
|
|
|
243
264
|
- theme, monospace font, and thread text size;
|
|
244
265
|
- release package details and refresh controls in installed builds;
|
|
245
266
|
- account deletion.
|
|
246
|
-
- a Help center link that opens `https://boxes.dev/help`
|
|
247
|
-
|
|
267
|
+
- a Help center link that opens the public guides at `https://boxes.dev/help`
|
|
268
|
+
in the browser.
|
|
248
269
|
|
|
249
270
|
Someone opening your invite link can sign up with Google in their phone
|
|
250
271
|
browser. After signing up on a phone, they will see that setup happens on
|
|
@@ -260,6 +281,30 @@ Account deletion permanently deletes your boxes.dev account, projects,
|
|
|
260
281
|
personal Template boxes, and devboxes. Team Templates belong to the team and
|
|
261
282
|
are not deleted with one member's account. The deletion cannot be undone.
|
|
262
283
|
|
|
284
|
+
### Agent Accounts
|
|
285
|
+
|
|
286
|
+
**Settings → Agent accounts** manages the same Codex and Claude accounts as
|
|
287
|
+
Configure agents in the desktop app. Each agent has its own list of saved
|
|
288
|
+
logins and API keys, and the checked row is the one your devboxes use. Tap
|
|
289
|
+
**Add** beside an agent to sign in or save an API key. Tap a saved row to
|
|
290
|
+
choose **Use this account**, **Re-authenticate** or **Edit API key**, **Check
|
|
291
|
+
now**, or **Remove**.
|
|
292
|
+
|
|
293
|
+
To sign in to Codex, tap **Log in with ChatGPT**. The app shows a one-time
|
|
294
|
+
code, and **Open ChatGPT** copies it and opens the ChatGPT device sign-in page.
|
|
295
|
+
Sign in there if asked and paste the code. Codex will connect after you
|
|
296
|
+
approve, even if you finish in another browser.
|
|
297
|
+
|
|
298
|
+
To sign in to Claude Code, tap **Log in with Claude**, then **Open Claude** and
|
|
299
|
+
approve access. Claude will show a code; copy it, return to the app, paste it,
|
|
300
|
+
and tap **Continue**. Closing either sign-in cancels it.
|
|
301
|
+
|
|
302
|
+
When the active Codex or Claude account needs you to sign in again, or its API
|
|
303
|
+
key was rejected, a banner appears at the top of the app. **Reconnect** opens
|
|
304
|
+
that agent's sign-in, or opens Agent accounts when both agents need attention
|
|
305
|
+
or a key needs replacing. Dismissing the banner hides it until the app restarts
|
|
306
|
+
or another account starts failing.
|
|
307
|
+
|
|
263
308
|
## Mobile Versus Desktop
|
|
264
309
|
|
|
265
310
|
Use desktop for setup, full project orientation, file upload/download workflows,
|
|
@@ -267,5 +312,6 @@ Git staging and commits, port forwarding, runtime process inspection, and
|
|
|
267
312
|
detailed review.
|
|
268
313
|
|
|
269
314
|
Use mobile when you want to monitor progress, answer questions, send a quick
|
|
270
|
-
follow-up,
|
|
271
|
-
shell, sleep or destroy a devbox, or
|
|
315
|
+
follow-up, reconnect a Codex or Claude account, take a Template-box snapshot,
|
|
316
|
+
inspect a linked file or diff, open a shell, sleep or destroy a devbox, or
|
|
317
|
+
check billing/status away from the desktop.
|
|
@@ -134,6 +134,45 @@ to write files on the Template box. `snapshot` waits for the new snapshot that
|
|
|
134
134
|
future devboxes will use. Take one only when the user wants the change to reach
|
|
135
135
|
future devboxes. Ordinary shell commands still act on the current devbox.
|
|
136
136
|
|
|
137
|
+
## Environment Variables
|
|
138
|
+
|
|
139
|
+
An agent can list, set, and remove the centrally managed environment variables
|
|
140
|
+
of the current project. See
|
|
141
|
+
[Managed environment files](managed-environment-files.md) for how these files
|
|
142
|
+
reach machines.
|
|
143
|
+
|
|
144
|
+
```bash
|
|
145
|
+
dvb-onbox env list --json
|
|
146
|
+
dvb-onbox env set --file .env.local --name API_BASE_URL --value https://api.example.test
|
|
147
|
+
printf %s "$TOKEN" | dvb-onbox env set --file .env.local --name API_TOKEN --value-stdin
|
|
148
|
+
dvb-onbox env remove --file .env.local --name API_TOKEN
|
|
149
|
+
```
|
|
150
|
+
|
|
151
|
+
What these commands change depends on the project:
|
|
152
|
+
|
|
153
|
+
- In a project with its own Template box, they edit the project's variables.
|
|
154
|
+
On the Template box they need no extra permission. On a devbox, the current
|
|
155
|
+
thread needs the `edit-template-box` permission.
|
|
156
|
+
- In a Team Template project, they edit the user's own variables: values for
|
|
157
|
+
Member rows the team defined, and variables the user added to any file.
|
|
158
|
+
Team values belong to the team and cannot be changed here. The current
|
|
159
|
+
thread needs `edit-personal-environment`, or `edit-team-template` for a team
|
|
160
|
+
admin.
|
|
161
|
+
|
|
162
|
+
`--file` is relative to the folder the result reports as `pathBase`.
|
|
163
|
+
`set` replaces the variable if it exists, adds it if it doesn't, and creates
|
|
164
|
+
the managed file if boxes.dev does not manage that path yet. An existing file's
|
|
165
|
+
other content stays below the managed section, so remove an old line with the
|
|
166
|
+
same name from the file yourself, on this machine and on the Template box when
|
|
167
|
+
future devboxes should not have it. Bringing an existing file under management
|
|
168
|
+
with a review of its current lines is done in **Project settings →
|
|
169
|
+
Environment files**.
|
|
170
|
+
|
|
171
|
+
`--value-stdin` reads the value from standard input and drops one trailing
|
|
172
|
+
newline. `list` returns names, where each value comes from, and whether a value
|
|
173
|
+
is saved; it never returns values. Saved changes reach running machines within
|
|
174
|
+
about a minute. After an uncertain response, run `list` before retrying.
|
|
175
|
+
|
|
137
176
|
## Devbox Lifecycle And Template Maintenance
|
|
138
177
|
|
|
139
178
|
From the project's current ordinary Template box, an agent can inspect and edit
|
|
@@ -242,8 +281,9 @@ The request values are `create-devboxes-and-threads`,
|
|
|
242
281
|
`move-devboxes-to-folders`, `create-devbox-folders`,
|
|
243
282
|
`edit-devbox-lifecycle`, `edit-template-maintenance`, `destroy-devbox`,
|
|
244
283
|
`read-project-threads`, `read-user-threads`, `read-shared-threads`,
|
|
245
|
-
`read-team-threads`, `
|
|
246
|
-
`--json` for a
|
|
284
|
+
`read-team-threads`, `message-agents`, `edit-template-box`,
|
|
285
|
+
`edit-team-template`, and `edit-personal-environment`. Add `--json` for a
|
|
286
|
+
stable structured result.
|
|
247
287
|
|
|
248
288
|
The command creates one request for the exact managed thread and source box,
|
|
249
289
|
then waits up to ten minutes while the owner sees **Deny**, **Allow**, and,
|
|
@@ -253,18 +293,25 @@ for every agent on that source box until the owner turns it off; it is not a
|
|
|
253
293
|
one-operation grant. **Deny** declines this request without changing permission
|
|
254
294
|
settings. An agent cannot answer its own request.
|
|
255
295
|
|
|
256
|
-
`edit-template-box` and `edit-
|
|
257
|
-
|
|
296
|
+
`edit-template-box`, `edit-team-template`, and `edit-personal-environment`
|
|
297
|
+
work differently. They apply only to the agent in the requesting thread, and
|
|
258
298
|
the owner sees **Deny** and **Allow for 3 hours**. The grant expires 3 hours
|
|
259
299
|
after approval. Other threads and boxes never receive it, and no Agent
|
|
260
300
|
permissions switch or project setting can enable it. Request
|
|
261
|
-
`edit-template-box` from a devbox in a project with its own Template box
|
|
262
|
-
|
|
263
|
-
team
|
|
264
|
-
|
|
265
|
-
|
|
266
|
-
|
|
267
|
-
can
|
|
301
|
+
`edit-template-box` from a devbox in a project with its own Template box to
|
|
302
|
+
edit that Template box and the project's environment variables. Request
|
|
303
|
+
`edit-team-template` from a devbox in a Team Template project to edit that
|
|
304
|
+
Team Template, including its environment variables; only a team admin can
|
|
305
|
+
receive it. Request `edit-personal-environment` from a devbox in a Team
|
|
306
|
+
Template project to edit the user's own environment variables for that
|
|
307
|
+
project; any member can receive it, and a thread that already has
|
|
308
|
+
`edit-team-template` does not need it. A thread holds one of these grants at a
|
|
309
|
+
time. After the grant expires, the next command reports the missing permission
|
|
310
|
+
and the agent needs a new request.
|
|
311
|
+
|
|
312
|
+
For thread reads, agent messaging, folder access, thread titles, and creating
|
|
313
|
+
devboxes and threads, the owner can choose **Always allow for project**
|
|
314
|
+
directly.
|
|
268
315
|
This will enable the project's shared permission and make the requesting box
|
|
269
316
|
use it. All existing and future devboxes will follow that setting, except
|
|
270
317
|
those configured separately. Other devboxes will keep their individual
|
|
@@ -657,6 +704,50 @@ If a needed scope reports `thread_read_access_disabled`, request the matching
|
|
|
657
704
|
`read-team-threads` permission. Team visibility limits require a team setting
|
|
658
705
|
change; an agent permission cannot override them.
|
|
659
706
|
|
|
707
|
+
## Message Other Agents
|
|
708
|
+
|
|
709
|
+
With **Message other agents** enabled in Agent permissions, an agent can send a
|
|
710
|
+
short message to another Codex or Claude thread in the same project, on the
|
|
711
|
+
same devbox or a different one, and receive messages in return. The setting
|
|
712
|
+
applies to every agent on the box. It is off by default, inherits the project's
|
|
713
|
+
setting, and can be overridden on a box. Both the sender's and the recipient's
|
|
714
|
+
boxes need it.
|
|
715
|
+
|
|
716
|
+
```bash
|
|
717
|
+
dvb-onbox threads message --to <thread-id> \
|
|
718
|
+
--message "The endpoint now returns 422 for invalid widgets." --json
|
|
719
|
+
```
|
|
720
|
+
|
|
721
|
+
`--to` takes a boxes.dev thread ID, such as one named in a received message,
|
|
722
|
+
one returned by `dvb-onbox threads start`, or one from
|
|
723
|
+
`dvb-onbox threads list --scope project`. Use this command rather than a
|
|
724
|
+
built-in agent messaging tool such as Claude's SendMessage, which cannot
|
|
725
|
+
address boxes.dev thread IDs or reach Codex and other devboxes, and may hold a
|
|
726
|
+
message until the recipient's user approves it. Messages are limited to 4 KiB;
|
|
727
|
+
point to files or threads for longer material. Only a managed agent thread can send,
|
|
728
|
+
so the recipient can reply. Sending will start an idle agent and wake the
|
|
729
|
+
recipient's devbox if it's asleep, which uses compute and model usage. An
|
|
730
|
+
active agent reads the message at its next opportunity in its current work.
|
|
731
|
+
|
|
732
|
+
The recipient's Codex or Claude receives the message from another agent, not
|
|
733
|
+
as user input. The message names the sender's thread and the command for
|
|
734
|
+
replying. It cannot answer a pending permission prompt or question for the
|
|
735
|
+
user. The user sees it in the recipient's thread as a message from the sending
|
|
736
|
+
agent, linked to the sender's thread.
|
|
737
|
+
|
|
738
|
+
A successful result means the recipient accepted the message; it does not mean
|
|
739
|
+
the agent has read, acted on, or answered it. Replies arrive later as messages
|
|
740
|
+
in the sender's thread. After `operation_indeterminate`, do not send the
|
|
741
|
+
message again, because it may already have arrived. A Claude agent in a
|
|
742
|
+
terminal that is busy or controlled by the user cannot receive messages
|
|
743
|
+
(`thread_busy` or `thread_controlled_elsewhere`); an idle, unattended terminal
|
|
744
|
+
session can. The recipient must be a started, unarchived thread in the same
|
|
745
|
+
project; messaging teammates or other projects is not available.
|
|
746
|
+
|
|
747
|
+
If sending reports `messaging_disabled`, request `message-agents`.
|
|
748
|
+
`recipient_messaging_disabled` means the recipient's devbox has messaging off;
|
|
749
|
+
only the user can change that, in that devbox's Agent permissions.
|
|
750
|
+
|
|
660
751
|
## Destroy And Archive The Current Devbox
|
|
661
752
|
|
|
662
753
|
An agent can request destruction of its own ordinary devbox with:
|
|
@@ -950,6 +1041,34 @@ destination approval. See [Member files](member-managed-files.md) for upload
|
|
|
950
1041
|
and delivery behavior. These commands return definitions only and do not
|
|
951
1042
|
upload or read a member's file contents.
|
|
952
1043
|
|
|
1044
|
+
### Team Template environment variables
|
|
1045
|
+
|
|
1046
|
+
An admin can define the Team Template's environment variables from the same
|
|
1047
|
+
places as member-file requirements, or from a member devbox whose thread has
|
|
1048
|
+
the `edit-team-template` permission. A member devbox does not need an open
|
|
1049
|
+
editing session for these commands.
|
|
1050
|
+
|
|
1051
|
+
```bash
|
|
1052
|
+
dvb-onbox team-template env list --json
|
|
1053
|
+
dvb-onbox team-template env set --file sandbox/.env.local --name LOG_LEVEL --value debug
|
|
1054
|
+
dvb-onbox team-template env set --file sandbox/.env.local --name OPENAI_API_KEY \
|
|
1055
|
+
--member --instructions 'Create a key at platform.openai.com.'
|
|
1056
|
+
dvb-onbox team-template env set --file sandbox/.env.local --name SENTRY_DSN \
|
|
1057
|
+
--member --optional
|
|
1058
|
+
dvb-onbox team-template env remove --file sandbox/.env.local --name LOG_LEVEL
|
|
1059
|
+
```
|
|
1060
|
+
|
|
1061
|
+
Paths are relative to `/home/boxes`. `--value` or `--value-stdin` saves a Team
|
|
1062
|
+
value that every member project receives. `--member` asks each member for their
|
|
1063
|
+
own value instead, required unless `--optional` is added, with optional
|
|
1064
|
+
`--instructions`. Switching a variable from Team to Member deletes its Team
|
|
1065
|
+
value. From an ordinary Template box, add `--template <team-template-id>`.
|
|
1066
|
+
|
|
1067
|
+
Changes take effect without saving a new Team Template version. Existing member
|
|
1068
|
+
projects receive Team values within about a minute. A new required Member value
|
|
1069
|
+
does not block existing devboxes; members will see it as needed in **Project
|
|
1070
|
+
settings → Environment files**.
|
|
1071
|
+
|
|
953
1072
|
### Create a Team Template from this project
|
|
954
1073
|
|
|
955
1074
|
A team admin can ask an agent on an ordinary project's Template box to create
|
|
@@ -1223,5 +1342,6 @@ Save only when the user asked to publish the change. `save` uses the normal
|
|
|
1223
1342
|
verified save pipeline, waits for it to finish, and ends this thread's access
|
|
1224
1343
|
to that editing session. Access also ends when the grant expires or an admin
|
|
1225
1344
|
saves the session in the desktop app. To make more changes, run `open` again
|
|
1226
|
-
with a new key.
|
|
1227
|
-
|
|
1345
|
+
with a new key. The **Team Template environment variables** commands above
|
|
1346
|
+
work from a member devbox without `open`. Member-file requirements and Team
|
|
1347
|
+
Template creation are not available from a devbox.
|
|
@@ -55,7 +55,12 @@ belong to their project and do not appear as separate projects in this list.
|
|
|
55
55
|
|
|
56
56
|
The desktop local-folder setup wizard usually moves through these stages:
|
|
57
57
|
|
|
58
|
-
1. Account: sign in to boxes.dev
|
|
58
|
+
1. Account: sign in to boxes.dev, then optionally connect GitHub and Slack on
|
|
59
|
+
**Connect your accounts**. GitHub here is sign-in only; boxes.dev asks for
|
|
60
|
+
repository access later, once it knows the project's repositories. Team
|
|
61
|
+
admins on a team without a Slack workspace see **Connect Slack** to install
|
|
62
|
+
it, anyone on a team with a workspace can link their Slack account, and
|
|
63
|
+
other members see no Slack row. Neither connection is required to continue.
|
|
59
64
|
2. Agents: connect Codex or Claude Code. At least one connected coding agent is
|
|
60
65
|
required before the first project can start.
|
|
61
66
|
3. Project: choose the local project folder and project name.
|
|
@@ -91,10 +96,17 @@ included repository is writable and covered by the boxes.dev GitHub App. When
|
|
|
91
96
|
automatic GitHub access is selected, the Template box and future devboxes use
|
|
92
97
|
HTTPS push/pull access without registering an SSH key. This is the default for
|
|
93
98
|
a fresh GitHub-origin setup even when GitHub still needs to be connected or its
|
|
94
|
-
access needs to be updated. If
|
|
95
|
-
|
|
96
|
-
|
|
97
|
-
|
|
99
|
+
access needs to be updated. If boxes.dev can't access the account that owns a
|
|
100
|
+
repository yet, setup shows **Connect your GitHub repositories**. For the
|
|
101
|
+
user's own personal account, its **Connect on GitHub** button opens GitHub with
|
|
102
|
+
that account already selected and **All repositories** chosen. For an
|
|
103
|
+
organization, it opens GitHub's account list and asks the user to choose the
|
|
104
|
+
organization; GitHub lists only organizations the user belongs to. If an
|
|
105
|
+
organization requires an owner's approval, GitHub sends the member's request to
|
|
106
|
+
an organization owner. Setup also offers a request message to send to an owner,
|
|
107
|
+
for members waiting on approval and for users who aren't in the organization.
|
|
108
|
+
If the repository belongs to another person's personal account, setup names the
|
|
109
|
+
owner and provides instructions to send them.
|
|
98
110
|
If GitHub requires an access update, setup keeps automatic access selected and
|
|
99
111
|
shows the affected **Update GitHub access** link or links; setup cannot continue
|
|
100
112
|
until the update is accepted. The user can instead choose **Use an SSH key for
|
|
@@ -180,17 +192,22 @@ file even when a large folder's displayed listing is shortened. Git-ignored
|
|
|
180
192
|
files need a named file selection if you want to copy them.
|
|
181
193
|
|
|
182
194
|
The desktop app's Project step leads with **Set up with your coding agent**,
|
|
183
|
-
followed by a Team Template when the team has one
|
|
184
|
-
|
|
185
|
-
|
|
186
|
-
|
|
195
|
+
followed by a Team Template when the team has one. The local-folder and GitHub
|
|
196
|
+
options are fallbacks under **Other setup options** at the bottom of the step,
|
|
197
|
+
with the local folder first. **Use coding agent** expands the card to show the
|
|
198
|
+
prompt to copy into Codex or Claude Code in the local project folder. When the
|
|
199
|
+
remote setup thread starts, the agent offers to open that project in the
|
|
200
|
+
desktop app, so the Project step does not need to stay open.
|
|
187
201
|
|
|
188
202
|
The commands mirror the wizard's stages: `dvb agent-init start` seeds the
|
|
189
203
|
version 3 manifest with everything detectable. A standard GitHub origin seeds
|
|
190
204
|
managed access without waiting for connection or repository inventory; the
|
|
191
205
|
manifest can instead select SSH or skip Git access. If GitHub is not connected,
|
|
192
206
|
`dvb agent-init github connect` opens the existing boxes.dev GitHub connection
|
|
193
|
-
flow.
|
|
207
|
+
flow. Once GitHub is connected, the same command opens the GitHub page that
|
|
208
|
+
gives the boxes.dev GitHub App access to the project's repositories: the
|
|
209
|
+
owner's installation settings, or the install page with the owning account
|
|
210
|
+
selected. `dvb agent-init check` verifies the exact writable repositories, App
|
|
194
211
|
visibility, and current GitHub access before a managed launch; when an update
|
|
195
212
|
is required, it prints the exact GitHub action and the SSH alternative. `dvb
|
|
196
213
|
agent-init run` executes the whole plan — encrypted bundle, upload, Template
|
|
@@ -248,7 +265,8 @@ Setup asks the user to connect at least one coding agent:
|
|
|
248
265
|
|
|
249
266
|
Users can connect both, but only one is required to start. If auth was skipped
|
|
250
267
|
for one agent, or if auth later breaks, use Configure agents in the desktop app
|
|
251
|
-
|
|
268
|
+
or **Settings → Agent accounts** in the mobile app to add another account or API
|
|
269
|
+
key, choose the active credential, edit an API
|
|
252
270
|
key, re-auth, remove a saved credential, or disconnect an agent. The active
|
|
253
271
|
Codex and Claude choices are independent and apply globally across the user's
|
|
254
272
|
devboxes. On macOS, Configure agents is in the boxes.dev app menu.
|
|
@@ -308,7 +326,9 @@ opens Configure agents. Connecting that agent there clears the block.
|
|
|
308
326
|
## Project Selection
|
|
309
327
|
|
|
310
328
|
The local-folder project step chooses the folder that becomes the boxes.dev
|
|
311
|
-
project.
|
|
329
|
+
project. In the desktop app, open **Other setup options** at the bottom of the
|
|
330
|
+
Project step, then choose **Browse...** or drop the folder onto the local-folder
|
|
331
|
+
option.
|
|
312
332
|
The project name must use lowercase letters, numbers, and dashes. If the
|
|
313
333
|
selected folder contains multiple direct child Git repos, setup shows those
|
|
314
334
|
repos under **Git repositories** and the user can choose which ones to include
|
|
@@ -346,9 +366,11 @@ creation until a project is deleted or billing changes allow another project.
|
|
|
346
366
|
|
|
347
367
|
On the logged-in website, including from a mobile browser, choose **Create from
|
|
348
368
|
GitHub** and connect a GitHub account. After a user has set up their first
|
|
349
|
-
project, the desktop app also offers **Create from GitHub**
|
|
350
|
-
|
|
351
|
-
|
|
369
|
+
project, the desktop app also offers **Create from GitHub** under **Other
|
|
370
|
+
setup options** when they start another project, marked **Manual setup**
|
|
371
|
+
because it suits only repositories that need little setup. The desktop
|
|
372
|
+
first-project flow leaves this option out so it can guide new users through
|
|
373
|
+
copying their local development environment instead.
|
|
352
374
|
Connecting first authorizes the user's GitHub identity. If the boxes.dev GitHub
|
|
353
375
|
App is not installed yet, setup then makes installation the required next step:
|
|
354
376
|
choose the personal account or organization that owns the repositories and
|
|
@@ -26,8 +26,10 @@ 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 Settings
|
|
30
|
-
|
|
29
|
+
for Slack. Team admins can also connect Slack from **Team Settings**, or from
|
|
30
|
+
the **Account** step of first-run desktop setup when their team has no Slack
|
|
31
|
+
workspace yet. Slack opens an authorization screen; choose the workspace and
|
|
32
|
+
allow the app.
|
|
31
33
|
|
|
32
34
|
After Slack redirects back, the Slack integration home continues through the
|
|
33
35
|
remaining setup steps: link your identity, create your automation, and activate
|
|
@@ -48,8 +50,9 @@ step is still needed.
|
|
|
48
50
|
|
|
49
51
|
You can link by:
|
|
50
52
|
|
|
51
|
-
- choosing **Connect Slack** on the
|
|
52
|
-
|
|
53
|
+
- choosing **Connect Slack** on the **Account** step of first-run desktop setup
|
|
54
|
+
or on the website's getting-started page, when your team already has a
|
|
55
|
+
connected Slack workspace;
|
|
53
56
|
- using **Find my Slack account** in the automation editor;
|
|
54
57
|
- opening the boxes.dev app DM in Slack and sending `connect`;
|
|
55
58
|
- following a connect link sent by a team admin from Team Settings.
|
|
@@ -67,6 +70,15 @@ then choose **Activate**. The integration home also shows recent runs and
|
|
|
67
70
|
surfaces one recovery action if the workspace, identity, or default behavior
|
|
68
71
|
needs attention.
|
|
69
72
|
|
|
73
|
+
A new **Default behavior** uses the project's new-thread agent, or the coding
|
|
74
|
+
agent you set up if you use only one, with that agent's saved model and
|
|
75
|
+
reasoning level. When a project's setup finishes and you have linked Slack but
|
|
76
|
+
have no active Slack default, the desktop workbench shows **Start threads from
|
|
77
|
+
Slack** above the project with the agent, model, and reasoning level it will
|
|
78
|
+
use. **Turn on** creates and activates the Default behavior, **Configure**
|
|
79
|
+
creates it paused and opens it for review, and **Not now** hides the prompt
|
|
80
|
+
for that project.
|
|
81
|
+
|
|
70
82
|
Your default Slack receiver runs when you mention `@boxes.dev` without a named
|
|
71
83
|
command. Each mention starts an agent thread on a fresh devbox and appears in
|
|
72
84
|
the main thread list alongside other devbox threads.
|
|
@@ -876,7 +876,8 @@ Team admins choose **Thread access** in Team settings:
|
|
|
876
876
|
With **Thread titles** or **All threads**, use **Teammates' projects** in the
|
|
877
877
|
desktop project selector or mobile Home to choose a teammate's project. The
|
|
878
878
|
Team workbench reuses the familiar devbox, thread-list, transcript, and
|
|
879
|
-
optional Template-box layout in read-only form.
|
|
879
|
+
optional Template-box layout in read-only form. A devbox its owner named
|
|
880
|
+
appears under that name. It does not include a composer,
|
|
880
881
|
Files, Git/Review, terminal, ports, or runtime controls. Opening Team work or a
|
|
881
882
|
shared transcript does not select or wake the viewer's last Template box or
|
|
882
883
|
devbox. Merely browsing a teammate's work does not add it to **Shared with
|
|
@@ -123,8 +123,12 @@ must be ready before work can start.
|
|
|
123
123
|
## Agent Auth Problems
|
|
124
124
|
|
|
125
125
|
If a Codex or Claude thread cannot start or continue because auth is
|
|
126
|
-
missing or expired,
|
|
127
|
-
the
|
|
126
|
+
missing or expired, reconnect the affected agent from **Configure agents** in
|
|
127
|
+
the desktop app or **Settings → Agent accounts** in the mobile app. When the
|
|
128
|
+
active Codex or Claude account needs attention, the mobile app shows a banner
|
|
129
|
+
at the top of the screen. Its **Reconnect** action opens that agent's sign-in,
|
|
130
|
+
or opens Agent accounts when both agents need attention or an API key was
|
|
131
|
+
rejected.
|
|
128
132
|
|
|
129
133
|
If Claude's sign-in page shows a temporary error while boxes.dev is waiting,
|
|
130
134
|
use the provider page's retry action. boxes.dev keeps waiting for the sign-in
|