@boxes-dev/dvb-runtime 1.0.1113 → 1.0.1115

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/dvbd.mjs CHANGED
@@ -64830,9 +64830,9 @@ var init_sentry = __esm({
64830
64830
  uncaughtExceptionMonitorInstalled = false;
64831
64831
  currentDevboxSentryUser = null;
64832
64832
  readBuildMetadata = () => {
64833
- const rawPackageVersion = "1.0.1113";
64834
- const rawGitSha = "5c92512300006a85ac7be2bd93af7c9f48fb2799";
64835
- const rawSentryRelease = "boxes-dev-dvb@1.0.1113+5c92512300006a85ac7be2bd93af7c9f48fb2799";
64833
+ const rawPackageVersion = "1.0.1115";
64834
+ const rawGitSha = "44b7c199b316cc264c5da5d10ed4ce3c902d24dd";
64835
+ const rawSentryRelease = "boxes-dev-dvb@1.0.1115+44b7c199b316cc264c5da5d10ed4ce3c902d24dd";
64836
64836
  const packageVersion = typeof rawPackageVersion === "string" ? rawPackageVersion : void 0;
64837
64837
  const gitSha = typeof rawGitSha === "string" ? rawGitSha : void 0;
64838
64838
  const sentryRelease = typeof rawSentryRelease === "string" ? rawSentryRelease : void 0;
@@ -67383,7 +67383,7 @@ var init_packageVersion = __esm({
67383
67383
  return path8.join(process.cwd(), "dvb");
67384
67384
  };
67385
67385
  readEmbeddedPackageVersion = () => {
67386
- const raw = "1.0.1113";
67386
+ const raw = "1.0.1115";
67387
67387
  return trimVersion(raw);
67388
67388
  };
67389
67389
  readNearestPackageMetadata = (basePath) => {
@@ -280,6 +280,8 @@ title, agent settings, placement, and notification behavior. Omit `threadTitle`
280
280
  and `execution` for this target. Omit `prompt` to send the saved automation prompt.
281
281
  The automation's devbox cleanup and Slack output destinations do not apply to
282
282
  these follow-ups.
283
+ A Claude follow-up can run once its response has ended, even if a background
284
+ command is still running. The command will continue running.
283
285
  A sleeping target's box will wake if capacity is available. An awake target
284
286
  needs no additional awake slot.
285
287
 
@@ -280,16 +280,16 @@ machine you last used. Return to one of your own threads connected to a box or,
280
280
  available, the Template box when you want box controls and Files,
281
281
  Git/Review, Terminal, Browser, or Ports.
282
282
 
283
- The app menu also includes **Project settings**, **Settings...**,
284
- **Configure agents...**, **Sign Out**, update actions, and **Show Workbench**.
285
- Configure agents can save multiple Codex and Claude accounts or API keys and
283
+ The app menu also includes **Project Settings...**, **Settings...**,
284
+ **Configure Agents...**, update actions, and **Sign Out**. Configure agents can
285
+ save multiple Codex and Claude accounts or API keys and
286
286
  choose one active credential for each agent across all devboxes. Codex needs to
287
287
  restart to switch to or from an API key. While Codex is working on a devbox, it
288
288
  keeps the old credential and the desktop shows **Restart Codex** above the reply
289
289
  box. Threads stay connected and running work can still be steered or stopped,
290
290
  but new work needs to wait until the running work finishes or Codex restarts.
291
291
  Restarting stops all running Codex work on that devbox. The File menu also
292
- includes **Delete This Project**.
292
+ includes **Show Workbench** and **Delete This Project**.
293
293
 
294
294
  ## Box status
295
295
 
@@ -427,9 +427,10 @@ interrupt that work.
427
427
  Destroy and archive permanently deletes the devbox filesystem and preserves its
428
428
  eligible threads as archived cold-storage transcripts, including secondary
429
429
  threads that were already archived inside the devbox. The confirmation dialog
430
- warns about uncommitted changes, changed files, and local-only commits when that
431
- information is available. It also names the pull requests whose automatic
432
- follow-ups the devbox's threads handle. Destroying the devbox stops those
430
+ says when an agent is still working, and it warns about uncommitted changes,
431
+ changed files, and local-only commits when that information is available. It
432
+ also names the pull requests whose automatic follow-ups the devbox's threads
433
+ handle. Destroying the devbox stops those
433
434
  follow-ups, and the pull request shows them as paused until a restored or
434
435
  other thread turns them on again. As soon as the destroy starts, the devbox's
435
436
  threads move under its name in **Devboxes** → **Archived threads** on desktop
@@ -116,7 +116,7 @@ Use devbox threads for normal coding tasks.
116
116
 
117
117
  Setup asks you to connect at least one coding agent. You can connect or repair
118
118
  agent auth later from **Settings → Agents** in the desktop account menu.
119
- The macOS **Configure agents...** command opens the same section. The mobile app has the same controls under
119
+ The macOS **Configure Agents...** command opens the same section. The mobile app has the same controls under
120
120
  **Settings → Agent accounts**.
121
121
 
122
122
  Codex can be connected with ChatGPT login or an API key. Claude Code can be
@@ -169,6 +169,64 @@ moving its file, boxes.dev omits the old saved value. The member must review the
169
169
  new destination and choose **Use saved value here**, or enter a replacement.
170
170
  Other managed values continue syncing while that one is unresolved.
171
171
 
172
+ ## Loading Values Into Agents And Terminals
173
+
174
+ Managed files are ordinary files on disk, so an agent, MCP server, or terminal
175
+ command does not see their values unless something reads the file. To make a
176
+ file's values part of the environment itself, check **Load into agent and
177
+ terminal environments** in the file's editor. It is off by default and is
178
+ saved with the file's other changes.
179
+
180
+ While it is on, every box in the project adds the file's values to the
181
+ environment of Codex and Claude threads, the MCP servers those agents start,
182
+ terminals, and startup scripts. MCP settings can then refer to a value by
183
+ name instead of containing it:
184
+
185
+ - Claude Code expands `${NAME}` in `.mcp.json` and `~/.claude.json` server
186
+ settings, including `command`, `args`, `env`, `url`, and `headers`.
187
+ - Codex gives a stdio server only a few default variables plus the ones
188
+ you list, so name them in `env_vars = ["NAME"]` under
189
+ `[mcp_servers.<server>]` in `~/.codex/config.toml`. An HTTP server can use
190
+ `bearer_token_env_var = "NAME"` or `env_http_headers`.
191
+
192
+ A loaded value is a default: a name that the agent, box, or terminal already
193
+ sets keeps its own value. Some variables are never loaded, and the editor marks
194
+ rows whose names won't load:
195
+
196
+ - names that contain lowercase letters;
197
+ - names that start with `ANTHROPIC_`, `CLAUDE_`, `CODEX_`, `BOXES_`, or
198
+ `DEVBOX_`, which control agent sign-in and boxes.dev itself;
199
+ - `AWS_PROFILE`, `AWS_SDK_LOAD_CONFIG`, `GCE_METADATA_HOST`, and
200
+ `GOOGLE_CLOUD_QUOTA_PROJECT`, which the AWS and Google Cloud connections set;
201
+ - values that span several lines.
202
+
203
+ When two loaded files set the same name, the file whose path sorts first
204
+ wins. Loaded values are limited to 256 KiB in total. Files are read in path
205
+ order, and a value that would go past the limit is left out.
206
+
207
+ A box applies a change when it syncs, usually within seconds of a save or of
208
+ the box waking. New terminals, startup scripts, and new Claude threads start
209
+ with the new values. A Codex or Claude agent that is already running restarts
210
+ in the background once it is idle, with its conversations intact, and its MCP
211
+ servers start again with the new values. Codex threads on a box share one
212
+ agent, so a new Codex thread gets the change at that restart. An agent that is
213
+ working, waiting on a question, or holding queued messages or background tasks
214
+ restarts after that work finishes. Open terminals pick up changes at their
215
+ next prompt. A program already running in a terminal, including Claude Code or
216
+ Codex started there, keeps the environment it started with until you restart
217
+ it. Turning the setting off removes the values the same way.
218
+
219
+ In a Team Template, the admin chooses the setting for each file. It covers
220
+ everything at that path in managed projects, including variables members add
221
+ there. A member sees whether a Team Template file loads, and checks the box
222
+ for each file of their own. A normal project created from a Team Template
223
+ copies the setting with the file. `dvb-onbox env list` reports the setting;
224
+ it can be changed only in settings.
225
+
226
+ Loaded values are readable by every process the agent or terminal starts, the
227
+ same as the values in the file itself. Values are kept in a file on the box
228
+ that only the box user can read.
229
+
172
230
  ## Agent Commands
173
231
 
174
232
  Coding agents can list, set, and remove a project's variables with
@@ -1,13 +1,14 @@
1
1
  # Member Files
2
2
 
3
- Use this doc for questions about Team Template file requirements, member-owned
4
- configuration files, safe destinations, replacement, destination approval, or
5
- what happens at startup when a file is missing.
3
+ Use this doc for questions about Team Template file requirements, required and
4
+ optional member files, member-owned configuration files, safe destinations,
5
+ replacement, destination approval, or what happens at startup when a file is
6
+ missing.
6
7
 
7
8
  ## What Member Files Are
8
9
 
9
- A Team Template admin can require every project member to provide their own
10
- file at a fixed destination. This is useful for personal CLI configuration,
10
+ A Team Template admin can ask every project member to provide their own file
11
+ at a fixed destination. This is useful for personal CLI configuration,
11
12
  for example `$HOME/.convex/config.json`, when the tool expects a complete file
12
13
  rather than environment variables.
13
14
 
@@ -22,19 +23,23 @@ in an authorized Team Template editing session. See
22
23
  [Member-file requirements](onbox-agent-tools.md#member-file-requirements) for
23
24
  commands and revision handling.
24
25
 
25
- Every requirement is required. A member selects the local file while creating
26
- the project. The original local filename is used only in that browser view and
27
- is not saved by boxes.dev. Files may contain arbitrary bytes and can be up to
28
- 256 KiB.
29
-
30
- During project creation, files appear with required environment values under
31
- **Needed to create the project**, before the collapsed optional values. **Choose file**
26
+ Each requirement is either required or optional. New requirements are
27
+ required; the admin clears **Required** for a file that only some members
28
+ create, such as an optional local configuration file. A member selects every
29
+ required file while creating the project, and can skip an optional file and
30
+ add it later in **Project settings → Member files**. The original local
31
+ filename is used only in that browser view and is not saved by boxes.dev.
32
+ Files may contain arbitrary bytes and can be up to 256 KiB.
33
+
34
+ During project creation, required files appear with required environment
35
+ values under **Needed to create the project**. Optional files appear after the
36
+ optional values in the collapsed **Show optional** section. **Choose file**
32
37
  opens the native file picker. After reading it, the form shows the local
33
38
  filename and byte size, with **Change** and **Remove** actions.
34
39
  Reading the file does not verify its contents or credentials.
35
40
  Home destinations use `~/` in this form.
36
41
  Oversized or unreadable files show an error at that requirement. The bottom
37
- actions name missing files and link back to them.
42
+ actions name missing required files and link back to them.
38
43
 
39
44
  ## Storage And Delivery
40
45
 
@@ -46,7 +51,9 @@ destinations, while each member's bytes remain scoped to their own project.
46
51
  The devbox writes the exact uploaded bytes. Missing parent directories are
47
52
  created with owner-only access, and the file is written atomically with mode
48
53
  `0600`. A managed file owns its complete destination: local edits are replaced
49
- during the next repair.
54
+ during the next repair. Until a member saves a file, boxes.dev doesn't
55
+ write or remove anything at its destination, so a member who skips an optional
56
+ file can keep a copy they create there themselves.
50
57
 
51
58
  Delivery runs when a devbox is created or wakes, when the saved file changes,
52
59
  and during periodic repair. Deleting or modifying the local copy therefore
@@ -60,9 +67,10 @@ the bytes only after boxes.dev has bound it to the exact member and project.
60
67
  ## Startup And Changes
61
68
 
62
69
  A missing member file, or one awaiting destination approval, does not block a
63
- startup script or a new Codex or Claude session. They start without it, and the
64
- desktop and mobile apps warn the member until they add it; either app's
65
- Project settings can upload it. A file that cannot be written
70
+ startup script or a new Codex or Claude session. They start without it. For a
71
+ required file, the desktop and mobile apps warn the member until they add it;
72
+ either app's Project settings can upload it. A missing optional file shows as
73
+ optional there, without a warning. A file that cannot be written
66
74
  safely does block them until it is fixed, and Project settings explains what
67
75
  the member must do. An agent session that is already running is not stopped
68
76
  when a requirement or file changes.
@@ -73,9 +81,9 @@ saved bytes to the new destination automatically. The member must explicitly
73
81
  choose **Use my saved file at this new destination** or upload a replacement.
74
82
  Changing instructions alone does not require approval.
75
83
 
76
- Members can replace or remove their own saved file. Removing it makes the
77
- required item incomplete, and new devboxes and agent sessions start without the
78
- file until a replacement is saved. Each devbox removes its managed destination
84
+ Members can replace or remove their own saved file. Removing a required file
85
+ makes that requirement incomplete, and new devboxes and agent sessions start
86
+ without the file until a replacement is saved. Each devbox removes its managed destination
79
87
  at the next sync; a sleeping devbox does so after it wakes. Removal does not
80
88
  delete extra copies elsewhere or revoke credentials a process has already read.
81
89
  Downloading the centrally saved bytes requires a recent confirmation with the
@@ -236,10 +236,12 @@ Failed Codex messages and their attachment names also appear in the scrollable
236
236
  transcript. Use **Restore** to return the message and attachments to the composer
237
237
  alongside your current draft, or the dismiss button to remove the failed message.
238
238
 
239
- Codex question forms appear inline with all questions visible together. For a
240
- single choice question, tapping an option sends it immediately. For written
241
- answers or multiple questions, use the form's submit button. Unfinished answers
242
- stay in place when you scroll away and back. If Codex finishes its turn before
239
+ Codex and Claude questions appear inline one at a time, with arrows at the top
240
+ of the form to move between questions. Tapping an option answers the question
241
+ and moves to the next one; for a written answer, type it and tap **Continue**.
242
+ The answers are sent from the last question (Claude first returns to any
243
+ question still unanswered). Unfinished Codex answers stay in place when you
244
+ scroll away and back. If Codex finishes its turn before
243
245
  you send an asynchronous answer, your edited answer returns to the composer.
244
246
 
245
247
  A pending Codex question or form can appear before the phone connects to the