@boxes-dev/dvb-runtime 1.0.1110 → 1.0.1112
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 +16 -5
- package/dist/bin/dvb.mjs +1329 -697
- package/dist/bin/dvbd.mjs +4515 -608
- package/dist/managed-codex-install/package-lock.json +28 -28
- package/dist/managed-codex-install/package.json +1 -1
- package/dist/product-docs/references/agent-tools.md +18 -0
- package/dist/product-docs/references/automations.md +9 -0
- package/dist/product-docs/references/aws.md +21 -0
- package/dist/product-docs/references/desktop-workbench.md +17 -0
- package/dist/product-docs/references/google-cloud.md +8 -0
- package/dist/product-docs/references/mobile.md +14 -4
- package/dist/product-docs/references/onbox-agent-tools.md +140 -8
- package/dist/product-docs/references/ports-terminal-and-runtime.md +16 -4
- package/dist/product-docs/references/project-setup.md +24 -10
- package/dist/product-docs/references/tailscale.md +14 -0
- package/dist/product-docs/references/team-template.md +27 -9
- package/dist/product-docs/references/template-box-environment.md +7 -0
- package/dist/product-docs/references/threads-and-agents.md +93 -18
- package/dist/product-docs/references/troubleshooting.md +27 -0
- package/dist/product-docs/references/unattended-work.md +10 -3
- package/package.json +2 -2
|
@@ -8,13 +8,13 @@
|
|
|
8
8
|
"name": "@boxes-dev/managed-codex-install",
|
|
9
9
|
"version": "0.0.0",
|
|
10
10
|
"dependencies": {
|
|
11
|
-
"@openai/codex": "0.
|
|
11
|
+
"@openai/codex": "0.166.0"
|
|
12
12
|
}
|
|
13
13
|
},
|
|
14
14
|
"node_modules/@openai/codex": {
|
|
15
|
-
"version": "0.
|
|
16
|
-
"resolved": "https://registry.npmjs.org/@openai/codex/-/codex-0.
|
|
17
|
-
"integrity": "sha512-
|
|
15
|
+
"version": "0.166.0",
|
|
16
|
+
"resolved": "https://registry.npmjs.org/@openai/codex/-/codex-0.166.0.tgz",
|
|
17
|
+
"integrity": "sha512-2Szlp1l1cz5TX1ccpX4Zok3DZrot9xeZe0km+6/1v8JmqxADwyJxKBJah4dBymkwtS25j/u6dipJusTOI97Z8Q==",
|
|
18
18
|
"license": "Apache-2.0",
|
|
19
19
|
"bin": {
|
|
20
20
|
"codex": "bin/codex.js"
|
|
@@ -23,19 +23,19 @@
|
|
|
23
23
|
"node": ">=16"
|
|
24
24
|
},
|
|
25
25
|
"optionalDependencies": {
|
|
26
|
-
"@openai/codex-darwin-arm64": "npm:@openai/codex@0.
|
|
27
|
-
"@openai/codex-darwin-x64": "npm:@openai/codex@0.
|
|
28
|
-
"@openai/codex-linux-arm64": "npm:@openai/codex@0.
|
|
29
|
-
"@openai/codex-linux-x64": "npm:@openai/codex@0.
|
|
30
|
-
"@openai/codex-win32-arm64": "npm:@openai/codex@0.
|
|
31
|
-
"@openai/codex-win32-x64": "npm:@openai/codex@0.
|
|
26
|
+
"@openai/codex-darwin-arm64": "npm:@openai/codex@0.166.0-darwin-arm64",
|
|
27
|
+
"@openai/codex-darwin-x64": "npm:@openai/codex@0.166.0-darwin-x64",
|
|
28
|
+
"@openai/codex-linux-arm64": "npm:@openai/codex@0.166.0-linux-arm64",
|
|
29
|
+
"@openai/codex-linux-x64": "npm:@openai/codex@0.166.0-linux-x64",
|
|
30
|
+
"@openai/codex-win32-arm64": "npm:@openai/codex@0.166.0-win32-arm64",
|
|
31
|
+
"@openai/codex-win32-x64": "npm:@openai/codex@0.166.0-win32-x64"
|
|
32
32
|
}
|
|
33
33
|
},
|
|
34
34
|
"node_modules/@openai/codex-darwin-arm64": {
|
|
35
35
|
"name": "@openai/codex",
|
|
36
|
-
"version": "0.
|
|
37
|
-
"resolved": "https://registry.npmjs.org/@openai/codex/-/codex-0.
|
|
38
|
-
"integrity": "sha512-
|
|
36
|
+
"version": "0.166.0-darwin-arm64",
|
|
37
|
+
"resolved": "https://registry.npmjs.org/@openai/codex/-/codex-0.166.0-darwin-arm64.tgz",
|
|
38
|
+
"integrity": "sha512-5fWH6qqUInACcRADIewjlnRxDb4QLe0uriwehiZz0+viuAAB8I+WWefqw4xwHvyKaxeiGX4uK56+vrgfvFk3FQ==",
|
|
39
39
|
"cpu": [
|
|
40
40
|
"arm64"
|
|
41
41
|
],
|
|
@@ -50,9 +50,9 @@
|
|
|
50
50
|
},
|
|
51
51
|
"node_modules/@openai/codex-darwin-x64": {
|
|
52
52
|
"name": "@openai/codex",
|
|
53
|
-
"version": "0.
|
|
54
|
-
"resolved": "https://registry.npmjs.org/@openai/codex/-/codex-0.
|
|
55
|
-
"integrity": "sha512-
|
|
53
|
+
"version": "0.166.0-darwin-x64",
|
|
54
|
+
"resolved": "https://registry.npmjs.org/@openai/codex/-/codex-0.166.0-darwin-x64.tgz",
|
|
55
|
+
"integrity": "sha512-Vj5wXJPizKmrzNtnRNQf9PP6FJkG3iJU/UO3NE4WvkENZGoQfmImdwf4MVRI5NgwjSuC6LT0HbBRHPVVnwGHuw==",
|
|
56
56
|
"cpu": [
|
|
57
57
|
"x64"
|
|
58
58
|
],
|
|
@@ -67,9 +67,9 @@
|
|
|
67
67
|
},
|
|
68
68
|
"node_modules/@openai/codex-linux-arm64": {
|
|
69
69
|
"name": "@openai/codex",
|
|
70
|
-
"version": "0.
|
|
71
|
-
"resolved": "https://registry.npmjs.org/@openai/codex/-/codex-0.
|
|
72
|
-
"integrity": "sha512-
|
|
70
|
+
"version": "0.166.0-linux-arm64",
|
|
71
|
+
"resolved": "https://registry.npmjs.org/@openai/codex/-/codex-0.166.0-linux-arm64.tgz",
|
|
72
|
+
"integrity": "sha512-w0ScAsBr9aZKtIFrh6HN6KU2yjKKeSCzYfbb7DB0Ccj4BYPzeZtUeQprbycLCwuX3AFQdbdjapmLho2iot74jQ==",
|
|
73
73
|
"cpu": [
|
|
74
74
|
"arm64"
|
|
75
75
|
],
|
|
@@ -84,9 +84,9 @@
|
|
|
84
84
|
},
|
|
85
85
|
"node_modules/@openai/codex-linux-x64": {
|
|
86
86
|
"name": "@openai/codex",
|
|
87
|
-
"version": "0.
|
|
88
|
-
"resolved": "https://registry.npmjs.org/@openai/codex/-/codex-0.
|
|
89
|
-
"integrity": "sha512-
|
|
87
|
+
"version": "0.166.0-linux-x64",
|
|
88
|
+
"resolved": "https://registry.npmjs.org/@openai/codex/-/codex-0.166.0-linux-x64.tgz",
|
|
89
|
+
"integrity": "sha512-CxDm3+D1cpbGJeHrdzINoG+3wn9BVncP4qpZaaNYkxe8iPtRJOYyCJnnPoVjWRIBvI9vPKbRoifsMSA5xDaUpw==",
|
|
90
90
|
"cpu": [
|
|
91
91
|
"x64"
|
|
92
92
|
],
|
|
@@ -101,9 +101,9 @@
|
|
|
101
101
|
},
|
|
102
102
|
"node_modules/@openai/codex-win32-arm64": {
|
|
103
103
|
"name": "@openai/codex",
|
|
104
|
-
"version": "0.
|
|
105
|
-
"resolved": "https://registry.npmjs.org/@openai/codex/-/codex-0.
|
|
106
|
-
"integrity": "sha512-
|
|
104
|
+
"version": "0.166.0-win32-arm64",
|
|
105
|
+
"resolved": "https://registry.npmjs.org/@openai/codex/-/codex-0.166.0-win32-arm64.tgz",
|
|
106
|
+
"integrity": "sha512-LWO1cyGlxbKgeUM7QJ1a6QMSsJi++3PqgIi6BmIUBoj/kzZqRIR69UDMQgeU/9izzJFYMSbwt++lHnUFyjQXlA==",
|
|
107
107
|
"cpu": [
|
|
108
108
|
"arm64"
|
|
109
109
|
],
|
|
@@ -118,9 +118,9 @@
|
|
|
118
118
|
},
|
|
119
119
|
"node_modules/@openai/codex-win32-x64": {
|
|
120
120
|
"name": "@openai/codex",
|
|
121
|
-
"version": "0.
|
|
122
|
-
"resolved": "https://registry.npmjs.org/@openai/codex/-/codex-0.
|
|
123
|
-
"integrity": "sha512-
|
|
121
|
+
"version": "0.166.0-win32-x64",
|
|
122
|
+
"resolved": "https://registry.npmjs.org/@openai/codex/-/codex-0.166.0-win32-x64.tgz",
|
|
123
|
+
"integrity": "sha512-NS8Ps5oG5r19pCrMCUXwUqOui6odnUIoBlQkrjCJ+h1k6KiwCzC/+mI9d3nSZCqFoVONPBTmqyq8NYq3YaFGyA==",
|
|
124
124
|
"cpu": [
|
|
125
125
|
"x64"
|
|
126
126
|
],
|
|
@@ -285,6 +285,24 @@ includes a bounded compact transcript when available; needs-input, failure,
|
|
|
285
285
|
interruption, archive, timeout, and local cancellation remain distinct.
|
|
286
286
|
Ctrl+C stops only local observation and does not interrupt the remote agent.
|
|
287
287
|
|
|
288
|
+
When the agent is waiting for input, `pendingInput` describes its current
|
|
289
|
+
question or approval request, with the owner's name and a `threadUrl` when
|
|
290
|
+
available. Lists include a short description; reads and input waits include
|
|
291
|
+
the questions and choices. `truncated` identifies shortened descriptions.
|
|
292
|
+
If the agent reports waiting without a saved question, the kind is `unknown`.
|
|
293
|
+
Null or an omitted field means no pending input is known from this read.
|
|
294
|
+
|
|
295
|
+
Codex questions come from saved pending requests, so reading one does not
|
|
296
|
+
require attaching to the live agent. An exact-turn wait stops only when the
|
|
297
|
+
request identifies that turn. A question without a turn ID can appear in
|
|
298
|
+
reads without ending the wait; pass its question and link to the owner.
|
|
299
|
+
|
|
300
|
+
Give the owner the question and thread link. They can open the thread in the
|
|
301
|
+
app to answer; seeing the request does not authorize an agent or teammate to
|
|
302
|
+
answer or approve it. After the owner answers, wait again on the same turn:
|
|
303
|
+
an earlier question does not end that new wait. boxes.dev permission requests
|
|
304
|
+
may remain visible after a turn ends and do not end an exact-turn wait.
|
|
305
|
+
|
|
288
306
|
For incremental orchestration, stream durable lifecycle events:
|
|
289
307
|
|
|
290
308
|
```bash
|
|
@@ -36,6 +36,15 @@ conversation on its current devbox, using the thread's current agent settings.
|
|
|
36
36
|
|
|
37
37
|
## Creating An Automation
|
|
38
38
|
|
|
39
|
+
Agents with `edit-automations` can prepare a default Slack or Linear receiver
|
|
40
|
+
using `dvb-onbox automations create-receiver --integration slack|linear --json`.
|
|
41
|
+
The integration must already be connected and the owner's identity linked.
|
|
42
|
+
Creation saves a paused receiver with the same defaults as the app; repeating
|
|
43
|
+
the command returns the existing receiver without changing it. The agent can
|
|
44
|
+
then configure and activate it through the existing automation commands.
|
|
45
|
+
Who can trigger Slack, bot access, Slack Connect locations and attachment
|
|
46
|
+
policies remain owner settings in Integrations.
|
|
47
|
+
|
|
39
48
|
Open the Automations section in the desktop workbench and choose **New
|
|
40
49
|
automation**. Choose when the automation should run, then configure its name,
|
|
41
50
|
agent, prompt, and model controls. Trigger-specific setup such as a schedule or
|
|
@@ -234,6 +234,27 @@ current machine identity before the helper can receive credentials.
|
|
|
234
234
|
|
|
235
235
|
## Change, Remove, Or Reconnect
|
|
236
236
|
|
|
237
|
+
### Agent setup
|
|
238
|
+
|
|
239
|
+
An agent can inspect saved integration status with
|
|
240
|
+
`dvb-onbox project settings get --json` and explicitly list the accounts and
|
|
241
|
+
permission sets assigned to the owner's Company SSO identity. The list includes
|
|
242
|
+
account names and IDs, including production accounts, but no credentials.
|
|
243
|
+
|
|
244
|
+
Adding or changing a managed Company SSO profile requires approval of that
|
|
245
|
+
specific change. The request identifies the boxes.dev project, profile, AWS
|
|
246
|
+
account and permission set. Approving it will make that access available to
|
|
247
|
+
programs and agents on the project's boxes. The agent must apply the approved
|
|
248
|
+
change within ten minutes; the saved choice remains afterward. A different
|
|
249
|
+
account or permission set requires another approval.
|
|
250
|
+
|
|
251
|
+
Agents cannot replace an access-key profile, remove profiles, change team SSO
|
|
252
|
+
setup or sign in for the owner through these controls. Follow the returned
|
|
253
|
+
owner-settings link for those steps. See `onbox-agent-tools.md` for the command
|
|
254
|
+
contract.
|
|
255
|
+
|
|
256
|
+
### Manage profiles in the app
|
|
257
|
+
|
|
237
258
|
The **Managed profiles** section shows the project's centrally managed access:
|
|
238
259
|
|
|
239
260
|
- `boxes-dev` is the required default. Use **Edit** to change its account,
|
|
@@ -504,6 +504,9 @@ preview. Open the notification to answer in the thread; ordinary progress
|
|
|
504
504
|
messages do not send question alerts. Existing notification settings apply,
|
|
505
505
|
and questions can still notify you when the thread's completion alerts are muted.
|
|
506
506
|
|
|
507
|
+
Codex also sends an input alert when it pauses for a question, form, or approval.
|
|
508
|
+
Reopening the same pending request does not send another alert.
|
|
509
|
+
|
|
507
510
|
The menu for an eligible non-archived thread includes **Mark unread**. The
|
|
508
511
|
thread stays unread until you open it again, and the same state appears in the
|
|
509
512
|
mobile app and unread badge counts.
|
|
@@ -654,6 +657,20 @@ choice. Profile reset is the separate destructive action.
|
|
|
654
657
|
Browser can also pop out from the side pane into
|
|
655
658
|
a near-full-window overlay and dock back into the workbench.
|
|
656
659
|
|
|
660
|
+
In the desktop Browser toolbar, select **Show downloads**, then **Open** beside a
|
|
661
|
+
completed file to open it in the file viewer. Files stay on the selected box;
|
|
662
|
+
use Files to download a copy to your computer. When an automation tool chooses
|
|
663
|
+
another download folder, Browser retains its own named copy without moving the
|
|
664
|
+
tool's file. A large download can stay in progress while that copy finishes.
|
|
665
|
+
If Browser can't retain its copy, the download entry will show an error, even
|
|
666
|
+
if the automation tool saved its own file successfully. Retained files use disk
|
|
667
|
+
space and aren't automatically deleted when an agent disconnects or an entry
|
|
668
|
+
leaves the recent-download list.
|
|
669
|
+
After an automation tool disconnects, later downloads can also stay in the
|
|
670
|
+
box's `~/Downloads` folder. Use **Open** to find the retained file, then delete
|
|
671
|
+
it in Files when no longer needed; delete the other copy too if one remains in
|
|
672
|
+
`~/Downloads`.
|
|
673
|
+
|
|
657
674
|
The mobile app's Browser shares these tabs and profile. Opening it on a phone
|
|
658
675
|
resizes the shared browser to the phone's screen, and the pane keeps showing
|
|
659
676
|
its last picture. Moving the pointer into the pane, or focusing it, resizes the
|
|
@@ -111,6 +111,14 @@ Cloud page.
|
|
|
111
111
|
|
|
112
112
|
## Change, Remove, Or Reconnect
|
|
113
113
|
|
|
114
|
+
An agent can read saved connection and project status with
|
|
115
|
+
`dvb-onbox project settings get --json`. After the owner signs in, the agent can
|
|
116
|
+
request `edit-google-cloud-integration` for three hours to choose an accessible
|
|
117
|
+
default/quota project for this boxes.dev project. The selected project remains
|
|
118
|
+
after permission expires. Selection does not limit the Google account's IAM
|
|
119
|
+
access or change its permissions. Signing in, changing accounts, disconnecting
|
|
120
|
+
and signing out remain owner actions in the app.
|
|
121
|
+
|
|
114
122
|
The options menu on the desktop project row, and the **Options** section on
|
|
115
123
|
mobile, have these actions:
|
|
116
124
|
|
|
@@ -242,6 +242,12 @@ answers or multiple questions, use the form's submit button. Unfinished answers
|
|
|
242
242
|
stay in place when you scroll away and back. If Codex finishes its turn before
|
|
243
243
|
you send an asynchronous answer, your edited answer returns to the composer.
|
|
244
244
|
|
|
245
|
+
A pending Codex question or form can appear before the phone connects to the
|
|
246
|
+
agent. You can read it while connecting, but its response controls become
|
|
247
|
+
available only when the agent confirms the request is still pending.
|
|
248
|
+
Prefilled form values and browser destinations load with that connection.
|
|
249
|
+
Requests answered on another device disappear when the phone reconnects.
|
|
250
|
+
|
|
245
251
|
While a Codex turn is active, a follow-up in Queue mode appears as **Queued**
|
|
246
252
|
and contributes to the message count beside **Steer now**. That row stays
|
|
247
253
|
available while the queued follow-up moves through delivery. **Steer now**
|
|
@@ -368,10 +374,11 @@ settling.
|
|
|
368
374
|
In a devbox thread, tapping the **Devbox** pill in the header opens the
|
|
369
375
|
devbox's status and a read-only list of its Git changes. The status names the
|
|
370
376
|
state behind the pill's colored dot, such as **Running**, **Sleeping**,
|
|
371
|
-
**Waking**, **Upgrading**, or **Upgrade failed**.
|
|
372
|
-
boxes.dev update didn't install on the devbox
|
|
373
|
-
|
|
374
|
-
|
|
377
|
+
**Waking**, **Upgrading**, or **Upgrade failed**. An amber dot with **Upgrade
|
|
378
|
+
failed** means the latest boxes.dev update didn't install on the devbox, which
|
|
379
|
+
still works on its current version. The Git list shows each repository's
|
|
380
|
+
branch, merge conflicts, commits that haven't been pushed, and changed files
|
|
381
|
+
with added and removed line counts. Tapping a changed file opens
|
|
375
382
|
its diff in the file viewer. A warning icon in the pill or the thread row means
|
|
376
383
|
a repository has unresolved merge conflicts.
|
|
377
384
|
|
|
@@ -454,6 +461,9 @@ with a question preview. Open it to answer in the thread. Quiet hours, pause,
|
|
|
454
461
|
desktop presence, and this phone's alert preference still apply; muting a
|
|
455
462
|
thread's completion notifications will not mute its questions.
|
|
456
463
|
|
|
464
|
+
Codex also sends an input alert when it pauses for a question, form, or approval.
|
|
465
|
+
Reopening the same pending request does not send another alert.
|
|
466
|
+
|
|
457
467
|
When several accounts are signed in, the phone receives notifications from all
|
|
458
468
|
of them. A notification for an account other than the one open appears even
|
|
459
469
|
while the app is in use, and tapping it switches to that account before opening
|
|
@@ -75,10 +75,12 @@ dvb-onbox whoami --json
|
|
|
75
75
|
|
|
76
76
|
The JSON result contains the account's `userId`, `email`, and `name`. `email`
|
|
77
77
|
and `name` are `null` when the account has none. `userId` is the account's
|
|
78
|
-
stable ID and stays the same if its email address changes.
|
|
79
|
-
|
|
80
|
-
|
|
81
|
-
|
|
78
|
+
stable ID and stays the same if its email address changes. On a devbox, the
|
|
79
|
+
result also includes the devbox's instance ID as `devboxId`; it is `null` on
|
|
80
|
+
any other box. The command needs no permission and works on a Template box, a
|
|
81
|
+
devbox, and a Team Template editing machine. Use it when a script or tool needs
|
|
82
|
+
to attribute work to the person who owns the box; it does not identify who sent
|
|
83
|
+
a particular message.
|
|
82
84
|
|
|
83
85
|
## Plan And Usage
|
|
84
86
|
|
|
@@ -314,7 +316,7 @@ dvb-onbox project settings set --settings-file /home/boxes/settings-edit.json --
|
|
|
314
316
|
dvb-onbox team-template settings set --settings-file /home/boxes/settings-edit.json --json
|
|
315
317
|
```
|
|
316
318
|
|
|
317
|
-
|
|
319
|
+
General project writes need the current thread's three-hour `edit-project-settings`
|
|
318
320
|
grant. The project's setup thread can save `default_branches` without one. An active `edit-template-box` or `edit-team-template` grant also covers
|
|
319
321
|
that thread's project settings. Team Template writes need team-admin authority
|
|
320
322
|
and `edit-team-template`, or an existing authorized template editing host or
|
|
@@ -323,6 +325,82 @@ including from an independent project created from it. Request only the minimum
|
|
|
323
325
|
permission returned by a denied write. Agent permission defaults remain
|
|
324
326
|
user-only even with an editing grant.
|
|
325
327
|
|
|
328
|
+
### Integration status and setup
|
|
329
|
+
|
|
330
|
+
The project read includes `integrations.isTeamAdmin` and
|
|
331
|
+
`integrations.providers` for Tailscale, AWS, Google Cloud (`google_cloud`),
|
|
332
|
+
GitHub, Slack, Linear, Convex, Vercel, managed MCPs (`mcp`) and project plugins.
|
|
333
|
+
Each entry separates account, team and project scope and includes its Team
|
|
334
|
+
Template `requirement` and `ownerSetupUrl`. The setup link opens that integration
|
|
335
|
+
for the current project in the desktop app; on a phone it explains that desktop
|
|
336
|
+
is needed. Status reads contain no saved secrets, sign-in codes or login URLs.
|
|
337
|
+
They describe persisted configuration and reported application state, not a live
|
|
338
|
+
connection test. Use the integration's native diagnostics, such as
|
|
339
|
+
`tailscale status`, to check the current box. `dvb-onbox setup status` reports
|
|
340
|
+
the managed Template-box setup job; it is not a general integration health check.
|
|
341
|
+
|
|
342
|
+
Integration operations use the same settings file command with these sections:
|
|
343
|
+
|
|
344
|
+
| Section | Fields and permission |
|
|
345
|
+
| --- | --- |
|
|
346
|
+
| `aws_accounts` | No other fields; explicitly lists the signed-in owner's assigned accounts, without an edit grant. |
|
|
347
|
+
| `aws_roles` | `accountId`; lists that owner's assigned roles in the account, without an edit grant. |
|
|
348
|
+
| `aws_profile` | `profileName`, `accountId`, `roleName`, `expectedBindingId` (the read's binding ID, or null for a new profile), `reason` and `approvalRequestId`. The last two are text or null. Requires approval of this exact change. |
|
|
349
|
+
| `tailscale_enable` | `connectNewDevboxesAutomatically` (boolean, or null to preserve), `reason` and `approvalRequestId` (text or null). Requires approval of this exact enablement and optional auto-connect choice. |
|
|
350
|
+
| `tailscale_auto_connect` | `enabled`; requires `edit-tailscale-integration` for three hours. |
|
|
351
|
+
| `google_cloud_project` | `gcpProjectId`; requires `edit-google-cloud-integration` for three hours. |
|
|
352
|
+
| `google_cloud_projects` | No other fields; lists accessible projects under `edit-google-cloud-integration`. |
|
|
353
|
+
|
|
354
|
+
AWS discovery exposes account names/IDs and role names, including production
|
|
355
|
+
names, but no credentials. It is an explicit provider request, separate from
|
|
356
|
+
status reads. Respect any returned pagination or truncation information.
|
|
357
|
+
Use `boxes-dev` for the first profile. Additional managed profile names must
|
|
358
|
+
start with `boxes-` and contain only lowercase letters, numbers and hyphens.
|
|
359
|
+
|
|
360
|
+
Successful JSON results contain `settings.saved: true` for edits, optionally
|
|
361
|
+
with `unchanged`, `alreadyEnabled` or `alreadyCompleted` set to true. Discovery
|
|
362
|
+
returns `settings.choices.accounts`, `settings.choices.roles`, or
|
|
363
|
+
`settings.choices.projects`; Google results also include
|
|
364
|
+
`settings.choices.truncated`. Discovery does not save settings.
|
|
365
|
+
|
|
366
|
+
For an exact action, first submit `approvalRequestId: null`. The command reports
|
|
367
|
+
that nothing was saved and returns an approval request ID. Wait with
|
|
368
|
+
`dvb-onbox permissions wait --request-id <id> --json`; after approval, resubmit
|
|
369
|
+
the same operation with that ID. Do not request these action kinds through
|
|
370
|
+
`permissions request`, which cannot describe the specific change. The request
|
|
371
|
+
names the actual account or tailnet using backend-verified details; `reason`
|
|
372
|
+
is optional attributed context from the agent. Denial saves nothing.
|
|
373
|
+
The wait command's `granted` result confirms approval only; the resubmission
|
|
374
|
+
still needs to succeed before the setting changes.
|
|
375
|
+
|
|
376
|
+
Preparation returns `approval_required` with `approvalRequestId`. If application
|
|
377
|
+
returns `approval_stale`, read current settings and prepare a fresh request.
|
|
378
|
+
For `approval_mismatch`, resubmit the values the owner approved, or prepare a
|
|
379
|
+
new request for the intended change. `tailscale_not_eligible` means enablement
|
|
380
|
+
was refused; follow the returned owner-setup guidance before trying again.
|
|
381
|
+
|
|
382
|
+
Approved actions must be applied within ten minutes. A changed target needs a
|
|
383
|
+
fresh approval. A completed retry reports completion and does not overwrite
|
|
384
|
+
later human edits. After an unknown or replaced request ID, read status again.
|
|
385
|
+
Use an updated app or CLI if the owner's client cannot show the detailed request.
|
|
386
|
+
|
|
387
|
+
Routine Google and Tailscale grants are independent of general Project or
|
|
388
|
+
Template editing. Expiry stops further edits and does not undo saved changes.
|
|
389
|
+
Google selection sets a default/quota project; it does not restrict IAM access.
|
|
390
|
+
Tailscale auto-connect affects future devboxes only. Once enabled, anything
|
|
391
|
+
running on the project's boxes can use their granted network access.
|
|
392
|
+
|
|
393
|
+
Sign-in, team configuration, global sign-out and project removal remain owner
|
|
394
|
+
steps. Agents cannot replace an AWS access-key profile through this command.
|
|
395
|
+
GitHub, Convex and Vercel gain status reads only. Managed MCP and plugin commands
|
|
396
|
+
retain their existing authority: adding a non-OAuth project MCP can immediately
|
|
397
|
+
make its tools available to agents across project boxes, and agents can remove
|
|
398
|
+
project MCP connections without a temporary grant. Team definitions retain
|
|
399
|
+
their current protections. The reads cover managed connections and the project
|
|
400
|
+
plugin registry, not every locally installed extension.
|
|
401
|
+
|
|
402
|
+
### General settings operations
|
|
403
|
+
|
|
326
404
|
For example, preserve every lifecycle field returned by `get`, then change
|
|
327
405
|
only the intended value in this operation:
|
|
328
406
|
|
|
@@ -495,6 +573,7 @@ dvb-onbox automations options --json
|
|
|
495
573
|
dvb-onbox automations list --json
|
|
496
574
|
dvb-onbox automations get --automation <id> --json
|
|
497
575
|
dvb-onbox automations create --spec-file spec.json [--prompt-file prompt.md] --json
|
|
576
|
+
dvb-onbox automations create-receiver --integration slack|linear --json
|
|
498
577
|
dvb-onbox automations update --automation <id> [--spec-file changes.json] [--prompt-file prompt.md] --if-revision <revision> [--dry-run] --json
|
|
499
578
|
dvb-onbox automations activate --automation <id> --json
|
|
500
579
|
dvb-onbox automations pause --automation <id> --json
|
|
@@ -512,6 +591,12 @@ commands need the current thread's `edit-automations` permission (see
|
|
|
512
591
|
[Agent Permissions](#agent-permissions)); without it they fail with
|
|
513
592
|
`automation_editing_disabled`.
|
|
514
593
|
|
|
594
|
+
`create-receiver` creates the project's paused default Slack or Linear receiver
|
|
595
|
+
after the owner has connected and linked their identity. Repeating it returns
|
|
596
|
+
the existing receiver without changing its state. It accepts no access policy,
|
|
597
|
+
bot, external-location or file-attachment options. Configure and activate through
|
|
598
|
+
the existing automation operations; keep those access choices in Integrations.
|
|
599
|
+
|
|
515
600
|
### Spec
|
|
516
601
|
|
|
517
602
|
`create` reads a JSON spec. Put the prompt in the spec as `prompt` or in a
|
|
@@ -563,8 +648,9 @@ separate `--prompt-file`, not both. File paths can be relative or absolute.
|
|
|
563
648
|
(0–6, Sunday first) for weekly schedules; and `monthDay` for monthly ones.
|
|
564
649
|
Runs begin at the first matching time after now, so `startDate` can be
|
|
565
650
|
today or earlier. The `startDate` of a weekly schedule must fall on one of
|
|
566
|
-
its `weekdays`, and that of a monthly schedule on its `monthDay`.
|
|
567
|
-
Slack
|
|
651
|
+
its `weekdays`, and that of a monthly schedule on its `monthDay`.
|
|
652
|
+
Slack named-command and API triggers must be set up in the desktop app.
|
|
653
|
+
Use `create-receiver` for a default Slack or Linear receiver.
|
|
568
654
|
- `threadPlacement`: `nested` (under the automation) or `main` (the main
|
|
569
655
|
thread list).
|
|
570
656
|
- `target`: `{"kind": "thread", "thread": "current"}` to continue the calling
|
|
@@ -829,7 +915,8 @@ The request values are `create-devboxes-and-threads`,
|
|
|
829
915
|
`destroy-created-devboxes`, `destroy-project-devboxes`, `read-project-threads`, `read-user-threads`, `read-shared-threads`,
|
|
830
916
|
`read-team-threads`, `control-created-threads`, `control-project-threads`,
|
|
831
917
|
`control-user-threads`, `message-agents`, `message-teammates-agents`, `edit-template-box`,
|
|
832
|
-
`edit-team-template`, `edit-project-settings`, `edit-personal-environment`,
|
|
918
|
+
`edit-team-template`, `edit-project-settings`, `edit-personal-environment`,
|
|
919
|
+
`edit-automations`, `edit-tailscale-integration`, and `edit-google-cloud-integration`.
|
|
833
920
|
Add `--json` for a stable structured result.
|
|
834
921
|
|
|
835
922
|
The command creates one request for the exact managed thread and source box,
|
|
@@ -868,6 +955,13 @@ pause, activate, run, and delete the owner's automations in that project; see
|
|
|
868
955
|
[Automations](#automations). It is kept apart from the grants above, so a
|
|
869
956
|
thread can hold it together with one of them.
|
|
870
957
|
|
|
958
|
+
`edit-tailscale-integration` and `edit-google-cloud-integration` are independent
|
|
959
|
+
three-hour grants for routine integration settings. A thread can hold both
|
|
960
|
+
alongside its other grants. They do not inherit from broader settings access.
|
|
961
|
+
`change-aws-profile` and `enable-tailscale-integration` require the exact settings
|
|
962
|
+
operation to prepare their approval, rather than `permissions request`. See
|
|
963
|
+
[Integration status and setup](#integration-status-and-setup).
|
|
964
|
+
|
|
871
965
|
For thread reads and controls, agent messaging, folder access, thread titles, destroying
|
|
872
966
|
devboxes, and creating devboxes and threads, the owner can choose **Always allow for project**
|
|
873
967
|
directly.
|
|
@@ -1555,6 +1649,28 @@ an opaque resume cursor on every JSONL row. With no turn, cursor, or
|
|
|
1555
1649
|
`--from-start`, it follows only events created after the command starts. An
|
|
1556
1650
|
exact-turn stream ends after needs-input or a terminal event.
|
|
1557
1651
|
|
|
1652
|
+
When a child needs input, `pendingInput` describes the current question or
|
|
1653
|
+
approval request, including the owner's name and a `threadUrl` when available.
|
|
1654
|
+
Lists and status reads include a short description; reads, input waits, and a still-pending
|
|
1655
|
+
exact-turn result include the questions and choices. `truncated` identifies
|
|
1656
|
+
shortened content. A waiting agent without a saved question has kind
|
|
1657
|
+
`unknown`. Null or an omitted field means no pending input is known from that
|
|
1658
|
+
read; these descriptions can lag the live agent.
|
|
1659
|
+
|
|
1660
|
+
Codex descriptions use saved pending requests and do not require a live
|
|
1661
|
+
attachment. A request tied to the active turn makes reads report
|
|
1662
|
+
`needs_input` and ends a wait for that turn. A request without a turn ID
|
|
1663
|
+
remains visible in reads but cannot end an exact-turn wait. Pass its question
|
|
1664
|
+
and link to the owner instead of assuming the turn has completed.
|
|
1665
|
+
|
|
1666
|
+
Give the owner the question and link so they can open the thread in the app
|
|
1667
|
+
and answer. The request ID is only an opaque identifier; it grants no ability
|
|
1668
|
+
to answer or approve for the owner. After an answer, wait again on the same
|
|
1669
|
+
turn. An earlier question does not end that new wait, and an input wait does
|
|
1670
|
+
not mean the turn has completed. An `access_request` describes an outstanding
|
|
1671
|
+
boxes.dev permission request; it can outlive a turn and never ends an
|
|
1672
|
+
exact-turn wait.
|
|
1673
|
+
|
|
1558
1674
|
If an accepted child is later deleted, `threads list` retains its ID as a
|
|
1559
1675
|
`failed` entry titled **Deleted delegated thread**. Reads explain that it was
|
|
1560
1676
|
deleted, and controls return `thread_not_found`. Retrying its original start with the same idempotency key
|
|
@@ -1670,6 +1786,13 @@ be read, even while the agent is working. These stored states can lag live work
|
|
|
1670
1786
|
or change before a message arrives, so they do not guarantee idle-only delivery.
|
|
1671
1787
|
Reading status does not wake a devbox or require delegation permission.
|
|
1672
1788
|
|
|
1789
|
+
Readers with conversation access also receive `pendingInput` for a waiting
|
|
1790
|
+
agent, using the same question and owner-link fields as delegated reads.
|
|
1791
|
+
Metadata-only readers receive no pending-input details. boxes.dev permission
|
|
1792
|
+
requests are visible only for the owner's own threads. When reading through
|
|
1793
|
+
a supplied share invitation, use the returned `threadUrl` to preserve that
|
|
1794
|
+
access; the link grants no ability to answer for the owner.
|
|
1795
|
+
|
|
1673
1796
|
For known threads, fetch their metadata together instead of scanning the whole
|
|
1674
1797
|
project or reading their conversations:
|
|
1675
1798
|
|
|
@@ -1734,6 +1857,15 @@ They may lag active work and shorten long messages. They do not wake boxes,
|
|
|
1734
1857
|
mark threads read, claim links, or expose full tool logs. Without `--scope`,
|
|
1735
1858
|
the existing `list` and `read` commands still select delegated children only.
|
|
1736
1859
|
|
|
1860
|
+
Scoped preview and full JSON messages include `messageTimeMs`: the time recorded
|
|
1861
|
+
for the source message, in Unix milliseconds, or `null` when unavailable. Older
|
|
1862
|
+
services may omit the field. Continued parts of a message retain the same time.
|
|
1863
|
+
A queued message's time reflects delivery to the agent.
|
|
1864
|
+
Use message times, rather than thread `updatedAt`, when reconstructing activity;
|
|
1865
|
+
keep the returned message order. Some forked Codex threads timestamp copied messages
|
|
1866
|
+
at the fork time, so their dates do not establish when the original conversation
|
|
1867
|
+
happened.
|
|
1868
|
+
|
|
1737
1869
|
For original visible message text, add `--full --json`:
|
|
1738
1870
|
|
|
1739
1871
|
```bash
|
|
@@ -19,6 +19,17 @@ preference. When auto-wake is off, passive navigation leaves the box
|
|
|
19
19
|
asleep. Explicitly sending a message to a Codex or Claude thread will still
|
|
20
20
|
wake its machine through the normal wake flow, even with auto-wake off.
|
|
21
21
|
|
|
22
|
+
The running box's status menu also has **Keep awake**, which keeps the box
|
|
23
|
+
awake for 1, 2, or 4 hours even when idle. Users turn it on while testing an
|
|
24
|
+
app through desktop localhost forwarding, which doesn't count as activity.
|
|
25
|
+
While it's on, a lightning icon shows next to the box name in the status pill,
|
|
26
|
+
and the pill's tooltip and the menu show the deadline. The box uses box-hours
|
|
27
|
+
the whole time, and billing limits still apply. **Turn off** in the same
|
|
28
|
+
submenu, or sleeping, resetting or rebooting the box, ends it. Then normal idle
|
|
29
|
+
sleep resumes unless other work keeps the box awake. Only the user can turn it
|
|
30
|
+
on, from the desktop app; it isn't offered on Team Template editing boxes.
|
|
31
|
+
Agents use keep-awake requests instead (below).
|
|
32
|
+
|
|
22
33
|
When the box is sleeping, use Wake from the status pill, Terminal, Files,
|
|
23
34
|
Git, or Ports. If a devbox is sleeping because the awake devbox limit is full,
|
|
24
35
|
boxes.dev asks you to sleep another devbox before continuing.
|
|
@@ -210,10 +221,11 @@ again. Choosing the computer icon on a different box will move localhost there.
|
|
|
210
221
|
On a new-thread draft, **Ports** remains available to inspect or release the
|
|
211
222
|
chosen box.
|
|
212
223
|
|
|
213
|
-
Keeping localhost does not freeze a branch, start an app, or keep the box awake
|
|
214
|
-
|
|
215
|
-
|
|
216
|
-
|
|
224
|
+
Keeping localhost does not freeze a branch, start an app, or keep the box awake;
|
|
225
|
+
use **Keep awake** in the status menu for that. If it sleeps, select it and use
|
|
226
|
+
the existing wake control. If it is removed or becomes unavailable, localhost
|
|
227
|
+
stays assigned until you release it or choose another box. Other tools,
|
|
228
|
+
including Terminal and Git, still follow selection.
|
|
217
229
|
|
|
218
230
|
Signing in to a Template box MCP temporarily forwards only its sign-in callback
|
|
219
231
|
port. Your app's other ports stay on the box you chose. If that callback port is
|
|
@@ -286,8 +286,12 @@ project's setup page. The page lists five stages: planning the setup with the
|
|
|
286
286
|
coding agent, uploading the project files (with a percentage), creating the
|
|
287
287
|
Template box, unpacking the files on the Template box, and starting setup on
|
|
288
288
|
the Template box. While the agent plans, the page shows when it prepares the
|
|
289
|
-
project, when the user needs to act, when
|
|
290
|
-
when a
|
|
289
|
+
project, when the user needs to act, when the plan still has unfinished parts,
|
|
290
|
+
when a check found other issues in the plan, when a setup command fails, and
|
|
291
|
+
when the setup plan is ready for approval. If a check finds no connected
|
|
292
|
+
account or available Codex model provider for the plan's coding agents, the
|
|
293
|
+
page asks the user to add one through `dvb agent-init accounts`, or to have the
|
|
294
|
+
agent switch the plan to a coding agent they've already connected.
|
|
291
295
|
The planning stage spins only while the agent prepares the project. When setup
|
|
292
296
|
can't continue until the user checks the coding agent, such as for a check
|
|
293
297
|
that found issues or a plan ready for approval, the stage stops spinning and
|
|
@@ -427,15 +431,22 @@ client remains preferred. Missing database variables, authentication problems,
|
|
|
427
431
|
missing MySQL clients, and PostgreSQL servers newer than the available client
|
|
428
432
|
are reported before the full bundle is built.
|
|
429
433
|
|
|
434
|
+
The agent should run on the computer where the user develops the app. If it
|
|
435
|
+
runs somewhere else, such as Codex cloud, it should tell the user before
|
|
436
|
+
continuing. Setup will copy the project from that environment, so the
|
|
437
|
+
environment needs to run the app with its configuration and services. Files
|
|
438
|
+
and agent settings on the user's own computer won't be included.
|
|
439
|
+
|
|
430
440
|
The prompt from **Get started**, the website's **New project** page, or the
|
|
431
441
|
desktop app's **Set up with your coding agent** card has the agent run `dvb
|
|
432
442
|
agent-init --login-code <code>`, which signs the CLI in without another
|
|
433
443
|
browser sign-in. If the code has expired or was already used, the CLI keeps an
|
|
434
444
|
existing CLI sign-in when it has one. Otherwise, `dvb agent-init login` opens
|
|
435
445
|
Google sign-in in the browser, prints the link, and waits for the user to
|
|
436
|
-
finish.
|
|
437
|
-
|
|
438
|
-
|
|
446
|
+
finish. When the agent runs on another computer, the browser can't reach the
|
|
447
|
+
CLI, so the agent asks the user to copy a fresh prompt instead. The CLI
|
|
448
|
+
assumes another computer over SSH and on Linux without a display, which
|
|
449
|
+
includes cloud agent environments such as Codex cloud.
|
|
439
450
|
|
|
440
451
|
Next, `dvb agent-init accounts` opens **Connect your accounts** in the
|
|
441
452
|
browser. There the user connects Codex, Claude Code, or both, and can connect
|
|
@@ -448,8 +459,8 @@ connection allows Codex setup without an OpenAI account. **Done** becomes
|
|
|
448
459
|
available once a coding agent is connected,
|
|
449
460
|
and the command waits until the user chooses it. If an agent is already
|
|
450
461
|
connected to boxes.dev, no new sign-in is needed; choose **Done** to continue
|
|
451
|
-
setup with that account.
|
|
452
|
-
a link for the user to open and exits: on that page, Codex shows a one-time
|
|
462
|
+
setup with that account. When the agent runs on another computer, the
|
|
463
|
+
command prints a link for the user to open and exits: on that page, Codex shows a one-time
|
|
453
464
|
code to enter on ChatGPT, Claude Code asks for the code Claude shows, and the
|
|
454
465
|
user tells the agent when they're done. **Use a code instead** switches a
|
|
455
466
|
local page to the same code flows for setups where browser sign-in can't
|
|
@@ -464,8 +475,9 @@ the agent where the user can follow it. On a Mac or Linux computer with the
|
|
|
464
475
|
desktop app installed, the agent offers to open it with
|
|
465
476
|
`dvb agent-init open-desktop`, which opens the Template box on the setup
|
|
466
477
|
thread. Without the app, the agent gives the download link for that computer
|
|
467
|
-
(`https://boxes.dev/mac` or `https://boxes.dev/linux`)
|
|
468
|
-
|
|
478
|
+
(`https://boxes.dev/mac` or `https://boxes.dev/linux`). On other operating
|
|
479
|
+
systems, or when the agent runs on another computer, it points to the mobile
|
|
480
|
+
app. When setup finishes on a
|
|
469
481
|
Mac or Linux computer with the desktop app installed, `dvb agent-init` opens the app on the setup thread, where the user
|
|
470
482
|
can read the setup agent's summary. Otherwise, the agent lists the same
|
|
471
483
|
choices. Either way, the agent also mentions `dvb agents <project>`, which
|
|
@@ -532,7 +544,9 @@ Each saved subscription row in desktop Configure agents shows a small bar for
|
|
|
532
544
|
the weekly limit's remaining usage. A 5-hour bar appears below it only when
|
|
533
545
|
that limit is low (below 20% left) or the account has no weekly limit. Hovering
|
|
534
546
|
over the bars shows the same quota details as the thread composer, plus when
|
|
535
|
-
the reading was taken if it is more than 15 minutes old.
|
|
547
|
+
the reading was taken if it is more than 15 minutes old. A Claude subscription
|
|
548
|
+
that has run out of a limit and is still working on extra usage shows **Using
|
|
549
|
+
extra usage** beside its name. Opening Configure
|
|
536
550
|
agents asks the providers for fresh readings of saved subscriptions; an
|
|
537
551
|
account whose saved sign-in has expired keeps its last reading until an agent
|
|
538
552
|
uses it again. API key rows show when the key was last used and today's tokens,
|
|
@@ -75,6 +75,20 @@ Tailscale integration page. boxes.dev uses the team connection to confirm that:
|
|
|
75
75
|
After verification succeeds, choose **Enable Tailscale** to enable the project.
|
|
76
76
|
Verification alone does not enable the integration.
|
|
77
77
|
|
|
78
|
+
An agent can inspect saved status with `dvb-onbox project settings get --json`
|
|
79
|
+
and request approval to enable Tailscale for this project. The request names
|
|
80
|
+
the tailnet and tag and can include the choice to connect future devboxes
|
|
81
|
+
automatically. Approving it will authorize network access for software and
|
|
82
|
+
agents on the project's boxes. The agent must apply that exact choice within
|
|
83
|
+
ten minutes; enablement remains afterward. The same eligibility check applies
|
|
84
|
+
as in the owner's setup flow.
|
|
85
|
+
|
|
86
|
+
Later changes to **Connect new devboxes automatically** need the thread's
|
|
87
|
+
three-hour `edit-tailscale-integration` permission. Expiry stops further edits
|
|
88
|
+
and leaves the saved setting in place. Team setup and project-wide disable
|
|
89
|
+
remain owner/admin actions. Saved status is not a live connectivity check;
|
|
90
|
+
use `tailscale status` on the box for that.
|
|
91
|
+
|
|
78
92
|
This verification uses Tailscale's policy engine, so direct users, groups,
|
|
79
93
|
SCIM-synced groups, wildcards, and autogroups continue to be managed in
|
|
80
94
|
Tailscale. GitHub-only and passkey-only Tailscale login names are not supported
|