@boxes-dev/dvb-runtime 1.0.1109 → 1.0.1111
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/bin/dvb.mjs +1148 -583
- package/dist/bin/dvbd.mjs +4541 -609
- 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 +24 -2
- package/dist/product-docs/references/fork-workflows.md +17 -0
- package/dist/product-docs/references/google-cloud.md +8 -0
- package/dist/product-docs/references/mobile.md +17 -7
- package/dist/product-docs/references/onbox-agent-tools.md +145 -4
- package/dist/product-docs/references/ports-terminal-and-runtime.md +32 -0
- package/dist/product-docs/references/tailscale.md +14 -0
- package/dist/product-docs/references/team-template.md +27 -9
- package/dist/product-docs/references/threads-and-agents.md +35 -17
- package/dist/product-docs/references/troubleshooting.md +43 -0
- package/dist/product-docs/references/unattended-work.md +10 -3
- package/package.json +2 -2
|
@@ -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,
|
|
@@ -283,8 +283,13 @@ Git/Review, Terminal, Browser, or Ports.
|
|
|
283
283
|
The app menu also includes **Project settings**, **Settings...**,
|
|
284
284
|
**Configure agents...**, **Sign Out**, update actions, and **Show Workbench**.
|
|
285
285
|
Configure agents can save multiple Codex and Claude accounts or API keys and
|
|
286
|
-
choose one active credential for each agent across all devboxes.
|
|
287
|
-
|
|
286
|
+
choose one active credential for each agent across all devboxes. Codex needs to
|
|
287
|
+
restart to switch to or from an API key. While Codex is working on a devbox, it
|
|
288
|
+
keeps the old credential and the desktop shows **Restart Codex** above the reply
|
|
289
|
+
box. Threads stay connected and running work can still be steered or stopped,
|
|
290
|
+
but new work needs to wait until the running work finishes or Codex restarts.
|
|
291
|
+
Restarting stops all running Codex work on that devbox. The File menu also
|
|
292
|
+
includes **Delete This Project**.
|
|
288
293
|
|
|
289
294
|
## Box status
|
|
290
295
|
|
|
@@ -499,6 +504,9 @@ preview. Open the notification to answer in the thread; ordinary progress
|
|
|
499
504
|
messages do not send question alerts. Existing notification settings apply,
|
|
500
505
|
and questions can still notify you when the thread's completion alerts are muted.
|
|
501
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
|
+
|
|
502
510
|
The menu for an eligible non-archived thread includes **Mark unread**. The
|
|
503
511
|
thread stays unread until you open it again, and the same state appears in the
|
|
504
512
|
mobile app and unread badge counts.
|
|
@@ -649,6 +657,20 @@ choice. Profile reset is the separate destructive action.
|
|
|
649
657
|
Browser can also pop out from the side pane into
|
|
650
658
|
a near-full-window overlay and dock back into the workbench.
|
|
651
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
|
+
|
|
652
674
|
The mobile app's Browser shares these tabs and profile. Opening it on a phone
|
|
653
675
|
resizes the shared browser to the phone's screen, and the pane keeps showing
|
|
654
676
|
its last picture. Moving the pointer into the pane, or focusing it, resizes the
|
|
@@ -449,6 +449,16 @@ If a Codex or Claude turn is still working when destruction is confirmed,
|
|
|
449
449
|
boxes.dev stops that turn before preserving the transcript. Other active agent
|
|
450
450
|
types must finish or be stopped before the devbox can be destroyed.
|
|
451
451
|
|
|
452
|
+
If a forked Codex thread needs missing parent history, boxes.dev first tries
|
|
453
|
+
to recover it from your saved thread archives in the same project. If the
|
|
454
|
+
required history is still missing, the devbox will stay available and the app
|
|
455
|
+
will list the affected threads. Choose **Keep devbox**, or review **Destroy anyway**.
|
|
456
|
+
Confirming that choice will keep those threads as readable **History only**
|
|
457
|
+
conversations that cannot be continued. Healthy threads will keep their normal
|
|
458
|
+
restorable archives. If readable history has not finished syncing, the devbox
|
|
459
|
+
will stay available; retry after syncing or delete the affected thread before
|
|
460
|
+
destroying the devbox. Automatic cleanup will not accept this loss for you.
|
|
461
|
+
|
|
452
462
|
Destroying a devbox does not automatically save code to the Template box or to
|
|
453
463
|
Git. Commit, push, merge, download, or otherwise save anything important first.
|
|
454
464
|
The archived transcripts remain readable without a running machine. To
|
|
@@ -459,6 +469,13 @@ current saved Team Template version. The available destination returns the
|
|
|
459
469
|
thread directly to the normal thread list. Restoring a thread restores its
|
|
460
470
|
conversation, not the destroyed devbox's filesystem or working tree.
|
|
461
471
|
|
|
472
|
+
If a restore cannot use the Template box's copy of a fork's parent history,
|
|
473
|
+
the thread will explain the conflict. Where **Restore to new devbox** is
|
|
474
|
+
available, that action will use a separate devbox and preserve the parent on
|
|
475
|
+
its current box. Otherwise, restore the original thread's history on the
|
|
476
|
+
Template box before retrying. Leaving the thread archived will keep its saved
|
|
477
|
+
archive available.
|
|
478
|
+
|
|
462
479
|
If the devbox has a child draft with unsent text, boxes.dev blocks destruction
|
|
463
480
|
until that draft is opened and discarded.
|
|
464
481
|
|
|
@@ -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
|
|
|
@@ -88,9 +88,9 @@ Open a project to see its threads. The list can include:
|
|
|
88
88
|
- recent threads;
|
|
89
89
|
- with **Group devboxes started by agents** on in Settings, each devbox an
|
|
90
90
|
agent started, under the devbox that started it. A slim row labeled
|
|
91
|
-
**Devboxes
|
|
92
|
-
count because the phone may not have loaded all of them, and a
|
|
93
|
-
parent has not loaded lists on its own until it does;
|
|
91
|
+
**Devboxes** shows their status and starts open; tap it to hide them. It
|
|
92
|
+
shows no count because the phone may not have loaded all of them, and a
|
|
93
|
+
devbox whose parent has not loaded lists on its own until it does;
|
|
94
94
|
- devbox groups, with child threads under the devbox and, when the devbox has
|
|
95
95
|
archived threads, an **Archived threads** list at the end of the group;
|
|
96
96
|
- an **Archived threads** list at the end of the project for the Template
|
|
@@ -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
|
|
@@ -314,7 +314,7 @@ dvb-onbox project settings set --settings-file /home/boxes/settings-edit.json --
|
|
|
314
314
|
dvb-onbox team-template settings set --settings-file /home/boxes/settings-edit.json --json
|
|
315
315
|
```
|
|
316
316
|
|
|
317
|
-
|
|
317
|
+
General project writes need the current thread's three-hour `edit-project-settings`
|
|
318
318
|
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
319
|
that thread's project settings. Team Template writes need team-admin authority
|
|
320
320
|
and `edit-team-template`, or an existing authorized template editing host or
|
|
@@ -323,6 +323,82 @@ including from an independent project created from it. Request only the minimum
|
|
|
323
323
|
permission returned by a denied write. Agent permission defaults remain
|
|
324
324
|
user-only even with an editing grant.
|
|
325
325
|
|
|
326
|
+
### Integration status and setup
|
|
327
|
+
|
|
328
|
+
The project read includes `integrations.isTeamAdmin` and
|
|
329
|
+
`integrations.providers` for Tailscale, AWS, Google Cloud (`google_cloud`),
|
|
330
|
+
GitHub, Slack, Linear, Convex, Vercel, managed MCPs (`mcp`) and project plugins.
|
|
331
|
+
Each entry separates account, team and project scope and includes its Team
|
|
332
|
+
Template `requirement` and `ownerSetupUrl`. The setup link opens that integration
|
|
333
|
+
for the current project in the desktop app; on a phone it explains that desktop
|
|
334
|
+
is needed. Status reads contain no saved secrets, sign-in codes or login URLs.
|
|
335
|
+
They describe persisted configuration and reported application state, not a live
|
|
336
|
+
connection test. Use the integration's native diagnostics, such as
|
|
337
|
+
`tailscale status`, to check the current box. `dvb-onbox setup status` reports
|
|
338
|
+
the managed Template-box setup job; it is not a general integration health check.
|
|
339
|
+
|
|
340
|
+
Integration operations use the same settings file command with these sections:
|
|
341
|
+
|
|
342
|
+
| Section | Fields and permission |
|
|
343
|
+
| --- | --- |
|
|
344
|
+
| `aws_accounts` | No other fields; explicitly lists the signed-in owner's assigned accounts, without an edit grant. |
|
|
345
|
+
| `aws_roles` | `accountId`; lists that owner's assigned roles in the account, without an edit grant. |
|
|
346
|
+
| `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. |
|
|
347
|
+
| `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. |
|
|
348
|
+
| `tailscale_auto_connect` | `enabled`; requires `edit-tailscale-integration` for three hours. |
|
|
349
|
+
| `google_cloud_project` | `gcpProjectId`; requires `edit-google-cloud-integration` for three hours. |
|
|
350
|
+
| `google_cloud_projects` | No other fields; lists accessible projects under `edit-google-cloud-integration`. |
|
|
351
|
+
|
|
352
|
+
AWS discovery exposes account names/IDs and role names, including production
|
|
353
|
+
names, but no credentials. It is an explicit provider request, separate from
|
|
354
|
+
status reads. Respect any returned pagination or truncation information.
|
|
355
|
+
Use `boxes-dev` for the first profile. Additional managed profile names must
|
|
356
|
+
start with `boxes-` and contain only lowercase letters, numbers and hyphens.
|
|
357
|
+
|
|
358
|
+
Successful JSON results contain `settings.saved: true` for edits, optionally
|
|
359
|
+
with `unchanged`, `alreadyEnabled` or `alreadyCompleted` set to true. Discovery
|
|
360
|
+
returns `settings.choices.accounts`, `settings.choices.roles`, or
|
|
361
|
+
`settings.choices.projects`; Google results also include
|
|
362
|
+
`settings.choices.truncated`. Discovery does not save settings.
|
|
363
|
+
|
|
364
|
+
For an exact action, first submit `approvalRequestId: null`. The command reports
|
|
365
|
+
that nothing was saved and returns an approval request ID. Wait with
|
|
366
|
+
`dvb-onbox permissions wait --request-id <id> --json`; after approval, resubmit
|
|
367
|
+
the same operation with that ID. Do not request these action kinds through
|
|
368
|
+
`permissions request`, which cannot describe the specific change. The request
|
|
369
|
+
names the actual account or tailnet using backend-verified details; `reason`
|
|
370
|
+
is optional attributed context from the agent. Denial saves nothing.
|
|
371
|
+
The wait command's `granted` result confirms approval only; the resubmission
|
|
372
|
+
still needs to succeed before the setting changes.
|
|
373
|
+
|
|
374
|
+
Preparation returns `approval_required` with `approvalRequestId`. If application
|
|
375
|
+
returns `approval_stale`, read current settings and prepare a fresh request.
|
|
376
|
+
For `approval_mismatch`, resubmit the values the owner approved, or prepare a
|
|
377
|
+
new request for the intended change. `tailscale_not_eligible` means enablement
|
|
378
|
+
was refused; follow the returned owner-setup guidance before trying again.
|
|
379
|
+
|
|
380
|
+
Approved actions must be applied within ten minutes. A changed target needs a
|
|
381
|
+
fresh approval. A completed retry reports completion and does not overwrite
|
|
382
|
+
later human edits. After an unknown or replaced request ID, read status again.
|
|
383
|
+
Use an updated app or CLI if the owner's client cannot show the detailed request.
|
|
384
|
+
|
|
385
|
+
Routine Google and Tailscale grants are independent of general Project or
|
|
386
|
+
Template editing. Expiry stops further edits and does not undo saved changes.
|
|
387
|
+
Google selection sets a default/quota project; it does not restrict IAM access.
|
|
388
|
+
Tailscale auto-connect affects future devboxes only. Once enabled, anything
|
|
389
|
+
running on the project's boxes can use their granted network access.
|
|
390
|
+
|
|
391
|
+
Sign-in, team configuration, global sign-out and project removal remain owner
|
|
392
|
+
steps. Agents cannot replace an AWS access-key profile through this command.
|
|
393
|
+
GitHub, Convex and Vercel gain status reads only. Managed MCP and plugin commands
|
|
394
|
+
retain their existing authority: adding a non-OAuth project MCP can immediately
|
|
395
|
+
make its tools available to agents across project boxes, and agents can remove
|
|
396
|
+
project MCP connections without a temporary grant. Team definitions retain
|
|
397
|
+
their current protections. The reads cover managed connections and the project
|
|
398
|
+
plugin registry, not every locally installed extension.
|
|
399
|
+
|
|
400
|
+
### General settings operations
|
|
401
|
+
|
|
326
402
|
For example, preserve every lifecycle field returned by `get`, then change
|
|
327
403
|
only the intended value in this operation:
|
|
328
404
|
|
|
@@ -495,6 +571,7 @@ dvb-onbox automations options --json
|
|
|
495
571
|
dvb-onbox automations list --json
|
|
496
572
|
dvb-onbox automations get --automation <id> --json
|
|
497
573
|
dvb-onbox automations create --spec-file spec.json [--prompt-file prompt.md] --json
|
|
574
|
+
dvb-onbox automations create-receiver --integration slack|linear --json
|
|
498
575
|
dvb-onbox automations update --automation <id> [--spec-file changes.json] [--prompt-file prompt.md] --if-revision <revision> [--dry-run] --json
|
|
499
576
|
dvb-onbox automations activate --automation <id> --json
|
|
500
577
|
dvb-onbox automations pause --automation <id> --json
|
|
@@ -512,6 +589,12 @@ commands need the current thread's `edit-automations` permission (see
|
|
|
512
589
|
[Agent Permissions](#agent-permissions)); without it they fail with
|
|
513
590
|
`automation_editing_disabled`.
|
|
514
591
|
|
|
592
|
+
`create-receiver` creates the project's paused default Slack or Linear receiver
|
|
593
|
+
after the owner has connected and linked their identity. Repeating it returns
|
|
594
|
+
the existing receiver without changing its state. It accepts no access policy,
|
|
595
|
+
bot, external-location or file-attachment options. Configure and activate through
|
|
596
|
+
the existing automation operations; keep those access choices in Integrations.
|
|
597
|
+
|
|
515
598
|
### Spec
|
|
516
599
|
|
|
517
600
|
`create` reads a JSON spec. Put the prompt in the spec as `prompt` or in a
|
|
@@ -563,8 +646,9 @@ separate `--prompt-file`, not both. File paths can be relative or absolute.
|
|
|
563
646
|
(0–6, Sunday first) for weekly schedules; and `monthDay` for monthly ones.
|
|
564
647
|
Runs begin at the first matching time after now, so `startDate` can be
|
|
565
648
|
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
|
|
649
|
+
its `weekdays`, and that of a monthly schedule on its `monthDay`.
|
|
650
|
+
Slack named-command and API triggers must be set up in the desktop app.
|
|
651
|
+
Use `create-receiver` for a default Slack or Linear receiver.
|
|
568
652
|
- `threadPlacement`: `nested` (under the automation) or `main` (the main
|
|
569
653
|
thread list).
|
|
570
654
|
- `target`: `{"kind": "thread", "thread": "current"}` to continue the calling
|
|
@@ -829,7 +913,8 @@ The request values are `create-devboxes-and-threads`,
|
|
|
829
913
|
`destroy-created-devboxes`, `destroy-project-devboxes`, `read-project-threads`, `read-user-threads`, `read-shared-threads`,
|
|
830
914
|
`read-team-threads`, `control-created-threads`, `control-project-threads`,
|
|
831
915
|
`control-user-threads`, `message-agents`, `message-teammates-agents`, `edit-template-box`,
|
|
832
|
-
`edit-team-template`, `edit-project-settings`, `edit-personal-environment`,
|
|
916
|
+
`edit-team-template`, `edit-project-settings`, `edit-personal-environment`,
|
|
917
|
+
`edit-automations`, `edit-tailscale-integration`, and `edit-google-cloud-integration`.
|
|
833
918
|
Add `--json` for a stable structured result.
|
|
834
919
|
|
|
835
920
|
The command creates one request for the exact managed thread and source box,
|
|
@@ -868,6 +953,13 @@ pause, activate, run, and delete the owner's automations in that project; see
|
|
|
868
953
|
[Automations](#automations). It is kept apart from the grants above, so a
|
|
869
954
|
thread can hold it together with one of them.
|
|
870
955
|
|
|
956
|
+
`edit-tailscale-integration` and `edit-google-cloud-integration` are independent
|
|
957
|
+
three-hour grants for routine integration settings. A thread can hold both
|
|
958
|
+
alongside its other grants. They do not inherit from broader settings access.
|
|
959
|
+
`change-aws-profile` and `enable-tailscale-integration` require the exact settings
|
|
960
|
+
operation to prepare their approval, rather than `permissions request`. See
|
|
961
|
+
[Integration status and setup](#integration-status-and-setup).
|
|
962
|
+
|
|
871
963
|
For thread reads and controls, agent messaging, folder access, thread titles, destroying
|
|
872
964
|
devboxes, and creating devboxes and threads, the owner can choose **Always allow for project**
|
|
873
965
|
directly.
|
|
@@ -1555,6 +1647,28 @@ an opaque resume cursor on every JSONL row. With no turn, cursor, or
|
|
|
1555
1647
|
`--from-start`, it follows only events created after the command starts. An
|
|
1556
1648
|
exact-turn stream ends after needs-input or a terminal event.
|
|
1557
1649
|
|
|
1650
|
+
When a child needs input, `pendingInput` describes the current question or
|
|
1651
|
+
approval request, including the owner's name and a `threadUrl` when available.
|
|
1652
|
+
Lists and status reads include a short description; reads, input waits, and a still-pending
|
|
1653
|
+
exact-turn result include the questions and choices. `truncated` identifies
|
|
1654
|
+
shortened content. A waiting agent without a saved question has kind
|
|
1655
|
+
`unknown`. Null or an omitted field means no pending input is known from that
|
|
1656
|
+
read; these descriptions can lag the live agent.
|
|
1657
|
+
|
|
1658
|
+
Codex descriptions use saved pending requests and do not require a live
|
|
1659
|
+
attachment. A request tied to the active turn makes reads report
|
|
1660
|
+
`needs_input` and ends a wait for that turn. A request without a turn ID
|
|
1661
|
+
remains visible in reads but cannot end an exact-turn wait. Pass its question
|
|
1662
|
+
and link to the owner instead of assuming the turn has completed.
|
|
1663
|
+
|
|
1664
|
+
Give the owner the question and link so they can open the thread in the app
|
|
1665
|
+
and answer. The request ID is only an opaque identifier; it grants no ability
|
|
1666
|
+
to answer or approve for the owner. After an answer, wait again on the same
|
|
1667
|
+
turn. An earlier question does not end that new wait, and an input wait does
|
|
1668
|
+
not mean the turn has completed. An `access_request` describes an outstanding
|
|
1669
|
+
boxes.dev permission request; it can outlive a turn and never ends an
|
|
1670
|
+
exact-turn wait.
|
|
1671
|
+
|
|
1558
1672
|
If an accepted child is later deleted, `threads list` retains its ID as a
|
|
1559
1673
|
`failed` entry titled **Deleted delegated thread**. Reads explain that it was
|
|
1560
1674
|
deleted, and controls return `thread_not_found`. Retrying its original start with the same idempotency key
|
|
@@ -1670,6 +1784,13 @@ be read, even while the agent is working. These stored states can lag live work
|
|
|
1670
1784
|
or change before a message arrives, so they do not guarantee idle-only delivery.
|
|
1671
1785
|
Reading status does not wake a devbox or require delegation permission.
|
|
1672
1786
|
|
|
1787
|
+
Readers with conversation access also receive `pendingInput` for a waiting
|
|
1788
|
+
agent, using the same question and owner-link fields as delegated reads.
|
|
1789
|
+
Metadata-only readers receive no pending-input details. boxes.dev permission
|
|
1790
|
+
requests are visible only for the owner's own threads. When reading through
|
|
1791
|
+
a supplied share invitation, use the returned `threadUrl` to preserve that
|
|
1792
|
+
access; the link grants no ability to answer for the owner.
|
|
1793
|
+
|
|
1673
1794
|
For known threads, fetch their metadata together instead of scanning the whole
|
|
1674
1795
|
project or reading their conversations:
|
|
1675
1796
|
|
|
@@ -1734,6 +1855,15 @@ They may lag active work and shorten long messages. They do not wake boxes,
|
|
|
1734
1855
|
mark threads read, claim links, or expose full tool logs. Without `--scope`,
|
|
1735
1856
|
the existing `list` and `read` commands still select delegated children only.
|
|
1736
1857
|
|
|
1858
|
+
Scoped preview and full JSON messages include `messageTimeMs`: the time recorded
|
|
1859
|
+
for the source message, in Unix milliseconds, or `null` when unavailable. Older
|
|
1860
|
+
services may omit the field. Continued parts of a message retain the same time.
|
|
1861
|
+
A queued message's time reflects delivery to the agent.
|
|
1862
|
+
Use message times, rather than thread `updatedAt`, when reconstructing activity;
|
|
1863
|
+
keep the returned message order. Some forked Codex threads timestamp copied messages
|
|
1864
|
+
at the fork time, so their dates do not establish when the original conversation
|
|
1865
|
+
happened.
|
|
1866
|
+
|
|
1737
1867
|
For original visible message text, add `--full --json`:
|
|
1738
1868
|
|
|
1739
1869
|
```bash
|
|
@@ -2298,6 +2428,17 @@ wakes. Listener failures therefore lose an already acknowledged webhook. Use
|
|
|
2298
2428
|
routed delivery for verification challenges or any request that needs the
|
|
2299
2429
|
application's status, headers, or response body.
|
|
2300
2430
|
|
|
2431
|
+
A routed request must receive the application's response status and headers
|
|
2432
|
+
within 10 seconds of reaching the box, or the caller gets HTTP 504. The time
|
|
2433
|
+
spent receiving the request body counts toward that limit. After that, the
|
|
2434
|
+
public-link limits in
|
|
2435
|
+
[Public app links](ports-terminal-and-runtime.md#public-app-links) apply: the
|
|
2436
|
+
connection closes after 2 minutes without data, the whole request must finish
|
|
2437
|
+
within 10 minutes of reaching the box (the 10-second wait is part of that time,
|
|
2438
|
+
not added to it), and a timeout does not guarantee that the application's work
|
|
2439
|
+
stops. For slow work, return a job ID quickly and let the caller poll its
|
|
2440
|
+
status.
|
|
2441
|
+
|
|
2301
2442
|
Project URL traffic does not wake a sleeping box or keep it awake. `list` and
|
|
2302
2443
|
`show` work without a running app. `claim`, `subscribe`, and `browser-link`
|
|
2303
2444
|
require the URL's configured port to be allowed by the project port policy and
|
|
@@ -263,6 +263,38 @@ matches every public link and Project URL, so sharing the port again does not
|
|
|
263
263
|
need another change. Do not set `allowedHosts: true`, which turns the check
|
|
264
264
|
off.
|
|
265
265
|
|
|
266
|
+
Public links apply their own HTTP time limits, whatever timeout the
|
|
267
|
+
application sets. The app must accept the connection within 10 seconds. The
|
|
268
|
+
link closes its connection to the app after 2 minutes without data, including
|
|
269
|
+
while the request is waiting for the first part of its response, so send data
|
|
270
|
+
well before then (for example, every 30 seconds). Each request must finish
|
|
271
|
+
within 10 minutes of arriving. Treat both as ceilings, not guaranteed
|
|
272
|
+
allowances: clients and uploads can have their own shorter limits. A request
|
|
273
|
+
whose response has not reached the client can fail with `Application timed out`
|
|
274
|
+
(HTTP 504), or with `Application unavailable` (HTTP 502) if the app sent only
|
|
275
|
+
its headers, which may stay buffered, so send body bytes early. A response that
|
|
276
|
+
has already reached the client is cut off instead and may keep its original
|
|
277
|
+
status code, so neither a 200 status nor a closed stream shows that the
|
|
278
|
+
operation finished. Raising the application's own timeout does not extend these
|
|
279
|
+
limits.
|
|
280
|
+
|
|
281
|
+
A timeout ends the HTTP connection but does not guarantee that the
|
|
282
|
+
application's work stops: the handler may continue and complete, or it may
|
|
283
|
+
notice the disconnect and cancel itself. Before retrying a request that is not
|
|
284
|
+
safe to repeat, check the application's own receipt or job status. If the
|
|
285
|
+
original request carried an idempotency key that the application or API
|
|
286
|
+
supports, retry with that original key rather than a new one. For work that
|
|
287
|
+
can take more than a minute or two or must not run twice, either stream or use
|
|
288
|
+
an application-owned job. To stream, send body bytes immediately, send progress
|
|
289
|
+
such as a server-sent event or line at least every 30 seconds, disable response
|
|
290
|
+
buffering in the framework and any proxy in front of it, end with an explicit
|
|
291
|
+
completion message, and finish within 10 minutes. For a job, which can also run
|
|
292
|
+
longer than 10 minutes, have the application persist it, return its ID (for
|
|
293
|
+
example, with HTTP 202), and let the client poll a status endpoint; after a
|
|
294
|
+
disconnect the client looks up the same job instead of resubmitting. The
|
|
295
|
+
application runs the job and stores its status, so keep the box awake until
|
|
296
|
+
long jobs finish.
|
|
297
|
+
|
|
266
298
|
If recovery replaces the machine, boxes.dev will revoke its old public links.
|
|
267
299
|
Share the app again on the recovered machine to get a new URL.
|
|
268
300
|
|
|
@@ -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
|
|
@@ -53,20 +53,31 @@ a saved version or a project created from it.
|
|
|
53
53
|
|
|
54
54
|
An admin can remove another member from **Team settings → Members** using the
|
|
55
55
|
member's menu. Select a remaining member as the work recipient, then choose
|
|
56
|
-
|
|
57
|
-
project
|
|
58
|
-
|
|
56
|
+
an action for every project. **Transfer threads** is the default: choose an
|
|
57
|
+
existing recipient-owned project for the conversations and attachments. Saved
|
|
58
|
+
conversations arrive under **Archived** and restore on the recipient's devboxes
|
|
59
|
+
using their credentials. The original project and machines follow Keep below.
|
|
60
|
+
**Transfer full project** moves the original machines as well. It is dangerous
|
|
61
|
+
when the former owner is untrusted: software they left behind may read future
|
|
62
|
+
code or credentials, even after access keys rotate. Each full project transfer
|
|
63
|
+
requires acknowledgement of this risk. Transferred work records its original
|
|
64
|
+
account. **Delete** uses permanent project deletion and requires confirmation
|
|
65
|
+
for each project.
|
|
59
66
|
Keep moves the project to the departing account's fresh personal team and
|
|
60
67
|
removes managed files, managed secrets, team access, and existing thread
|
|
61
68
|
sharing. Ordinary files and unmanaged environment-file content remain.
|
|
62
69
|
A kept managed project receives an independent Template box.
|
|
63
70
|
|
|
64
|
-
Sleeping boxes remain asleep during Transfer and Keep. Ownership
|
|
65
|
-
access change during removal; managed files and credentials are cleaned
|
|
66
|
-
the next wake, before the box is available. The first wake restarts the box
|
|
71
|
+
Sleeping boxes remain asleep during Transfer full project and Keep. Ownership
|
|
72
|
+
and team access change during removal; managed files and credentials are cleaned
|
|
73
|
+
up on the next wake, before the box is available. The first wake restarts the box
|
|
67
74
|
from its saved disk, preserving ordinary files and stopping old processes.
|
|
75
|
+
Thread transfer may wake a source box to archive native history; an initially
|
|
76
|
+
sleeping box returns to sleep after cleanup.
|
|
68
77
|
|
|
69
78
|
Running work stops during handoff, and automations pause for connection review.
|
|
79
|
+
Pending messages in reassigned threads require review before sending. Messages
|
|
80
|
+
with uncertain delivery retain their warning and do not replay automatically.
|
|
70
81
|
Account-specific connections require the new owner's authorization. The removed
|
|
71
82
|
account can continue using its personal team and will not automatically rejoin
|
|
72
83
|
the former team through its email domain. Remove its paid seat in Billing and
|
|
@@ -81,6 +92,8 @@ account; box preparation and the final handoff have separate progress updates.
|
|
|
81
92
|
The recipient can keep creating projects and devboxes while removal runs or
|
|
82
93
|
awaits retry. Names reserved for incoming work remain unavailable for new
|
|
83
94
|
projects and devboxes.
|
|
95
|
+
An existing project receiving threads cannot be deleted until transfer finishes;
|
|
96
|
+
other work in it can continue.
|
|
84
97
|
Team Template conversations transfer to the selected recipient, who must be
|
|
85
98
|
an admin when these conversations exist. Shared saved environments remain with
|
|
86
99
|
the team. The personal team needs its own billing setup before starting
|
|
@@ -529,7 +542,11 @@ boxes.dev GitHub connection and pull/push access. Any GitHub maintenance watch,
|
|
|
529
542
|
including a disabled watch, also requires access to the watched repository.
|
|
530
543
|
The flow presents
|
|
531
544
|
the existing connect, update-authorization, install, or grant-access action and
|
|
532
|
-
does not allocate the Template box until access is satisfied.
|
|
545
|
+
does not allocate the Template box until access is satisfied. If the member's
|
|
546
|
+
GitHub account can only read a repository, or can't reach one that boxes.dev
|
|
547
|
+
already has access to, the flow asks the member to get write access from an
|
|
548
|
+
owner of the repository's GitHub organization or account and offers a request
|
|
549
|
+
message to copy.
|
|
533
550
|
|
|
534
551
|
When creation starts, boxes.dev pins the selected filesystem version and the
|
|
535
552
|
current saved Project defaults as separate inputs. Later Team Template edits do
|
|
@@ -572,8 +589,9 @@ change. If waiting for preparation times out, the notice will say that completio
|
|
|
572
589
|
could not be confirmed and your message was not sent; it will retain your draft.
|
|
573
590
|
|
|
574
591
|
The new project is independent of later Team Template versions and save cleanup.
|
|
575
|
-
When removing a member, an admin chooses whether to transfer
|
|
576
|
-
that member keep
|
|
592
|
+
When removing a member, an admin chooses whether to transfer its threads,
|
|
593
|
+
transfer the full project, delete it, or let that member keep it under the
|
|
594
|
+
removal rules above.
|
|
577
595
|
Creating it uses a normal project slot and its
|
|
578
596
|
box uses the member's normal billing entitlement.
|
|
579
597
|
|