@boxes-dev/dvb-runtime 1.0.1012 → 1.0.1014

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 CHANGED
@@ -101146,8 +101146,8 @@ var init_otel = __esm({
101146
101146
  return trimmed && trimmed.length > 0 ? trimmed : void 0;
101147
101147
  };
101148
101148
  readBuildMetadata = () => {
101149
- const rawPackageVersion = "1.0.1012";
101150
- const rawGitSha = "184a335b89e66a5c47fdc4b334d88b2aff043dbb";
101149
+ const rawPackageVersion = "1.0.1014";
101150
+ const rawGitSha = "ad97cd572234e687a71892488a6e009a3298c247";
101151
101151
  const packageVersion = typeof rawPackageVersion === "string" ? rawPackageVersion : void 0;
101152
101152
  const gitSha = typeof rawGitSha === "string" ? rawGitSha : void 0;
101153
101153
  return { packageVersion, gitSha };
@@ -133553,9 +133553,9 @@ var init_sentry = __esm({
133553
133553
  uncaughtExceptionMonitorInstalled = false;
133554
133554
  currentDevboxSentryUser = null;
133555
133555
  readBuildMetadata2 = () => {
133556
- const rawPackageVersion = "1.0.1012";
133557
- const rawGitSha = "184a335b89e66a5c47fdc4b334d88b2aff043dbb";
133558
- const rawSentryRelease = "boxes-dev-dvb@1.0.1012+184a335b89e66a5c47fdc4b334d88b2aff043dbb";
133556
+ const rawPackageVersion = "1.0.1014";
133557
+ const rawGitSha = "ad97cd572234e687a71892488a6e009a3298c247";
133558
+ const rawSentryRelease = "boxes-dev-dvb@1.0.1014+ad97cd572234e687a71892488a6e009a3298c247";
133559
133559
  const packageVersion = typeof rawPackageVersion === "string" ? rawPackageVersion : void 0;
133560
133560
  const gitSha = typeof rawGitSha === "string" ? rawGitSha : void 0;
133561
133561
  const sentryRelease = typeof rawSentryRelease === "string" ? rawSentryRelease : void 0;
@@ -138757,7 +138757,7 @@ var init_packageVersion = __esm({
138757
138757
  return path17.join(process.cwd(), "dvb");
138758
138758
  };
138759
138759
  readEmbeddedPackageVersion = () => {
138760
- const raw = "1.0.1012";
138760
+ const raw = "1.0.1014";
138761
138761
  return trimVersion(raw);
138762
138762
  };
138763
138763
  readNearestPackageMetadata = (basePath) => {
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.1012";
96332
- const rawGitSha = "184a335b89e66a5c47fdc4b334d88b2aff043dbb";
96331
+ const rawPackageVersion = "1.0.1014";
96332
+ const rawGitSha = "ad97cd572234e687a71892488a6e009a3298c247";
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.1012";
128628
- const rawGitSha = "184a335b89e66a5c47fdc4b334d88b2aff043dbb";
128629
- const rawSentryRelease = "boxes-dev-dvb@1.0.1012+184a335b89e66a5c47fdc4b334d88b2aff043dbb";
128627
+ const rawPackageVersion = "1.0.1014";
128628
+ const rawGitSha = "ad97cd572234e687a71892488a6e009a3298c247";
128629
+ const rawSentryRelease = "boxes-dev-dvb@1.0.1014+ad97cd572234e687a71892488a6e009a3298c247";
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.1012";
130829
+ const raw = "1.0.1014";
130830
130830
  return trimVersion(raw);
130831
130831
  };
130832
130832
  readNearestPackageMetadata = (basePath) => {
@@ -0,0 +1,44 @@
1
+ # Development Environment Validation
2
+
3
+ Use this reference for the environment setup or repair requested in the current
4
+ thread. Follow that flow's setup plan, repository documentation, credential
5
+ rules, and completion instructions. For Team Template work, first select the
6
+ direct or remote editing workflow in
7
+ [On-box agent tools](onbox-agent-tools.md#team-template-commands).
8
+
9
+ ## Verify Persistent Configuration
10
+
11
+ Check the required tool versions and dependency/build steps. An installed
12
+ executable may not be selected by the agent's commands, and dependency
13
+ installation may not build the local packages those commands need.
14
+
15
+ After configuring tool activation, verify versions and a representative
16
+ project command from a fresh agent command without manually exporting PATH,
17
+ sourcing an rc file, or adding other temporary setup-only overrides. Check a
18
+ fresh terminal too when terminal use is in scope: interactive terminals and
19
+ agent commands may initialize differently. Keep environment selection that is
20
+ part of the project's normal command; verify that the next user can run that
21
+ command without repeating an unrecorded workaround.
22
+
23
+ For remote Team Template editing, perform these checks on the target editing
24
+ box. Success on the source project's Template box does not verify the target.
25
+
26
+ ## Verify Required Service Startup
27
+
28
+ Check how the required services start through the documented development
29
+ command or configured startup behavior. A manually started database on the
30
+ Team Template editing machine does not establish readiness in a new project;
31
+ the Team Template save flow cleans and cold-boots that machine before capture.
32
+
33
+ A script file on disk is not a registered startup setting. Maintenance and
34
+ destination startup serve different purposes. Read back settings you apply,
35
+ and report any remaining configuration step. Use the applicable project mode's
36
+ lifecycle instructions; see
37
+ [Team Templates](team-template.md#when-a-new-devbox-is-created).
38
+
39
+ ## Report Readiness For The Requested Work
40
+
41
+ Report what passed, failed, or remains unverified, with the commands and any
42
+ required user actions. A passing test subset does not establish that full
43
+ typechecking, builds, or local development works. Record memory limitations
44
+ and whether startup on a newly created machine was actually exercised.
@@ -218,6 +218,20 @@ Integrations → GitHub or Account settings. Push or Publish is shown only when
218
218
  Git/Review can identify a supported destination, or disabled with a reason when
219
219
  the repository is relevant but currently blocked.
220
220
 
221
+ You can connect the same GitHub account to multiple boxes.dev accounts, such
222
+ as your personal and work accounts. Connect GitHub separately from each
223
+ boxes.dev account; their connection settings and credentials remain separate.
224
+ To switch to a different GitHub account within one boxes.dev account,
225
+ disconnect the current GitHub account first.
226
+
227
+ If you revoke the boxes.dev App's authorization on GitHub, reconnect it in
228
+ each affected boxes.dev account. Removing or suspending an App installation
229
+ affects that installation's repositories, while access to other installations
230
+ remains available. Restore repository access from **Manage repos** when needed.
231
+ boxes.dev refreshes expiring credentials automatically before they expire.
232
+ If the refresh credential has also expired, reconnect GitHub. Temporary GitHub
233
+ outages are retried without treating your authorization as revoked.
234
+
221
235
  For a project created from GitHub with automatic access, fetch, pull, and push
222
236
  use the connected user's credential after boxes.dev verifies that the exact
223
237
  repository was selected for the project and the user still has write access.
@@ -302,10 +316,17 @@ but cannot add another repository at the project root.
302
316
 
303
317
  ## Git Author Identity
304
318
 
305
- Account settings has one **Git identity** name and email that boxes.dev can
306
- carry to the member's ordinary Template boxes and all assigned devboxes. Saving it is explicit:
307
- boxes.dev does not infer or save commit authorship from the account profile,
308
- login email, or connected GitHub account.
319
+ By default, boxes.dev uses your connected GitHub account's name and private
320
+ no-reply email for Git commits on your ordinary Template boxes and devboxes.
321
+ If your GitHub profile has no name, it uses your GitHub username. This default
322
+ follows your connected GitHub account without saving an account override.
323
+
324
+ To choose a different name and email, edit **Git identity** in Account settings
325
+ and save, or edit the fields during Team Template setup. Only an explicit edit
326
+ will save an override; continuing setup with the displayed default will keep
327
+ using GitHub. A saved override will stay the same when you reconnect GitHub or
328
+ change your login profile. Without a connected GitHub account, enter a name
329
+ and email or use your project's Git configuration.
309
330
 
310
331
  The Account value is a fallback. A global identity imported during project
311
332
  setup or later written to `~/.gitconfig` wins across that machine, and a
@@ -318,6 +339,7 @@ Edits reach active machines automatically. A sleeping machine stays asleep and
318
339
  uses the latest value after its next normal wake. **Stop supplying identity**
319
340
  removes only the boxes.dev fallback; it does not erase imported global,
320
341
  repository-local, signing, credential, alias, hook, or other Git configuration.
342
+ An explicitly cleared identity will stay off until you configure it again.
321
343
 
322
344
  ## GitHub CLI In Terminals And Agents
323
345
 
@@ -458,10 +480,20 @@ the agent will stop and explain why instead. The automatic turn will not merge
458
480
  or force-push the pull request, delete its branch, rerun workflows, or reply to
459
481
  or resolve review comments.
460
482
 
483
+ When the pull request merges, boxes.dev will also send that agent a final
484
+ notice so it can account for the merge in future work. This may wake the
485
+ machine and will wait behind any active agent turn. The notice will not ask the
486
+ agent to edit files or change branches. Paused follow-ups will still receive
487
+ this notice, provided the original agent thread remains available; archived or
488
+ deleted threads will not receive it. Turning follow-ups off will also turn off
489
+ the merge notice. Closing a pull request without merging will end follow-ups
490
+ silently.
491
+
461
492
  Bot feedback includes only reviews and comments that GitHub identifies as
462
493
  bot-authored. Comments from people will not start an automatic follow-up. Only
463
- one agent can handle follow-ups for a pull request at a time; turning them on
464
- from another agent will show the current agent and ask you to move the job.
494
+ one agent per boxes.dev account can handle follow-ups for a pull request at a
495
+ time; turning them on from another agent will show the current agent and ask
496
+ you to move the job.
465
497
 
466
498
  Use **Edit follow-ups** to change the selected events or turn the feature off.
467
499
  After three automatic follow-ups without a healthy pull request, boxes.dev will
@@ -43,6 +43,9 @@ Use this terminology consistently:
43
43
  copied-data boundaries.
44
44
  - `template-box-environment.md`: the Template box machine environment, baseline
45
45
  development tools, setup constraints, local-run verification, and snapshots.
46
+ - `environment-setup-validation.md`: shared validation guidance for ordinary
47
+ project and Team Template environment setup, including fresh agent commands,
48
+ persistent configuration, service startup, and readiness reporting.
46
49
  - `managed-environment-files.md`: centrally managed dotenv files, initial
47
50
  import, managed-prefix ownership, Team Template Team/member values,
48
51
  reveal/export, outages, snapshots, security boundaries, and limits.
@@ -105,9 +108,12 @@ Use this terminology consistently:
105
108
 
106
109
  ## Context Guidance
107
110
 
108
- If the user is in the setup thread, assume they are probably on the Template box
109
- and may be learning boxes.dev for the first time. Prefer setup, Template box,
110
- and new-user guidance.
111
+ For a setup thread, use its task and current box role to choose the guidance.
112
+ Ordinary project setup uses the project's Template box; a Team Template editor
113
+ thread runs directly on its editing machine, while an associated ordinary
114
+ Template box can operate on that machine remotely. Prefer setup and new-user
115
+ guidance for ordinary project onboarding, and Team Template guidance for shared
116
+ environment authoring.
111
117
 
112
118
  If the user is on a devbox thread, assume they are doing task work. Prefer
113
119
  devbox, file transfer, ports, git, testing, and completion guidance.
@@ -159,8 +159,9 @@ current runtime.
159
159
 
160
160
  ## Devbox Actions
161
161
 
162
- Mobile shows devbox status and lightweight Git-change counts on devbox rows and
163
- devbox pills. From a devbox row or devbox group you can:
162
+ Mobile thread lists show Git-change counts inline and a live devbox status dot
163
+ at the right, matching desktop. Sleeping devboxes show a timestamp in that
164
+ space. From a devbox row or devbox group you can:
164
165
 
165
166
  - start another thread on the same devbox;
166
167
  - pin or unpin the devbox;
@@ -232,8 +233,10 @@ Mobile settings include:
232
233
  - account deletion.
233
234
 
234
235
  Someone opening your invite link can sign up with Google in their phone
235
- browser. After signup, they can open the web app to manage their team, or
236
- download the Mac app on their computer to set up a local project.
236
+ browser. After signing up on a phone, they will see that setup happens on
237
+ their Mac, where to find the setup steps in their email, and a link to install
238
+ the mobile app. Signing up on a computer continues straight to first-project
239
+ setup in the web app.
237
240
 
238
241
  Thread text size defaults to **Medium** for transcript and message text on this
239
242
  device. Choose **Compact**, **Medium**, or **Large** in **Settings → Appearance**.
@@ -29,9 +29,11 @@ and permission-request commands still enforce the source box, thread, owner,
29
29
  and current setting.
30
30
 
31
31
  The Team Template commands are the exception to the settings model. Their
32
- skill can be present on a project Template box even when it has no Team
33
- Template access. The exact active editing association described below is the
34
- authority, and an unassociated box receives no targets.
32
+ skill is available in Team Template editing sessions and can also be present
33
+ on a project Template box without Team Template access. Direct editing uses
34
+ the current editing session; remote work from an ordinary Template box needs
35
+ the exact active association described below. An unassociated source box
36
+ receives no remote targets.
35
37
 
36
38
  ## Current Box Role
37
39
 
@@ -220,9 +222,26 @@ stable structured result.
220
222
 
221
223
  The command creates one request for the exact managed thread and source box,
222
224
  then waits up to ten minutes while the owner sees **Allow** and **Not now** in
223
- boxes.dev. **Allow** changes the existing persistent Agent permission for every
224
- agent on that source box until the owner turns it off; it is not a one-operation
225
- grant. The command cannot answer its own request or affect another box.
225
+ boxes.dev. By default, **Allow** changes the existing persistent Agent permission
226
+ for every agent on that source box until the owner turns it off; it is not a
227
+ one-operation grant. The owner chooses the scope; an agent cannot answer its own
228
+ request.
229
+
230
+ For folder access, thread titles, and creating devboxes and threads, the owner
231
+ can choose **All my devboxes in this project** before selecting **Allow**.
232
+ This will enable the project's shared permission and make the requesting box
233
+ use it. All existing and future devboxes without an individual override will
234
+ inherit that setting. Other devboxes will keep their explicit allow or deny
235
+ overrides. The choice is personal to the owner's
236
+ project, including projects created from a Team Template; it will not change
237
+ teammates' permissions. Template-only permissions keep their existing scope.
238
+
239
+ Change a box's override through its **Agent permissions** control, or choose
240
+ **Use project setting** to restore inheritance. Change shared access under
241
+ **Agent permissions for this project** in Project settings. Turning off a project
242
+ permission revokes it for every box that inherits it; explicit box overrides
243
+ remain in effect. Grants saved before project inheritance remain individual
244
+ overrides until you choose **Use project setting**.
226
245
 
227
246
  Run the request once and wait. `granted` and `already_granted` are successful;
228
247
  `denied`, `expired`, and `permission_request_pending` are non-successful
@@ -250,10 +269,10 @@ Users can independently enable **Update thread titles** from the **Agent
250
269
  permissions** control in an owned Codex or Claude thread header. That header
251
270
  control is where a box's live permissions are edited, for the Template box and
252
271
  devboxes alike. The permission applies to agents on that exact box and does
253
- not enable delegated devbox or thread creation. A new devbox starts with the
254
- project's default for this permission, set under **Agent permissions for new
255
- devboxes** in Project settings; the default is off unless the
256
- project owner changes it, and changing it does not affect existing devboxes.
272
+ not enable delegated devbox or thread creation. Boxes without an override use
273
+ the shared permission under **Agent permissions for this project** in Project
274
+ settings. It is off unless the owner changes it; changes affect existing and
275
+ future boxes that use the project setting.
257
276
 
258
277
  When enabled, the agent can replace the current thread's manual title override:
259
278
 
@@ -307,13 +326,11 @@ A user can allow agents on one exact Template box or devbox to create delegated
307
326
  threads. The setting is off by default and applies to every agent on that source
308
327
  box. Users change **Create devboxes and threads** from the **Agent permissions**
309
328
  control in the thread header, which appears on any thread running on that box.
310
- Under **Agent permissions for new devboxes** in a project's Project settings,
311
- users can opt in to having every new devbox they or an agent creates in that
312
- project start with the permission enabled. The project default is off, is
313
- stamped only when the devbox is created, and never changes an existing box. A
314
- new thread on the same box uses that box's current live permission. A new
315
- devbox uses the project default rather than copying the source box's live
316
- permission.
329
+ Under **Agent permissions for this project** in Project settings, users can
330
+ enable the permission for all their existing and future devboxes without an
331
+ override. The shared setting is off by default. A new thread on the same box
332
+ uses that box's effective permission. A new devbox inherits the project's live
333
+ setting, and later project changes apply until the user sets a box override.
317
334
 
318
335
  The start request is the authoritative check. When delegation is off, it fails
319
336
  with `delegation_disabled` without creating a thread or devbox and names the
@@ -562,12 +579,12 @@ for each source box under **Agent permissions**:
562
579
  - **Move to folders and create folders** includes move access and permits
563
580
  creation.
564
581
 
565
- A new devbox starts at the project's folder-access default, set under **Agent
566
- permissions for new devboxes** in Project settings; that default is
567
- **No folder access** unless the project owner changes it, and changing it does
568
- not affect existing boxes. Folder access belongs to the source box, not a
569
- thread: a new thread on the same box uses that box's current folder access, but
570
- the source box's permission does not transfer to a newly created devbox. The
582
+ A devbox without an override inherits the project's live folder access under
583
+ **Agent permissions for this project** in Project settings. The shared setting
584
+ is **No folder access** unless the owner changes it; changes apply to existing
585
+ and future inheriting boxes. Folder access belongs to the source box, not a
586
+ thread: a new thread on the same box uses that box's effective folder access,
587
+ while a new devbox inherits the project setting. The
571
588
  current source box determines the project; there is no project flag or project
572
589
  inventory command.
573
590
 
@@ -721,6 +738,51 @@ the file is missing, run the ordinary OAuth flow unchanged.
721
738
 
722
739
  ## Team Template Commands
723
740
 
741
+ ### Choose the execution mode
742
+
743
+ Run `dvb-onbox box status --json` before choosing a workflow:
744
+
745
+ - `team_template_edit_box`: the agent runs directly on the Team Template
746
+ editing machine. Use **Work directly on a Team Template editing box** below.
747
+ - `template_box`: local shell commands affect an ordinary project's Template
748
+ box. To edit an associated Team Template, use **Work on a Team Template from
749
+ an ordinary Template box**. To create a new definition from the current
750
+ project, use **Create a Team Template from this project**.
751
+ - `devbox`: local edits affect only this devbox. These creation and remote
752
+ editing commands require an ordinary Template box; do not treat this devbox
753
+ as the shared template.
754
+
755
+ Skill availability is not proof of an editing association. If role inspection
756
+ fails, report the command's error and use only the operations whose target is
757
+ established; do not interpret an unavailable role as proof that the user needs
758
+ to reconnect. Preparing an existing template does not require creating another
759
+ definition.
760
+
761
+ For environment setup or repair in either editing mode, read
762
+ [Development environment validation](environment-setup-validation.md).
763
+
764
+ ### Work directly on a Team Template editing box
765
+
766
+ Codex and Claude threads opened directly in the Team Template editor execute
767
+ on its current editing machine. Ordinary file and shell tools operate on that
768
+ checkout. Use the actual repository paths there; do not use remote `exec` or
769
+ `push` commands to reach the machine you already occupy.
770
+
771
+ This editing machine is not an ordinary project's Template box. Use
772
+ `dvb-onbox project maintenance get|apply` for its Team Template maintenance
773
+ policy and the **Member-file requirements** commands for member-file
774
+ definitions. Ordinary project setup completion, project lifecycle commands,
775
+ and `dvb-onbox snapshot` are not the Team Template save workflow. Configure
776
+ startup behavior in the Team Template's **When a new devbox is created** card
777
+ and use the editor's save flow when the user has requested publication. See
778
+ [Team Templates](team-template.md) for the editing lifecycle and project modes.
779
+
780
+ Saving this checkout cleans and cold-boots the editing machine before capturing
781
+ the saved version. This differs from **Create a Team Template from this
782
+ project**, which starts with clean clones and does not copy the source
783
+ project's home directory. Keep personal credentials out of the shared authored
784
+ environment; do not assume arbitrary home files are excluded.
785
+
724
786
  ### Member-file requirements
725
787
 
726
788
  An admin can list, add, update, and remove the files members need to provide for
@@ -941,14 +1003,14 @@ release pipeline. Requested member project creation becomes active only after
941
1003
  the first saved release is eligible. `edit-box discard` is only for the
942
1004
  unsaved draft created through this path.
943
1005
 
944
- ### Work on an existing Team Template checkout
1006
+ ### Work on a Team Template from an ordinary Template box
945
1007
 
946
- While editing a Team Template, a team admin can open the editor's **Agent**
947
- pane, choose Codex or Claude, and select one of their project Template boxes.
948
- boxes.dev creates an ordinary thread on that selected Template box and gives
949
- the box access to this exact Team Template editing session. Agents and other
950
- processes on the selected box can use that access; it is source-box access, not
951
- a permission limited to the one visible chat.
1008
+ This section applies to an agent on an ordinary project's Template box with an
1009
+ active association to a Team Template editing session, including one created
1010
+ through the creation workflow above. It does not describe a thread running
1011
+ directly in the Team Template editor. Agents and other processes on the
1012
+ associated source box can use that access; it is source-box access, not a
1013
+ permission limited to one visible chat.
952
1014
 
953
1015
  The agent still runs on the project Template box. Ordinary shell commands read
954
1016
  and change that project's files. Team Template work goes through the commands
@@ -966,13 +1028,12 @@ dvb-onbox team-template push \
966
1028
  --destination /home/boxes/file-in-team-template
967
1029
  ```
968
1030
 
969
- There is no persistent toggle for access to an existing edit checkout. Access begins when the admin starts the
970
- Agent-pane chat and remains attached to that editing session across pane
971
- switches, desktop reloads, and app closure. It ends when the admin chooses
972
- **Stop agent**, saves, discards, loses the editing session, or another
973
- lifecycle event closes the checkout. The ordinary Codex or Claude thread stays
974
- in the source project afterward, but it cannot list or reach the ended editing
975
- session. Starting a later editing session requires a new Agent-pane association.
1031
+ There is no persistent toggle for access to an existing edit checkout. The
1032
+ association belongs to that editing session and can survive desktop reloads
1033
+ and app closure. Access ends when the association is stopped, the checkout is
1034
+ saved or discarded, or its editing authority is lost. The ordinary Codex or
1035
+ Claude thread stays in the source project afterward, but cannot list or reach
1036
+ the ended editing session. A later checkout needs its own active association.
976
1037
 
977
1038
  `exec` is noninteractive, receives no stdin, and is limited to 120 seconds and
978
1039
  1 MiB for each output stream. Optional `--timeout-seconds`,
@@ -209,13 +209,18 @@ unavailable.
209
209
  ## Runtime Usage And Activity
210
210
 
211
211
  When live metrics are available, the titlebar can show CPU and memory usage.
212
- Memory usage excludes file cache when boxes.dev can identify it. Hover for more
213
- detail about CPU, memory, disk, and when the sample was updated.
212
+ Memory usage covers the whole machine, including containers and system services,
213
+ and accounts for memory the system can reclaim. Hover to see available memory,
214
+ CPU and disk details, and when the sample was updated. While a devbox is waiting
215
+ for a service update, its tooltip may show **Workload memory** instead, which
216
+ covers only the processes managed by boxes.dev.
214
217
 
215
218
  Click the usage indicator to open Activity. Activity lists processes inside the
216
219
  selected runtime, with command, CPU, memory, PID, and owner labels when
217
- available. Activity rows show per-process memory, so row totals may differ from
218
- the titlebar summary. You can sort by CPU or memory.
220
+ available. Activity's **Workload memory** total covers that workload, while the
221
+ titlebar shows the whole machine. Per-process memory figures may also include
222
+ shared memory, so the rows do not necessarily add up to either total. You can
223
+ sort by CPU or memory.
219
224
 
220
225
  Activity can terminate a process. If it keeps running after terminate, the UI
221
226
  can offer Force kill. Use these actions only when you understand what the
@@ -144,12 +144,39 @@ time, subject to awake devbox capacity. If Slack retries the same event,
144
144
  boxes.dev reuses the already linked automation run instead of starting a
145
145
  duplicate.
146
146
 
147
- Slack receives a started reply with a link to the boxes.dev thread. When a
147
+ By default, Slack receives a started reply with a link to the boxes.dev thread. When a
148
148
  teammate starts a thread in your workspace, the reply names you and boxes.dev
149
149
  sends you a direct message with links to the source Slack message and new
150
150
  boxes.dev thread. If final Slack replies are enabled, boxes.dev posts the
151
151
  agent's final answer back into the same Slack thread or DM.
152
152
 
153
+ To return to the original Slack conversation from the desktop workbench, click
154
+ the Slack icon beside the thread title. Hover over it to see **Open Slack thread**.
155
+
156
+ ## Choose What Appears In Slack
157
+
158
+ In the automation editor, **What should boxes.dev post in the Slack thread?**
159
+ controls reactions, started messages, attachment warnings, follow-up
160
+ confirmations, and replies when a run ends. Choose each separately for
161
+ **Internal** conversations and **Slack Connect** channels. Use **All** or
162
+ **None** above a column to change that audience together, then adjust individual
163
+ checkboxes. For quiet customer channels, choose **None** under **Slack Connect**.
164
+
165
+ **Include the full agent response** applies when replies at the end of a run
166
+ are enabled. Leave it off for a short status and link. It starts off for Slack
167
+ Connect. Turning off the parent reply keeps the full-response choice for later.
168
+
169
+ The location menu still decides where new runs can start. The Slack Connect
170
+ column appears when that location can include shared channels; hiding the
171
+ column keeps its saved choices. Attachment warnings can remain on even when
172
+ started messages or follow-up confirmations are off.
173
+
174
+ Changes apply to new Slack threads. Existing linked threads keep the choices
175
+ they started with. These settings control automatic activity for this
176
+ automation; help and replies before boxes.dev can identify an automation are
177
+ separate. Turning activity off does not send replacement DMs. The existing DM
178
+ to an owner when a teammate starts work in their workspace is unchanged.
179
+
153
180
  ## Follow-Ups And Controls
154
181
 
155
182
  After a Slack request starts a boxes.dev thread, mention `@boxes.dev` again in
@@ -167,7 +194,8 @@ Use Slack controls in the linked thread:
167
194
  - `@boxes.dev !cancel` cancels queued Slack follow-ups when possible.
168
195
 
169
196
  If the linked devbox is sleeping, boxes.dev may queue the follow-up while the
170
- runtime wakes. If capacity is full, Slack replies with guidance.
197
+ runtime wakes. If capacity is full, Slack replies with guidance when follow-up
198
+ confirmations are enabled.
171
199
 
172
200
  ## Slack Files
173
201
 
@@ -191,8 +219,9 @@ Limits and rules:
191
219
  omitted.
192
220
 
193
221
  An omitted file does not stop an otherwise valid request or linked follow-up.
194
- boxes.dev continues with every file that imported successfully, explains the
195
- omission in Slack, and tells the agent which intended input was not delivered.
222
+ boxes.dev continues with every file that imported successfully and tells the
223
+ agent which intended input was not delivered. It also explains the omission
224
+ in Slack when attachment warnings are enabled.
196
225
  If the work depends on an omitted file, attach it manually in the boxes.dev
197
226
  thread.
198
227
 
@@ -209,11 +238,10 @@ Slack integration home to reach that editor.
209
238
  Slack-triggered automations reply to their original Slack thread or DM when
210
239
  final replies are enabled.
211
240
 
212
- In a channel shared with another organization, boxes.dev replies with only a
213
- link to the finished boxes.dev thread. To let the agent's full response and
214
- failure text appear there too, turn on **Also post the full response in Slack
215
- Connect channels** in the automation's editor. That setting starts off, and it
216
- does not change replies in your own workspace's channels and DMs.
241
+ In a channel shared with another organization, enabled completion replies
242
+ default to a short status and link. To include the agent's response and failure
243
+ text, turn on **Include the full agent response** in the **Slack Connect**
244
+ column. The **Internal** column controls replies in your own workspace.
217
245
 
218
246
  Manual, scheduled, and API automations can separately send selected events to
219
247
  Slack channels or linked-user DMs. Those output destinations can receive final
@@ -30,6 +30,11 @@ and install only the missing dependencies the project needs.
30
30
 
31
31
  ## Development-Environment Setup
32
32
 
33
+ For setup and repairs, follow
34
+ [Development environment validation](environment-setup-validation.md) alongside
35
+ the current thread's setup plan. It covers persistent tool activation, fresh
36
+ agent and terminal checks, service startup, and reporting unfinished work.
37
+
33
38
  Treat Template box setup as environment work, not application feature work.
34
39
  Read the repository's own documentation and configuration, determine the
35
40
  relevant run path, and use the package manager and toolchain the project
@@ -243,7 +243,14 @@ a command such as `codex mcp add <name> --url <url>` or `claude mcp add
243
243
  --transport http <name> <url>` in a Template box or devbox creates the central
244
244
  current-project connection and continues authorization through the desktop app
245
245
  or the shown local-computer instructions. It does not create a separate
246
- machine-only copy. Unsupported transports and options, including local `stdio`,
246
+ machine-only copy. To enable both agents, run each agent's setup command with
247
+ the same name, URL, and authentication details, including any API-key headers.
248
+ The second command will add its agent to the existing project connection;
249
+ repeating either command will keep the existing connection and sign-in. OAuth
250
+ still requires authorization for each agent. For an **All projects** connection
251
+ or different settings under the same name, use the existing row's agent button
252
+ in **Integrations → MCPs**, or choose another name for a separate connection.
253
+ Unsupported transports and options, including local `stdio`,
247
254
  legacy SSE, and custom OAuth clients, continue through the native agent command
248
255
  and remain **Template-managed**. Run those commands on the Template box and take
249
256
  a snapshot if future devboxes need that local setup.
@@ -468,14 +475,21 @@ An idle thread starts normally with either preference. Once Claude accepts a
468
475
  steer, it cannot be edited or deleted as a waiting Queue message.
469
476
 
470
477
  The desktop and mobile composers also stay available while Codex or Claude
471
- Code is starting, reconnecting, or preparing a new fork. Messages sent during
472
- that wait appear as regular queued bubbles and send automatically in order once
473
- the agent is ready. Supported images and files stay attached to their queued
474
- message. boxes.dev stores waiting messages before handing them to the runtime,
475
- so delivery does not depend on keeping the original composer open. If startup
476
- or connection fails, messages that have not reached the runtime return to the
477
- composer as one draft, separated by newlines, with attachments restored when
478
- the current client supports them.
478
+ Code is starting, reconnecting, or preparing a new fork. On desktop, sending to
479
+ an existing thread on a sleeping box will wake the box and use the same queue.
480
+ Messages sent during that wait appear as regular queued bubbles and send
481
+ automatically in order once the agent is ready. Supported images and files stay
482
+ attached to their queued message. boxes.dev stores waiting messages before
483
+ handing them to the runtime, so delivery after server receipt does not depend
484
+ on keeping the app open.
485
+ Keep the app open until any attachment uploads finish and the message reaches
486
+ the server; messages saved only on your device will resume when you reopen
487
+ their thread. If startup or connection fails, messages that have not reached
488
+ the runtime return to the composer as one draft, separated by newlines, with
489
+ attachments restored when the current client supports them. Use **Stop** to
490
+ return waiting messages to your draft, including while attachments upload.
491
+ If you quit before an upload finishes, you may need to attach the files again;
492
+ boxes.dev will name any attachments it couldn't restore.
479
493
 
480
494
  If a direct Claude Code message fails after leaving the composer, its failed
481
495
  bubble can be deleted from the live tail. When boxes.dev can prove that Claude
@@ -276,9 +276,11 @@ recreated from git, agent output, or local notes.
276
276
  ## Git Commit Uses The Wrong Author
277
277
 
278
278
  Open Account settings to inspect or edit the boxes.dev **Git identity**
279
- fallback. If Account says a Template box or devbox could not be updated, use
280
- **Retry**. Active machines retry immediately; a sleeping machine is not woken
281
- and retries on its next normal wake.
279
+ fallback. Unless you saved an override, it comes from your connected GitHub
280
+ account's name and private no-reply email. Save an edit here if you prefer
281
+ another commit identity. If Account reports a failed update for a saved
282
+ override, use **Retry**. GitHub defaults retry automatically. Sleeping
283
+ machines stay asleep and retry on their next normal wake.
282
284
 
283
285
  An imported or later-written `~/.gitconfig` identity intentionally overrides
284
286
  the Account fallback for that machine. A repository-local identity overrides
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@boxes-dev/dvb-runtime",
3
- "version": "1.0.1012",
3
+ "version": "1.0.1014",
4
4
  "type": "module",
5
5
  "license": "UNLICENSED",
6
6
  "imports": {
@@ -77,5 +77,5 @@
77
77
  "e2b": "^2.18.0",
78
78
  "ink-testing-library": "^4.0.0"
79
79
  },
80
- "devboxReleasedAt": "2026-09-18T19:55:09Z"
80
+ "devboxReleasedAt": "2026-09-20T22:40:28Z"
81
81
  }