@boxes-dev/dvb-runtime 1.0.1070 → 1.0.1071

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
@@ -69726,9 +69726,9 @@ var init_sentry = __esm({
69726
69726
  uncaughtExceptionMonitorInstalled = false;
69727
69727
  currentDevboxSentryUser = null;
69728
69728
  readBuildMetadata = () => {
69729
- const rawPackageVersion = "1.0.1070";
69730
- const rawGitSha = "da013a8b246bdf050f327d914a36019408441924";
69731
- const rawSentryRelease = "boxes-dev-dvb@1.0.1070+da013a8b246bdf050f327d914a36019408441924";
69729
+ const rawPackageVersion = "1.0.1071";
69730
+ const rawGitSha = "9d44328d80bffd7ce2dfde1820030f1aaa3862bb";
69731
+ const rawSentryRelease = "boxes-dev-dvb@1.0.1071+9d44328d80bffd7ce2dfde1820030f1aaa3862bb";
69732
69732
  const packageVersion = typeof rawPackageVersion === "string" ? rawPackageVersion : void 0;
69733
69733
  const gitSha = typeof rawGitSha === "string" ? rawGitSha : void 0;
69734
69734
  const sentryRelease = typeof rawSentryRelease === "string" ? rawSentryRelease : void 0;
@@ -75112,7 +75112,7 @@ var init_packageVersion = __esm({
75112
75112
  return path18.join(process.cwd(), "dvb");
75113
75113
  };
75114
75114
  readEmbeddedPackageVersion = () => {
75115
- const raw = "1.0.1070";
75115
+ const raw = "1.0.1071";
75116
75116
  return trimVersion(raw);
75117
75117
  };
75118
75118
  readNearestPackageMetadata = (basePath) => {
package/dist/bin/dvbd.mjs CHANGED
@@ -64674,9 +64674,9 @@ var init_sentry = __esm({
64674
64674
  uncaughtExceptionMonitorInstalled = false;
64675
64675
  currentDevboxSentryUser = null;
64676
64676
  readBuildMetadata = () => {
64677
- const rawPackageVersion = "1.0.1070";
64678
- const rawGitSha = "da013a8b246bdf050f327d914a36019408441924";
64679
- const rawSentryRelease = "boxes-dev-dvb@1.0.1070+da013a8b246bdf050f327d914a36019408441924";
64677
+ const rawPackageVersion = "1.0.1071";
64678
+ const rawGitSha = "9d44328d80bffd7ce2dfde1820030f1aaa3862bb";
64679
+ const rawSentryRelease = "boxes-dev-dvb@1.0.1071+9d44328d80bffd7ce2dfde1820030f1aaa3862bb";
64680
64680
  const packageVersion = typeof rawPackageVersion === "string" ? rawPackageVersion : void 0;
64681
64681
  const gitSha = typeof rawGitSha === "string" ? rawGitSha : void 0;
64682
64682
  const sentryRelease = typeof rawSentryRelease === "string" ? rawSentryRelease : void 0;
@@ -66893,7 +66893,7 @@ var init_packageVersion = __esm({
66893
66893
  return path8.join(process.cwd(), "dvb");
66894
66894
  };
66895
66895
  readEmbeddedPackageVersion = () => {
66896
- const raw = "1.0.1070";
66896
+ const raw = "1.0.1071";
66897
66897
  return trimVersion(raw);
66898
66898
  };
66899
66899
  readNearestPackageMetadata = (basePath) => {
@@ -24,11 +24,13 @@ Team and enterprise arrangements may differ from these self-serve limits.
24
24
  Included box-hours, project limits, and awake-devbox limits apply per user;
25
25
  prepaid overage credits are shared through the team's billing account.
26
26
 
27
- For the YC deal, redeem the offer on YC and sign in to boxes.dev with the same
28
- email. The offer will apply to your team after your email is verified. If you
29
- already have a paid subscription or used a different email, contact
30
- hi@boxes.dev for help applying the offer; redemption will not automatically
31
- replace a paid subscription.
27
+ For the YC deal, redeem the offer on YC and enter the email you use to sign in
28
+ to boxes.dev. The offer will apply to your team after that email is verified.
29
+ Redemption does not replace a paid subscription automatically. If the team
30
+ already pays for a plan, a team admin can switch to the deal from Billing.
31
+ Switching will end the paid subscription right away, without an automatic
32
+ refund or prorated credit for the unused time. If you entered a
33
+ different email, contact hi@boxes.dev for help applying the offer.
32
34
 
33
35
  ## Box-Hours
34
36
 
@@ -99,13 +101,23 @@ tell the member to contact a team admin.
99
101
 
100
102
  ## Overage Credits
101
103
 
102
- Paid-plan overage uses prepaid usage credits. Team admins can buy manual credit
103
- amounts from billing. Current manual purchase options are $20, $50, $100, and
104
- $250.
104
+ Paid-plan overage uses prepaid usage credits. Team admins on an active Starter
105
+ or Pro plan can buy credits from billing. They can enter any amount from $20 up
106
+ to what the team can still buy this month, including cents, or pick $20, $50,
107
+ $100, or $250 to fill in the amount. A trial team needs to choose a paid plan
108
+ before it can buy credits.
105
109
 
106
- Team admins can turn on auto-reload. Auto-reload buys more credits when the
107
- credit balance reaches a configured threshold, up to a configured monthly
108
- purchase limit.
110
+ A team can buy up to $300 in credits per calendar month on Starter and up to
111
+ $1,000 on Pro, counting manual purchases and auto-reload together. Months follow
112
+ UTC. Purchased credits carry over to later months. Billing shows how much the
113
+ team can still buy this month and blocks larger amounts. A checkout that was
114
+ opened but not paid holds its amount for about 30 minutes. Teams that need more
115
+ credits can email hi@boxes.dev.
116
+
117
+ Team admins can turn on auto-reload. Auto-reload buys the configured reload
118
+ amount when the credit balance reaches a configured threshold. An optional
119
+ monthly auto-reload limit caps automatic purchases only; with no limit set,
120
+ auto-reload can continue up to the team's monthly credit purchase limit.
109
121
 
110
122
  If credits are low, the product warns users. If credits are depleted and the
111
123
  team is past included usage, compute can be blocked until a team admin buys
@@ -176,6 +188,8 @@ Common reasons:
176
188
  - The trial expired or used all trial box-hours.
177
189
  - The user does not have a paid seat.
178
190
  - Included usage is exhausted and no usable prepaid credits remain.
191
+ - The team reached its monthly credit purchase limit and its credits ran out.
192
+ The team can email hi@boxes.dev to buy more that month.
179
193
  - The team subscription is past due or unpaid.
180
194
  - The user reached their awake devbox limit.
181
195
  - The user reached their project limit.
@@ -10,10 +10,15 @@ runtime.
10
10
  The workbench has a few persistent areas:
11
11
 
12
12
  - The top bar is split at the left pane's edge. The left pane's own top area
13
- shows the project selector, a back button, a thread search button, and a
14
- usage icon (billing usage details on hover, when relevant). The back button retraces earlier workbench
13
+ shows the project selector, a back button, a crosshair button, a thread
14
+ search button, and a usage icon (billing usage details on hover, when relevant). The back button retraces earlier workbench
15
15
  selections, so an integration or automation detour can return to the thread
16
16
  you were viewing. It is disabled until there is somewhere to return. The
17
+ crosshair button scrolls the thread list to the selected thread, first
18
+ expanding the Devboxes or Template box section, folder, or devbox that hides
19
+ it. It is disabled when no thread is selected and hidden when the left pane
20
+ is too narrow to fit it. A thread inside a collapsed automation stays hidden
21
+ until you expand that automation. The
17
22
  content pane's title bar starts with runtime status, metrics, and ports when
18
23
  a Template box or devbox is selected, and ends with the
19
24
  Terminal/Files/Git/Review/Browser pane control as icon-only buttons that show
@@ -246,10 +251,11 @@ runtime has no live metrics.
246
251
  Expand **Settings** near the bottom of the project thread list and open
247
252
  **Project settings** for settings that belong to the project rather than to a
248
253
  particular machine. This page contains **Project storage**, **Git**, **Agent
249
- permissions for this project**, and **Devbox lifecycle**, including the
250
- project's preferred Git action, commit thread-link behavior, startup script,
251
- shared agent guidance, automatic waking of sleeping machines, and other
252
- new-devbox defaults. Opening it does not select or wake a machine.
254
+ permissions for this project**, **Devbox lifecycle**, and **Agent settings**,
255
+ including the project's preferred Git action, commit thread-link behavior,
256
+ startup script, shared agent guidance, automatic waking of sleeping machines,
257
+ other new-devbox defaults, and the Claude and Codex settings kept on every box
258
+ (see `threads-and-agents.md`). Opening it does not select or wake a machine.
253
259
 
254
260
  To change the automatic idle-sleep timeout, open **Account
255
261
  → Sleep timeout** and choose 5, 15, 30, or 60 minutes, or **Team default**.
@@ -531,6 +531,13 @@ as Fix checks, Mark ready, Address feedback, Push to update PR, or Merge. Push
531
531
  to update PR uses the same Pull-first Push dialog. When **View PR #N** appears,
532
532
  it opens that pull request in your browser.
533
533
 
534
+ Open the PR indicator in the conversation header and choose **Fix CI & apply
535
+ feedback** to prepare the available CI fixes and review feedback together.
536
+ Choose **Fix CI** or **Apply review feedback** to handle just one; an option
537
+ is unavailable when there is no work of that kind. Review the prepared prompt
538
+ and **Code review** attachment, then choose **Send** to start the agent.
539
+ Choose **Open PR in Git/Review** in the same menu to inspect the pull request.
540
+
534
541
  ## Automatic Pull Request Follow-ups
535
542
 
536
543
  For an open pull request, open its actions menu and choose **Automate
@@ -74,6 +74,48 @@ permission and works on a Template box, a devbox, and a Team Template editing
74
74
  machine. Use it when a script or tool needs to attribute work to the person who
75
75
  owns the box; it does not identify who sent a particular message.
76
76
 
77
+ ## Feedback And Bug Reports
78
+
79
+ An on-box agent can send feedback straight to the boxes.dev team. Use
80
+ `send-feedback` when `dvb-onbox` or another boxes.dev capability lacks a
81
+ command, option, or feature you needed, and `report-bug` when one behaved
82
+ incorrectly:
83
+
84
+ ```bash
85
+ dvb-onbox send-feedback "I needed to list the devboxes in a folder, but folders list shows only the folders."
86
+ dvb-onbox report-bug "ports share --port 3000 failed twice with service_unavailable while the app was listening."
87
+ ```
88
+
89
+ For a longer report, pipe the text to `--stdin`:
90
+
91
+ ```bash
92
+ printf '%s\n' \
93
+ 'Goal: wait for three delegated threads to finish before merging their work.' \
94
+ 'Tried: dvb-onbox threads wait <id> once for each thread.' \
95
+ 'Wished for: one command that waits until all of them are done.' \
96
+ | dvb-onbox send-feedback --stdin
97
+ ```
98
+
99
+ Add `--json` to receive the report's `eventId`. A report can be up to 32 KiB
100
+ and needs no permission. It goes to the same feedback queue as the desktop
101
+ app's **Send feedback**, together with the box owner's boxes.dev account, the
102
+ current box and project, and the current thread's ID.
103
+
104
+ You don't need the user's approval to send a report, and writing one shouldn't
105
+ interrupt the user's task. Describe what you were trying to do, what you ran,
106
+ what happened, and what would have helped.
107
+
108
+ Don't include anything confidential unless the user explicitly asks you to.
109
+ That covers secrets, credentials, environment values, source code, file
110
+ contents, personal data, and business or customer details from the user's
111
+ project; describe the user's work in general terms instead. IDs that help the
112
+ boxes.dev team debug the problem, such as thread, devbox, project, or request
113
+ IDs, are fine to include, as are error codes and messages from boxes.dev
114
+ commands.
115
+
116
+ Send one report for each distinct issue, and mention it briefly in your final
117
+ response. If the user asks you not to send feedback, don't.
118
+
77
119
  ## Plugin And MCP Requests
78
120
 
79
121
  Use the `boxes-agent-extensions` skill when a user asks to install, update, or
@@ -166,8 +208,10 @@ dvb-onbox team-template settings get --template <team-template-id> --json
166
208
 
167
209
  Project output includes Agent Guidance, prompt prefix, startup/teardown scripts
168
210
  and timeouts, Git preferences, port forwarding, storage, environment metadata,
169
- member-file requirements and supplied state, maintenance where applicable, and
170
- agent permission defaults. `effectiveGitAction` includes the account's default
211
+ member-file requirements and supplied state, maintenance where applicable,
212
+ agent permission defaults, and Claude and Codex agent settings
213
+ (`agentSettings`, plus the Team Template's read-only `teamAgentSettings` in a
214
+ member project). `effectiveGitAction` includes the account's default
171
215
  when no project preference is set. `autoWake` reports the account-wide
172
216
  preference shown in Project settings. `permissionDefaultsEditable` is always false.
173
217
 
@@ -182,13 +226,13 @@ Team Template output includes its identity, description, source/repositories,
182
226
  machine size, active saved version, project defaults and save epochs, setup
183
227
  instructions, integration requirements, member-project policy, cleanup,
184
228
  maintenance and watches, Project URL/MCP definitions, environment definitions,
185
- and member-file requirements. Omit `--template` to select the current editing
229
+ member-file requirements, and agent settings. Omit `--template` to select the current editing
186
230
  box's template or the project's source template. An explicit ID must belong to
187
231
  the caller's team. Reading does not open or wake a template editing machine.
188
232
  Environment/file metadata never includes saved secret values or file contents.
189
233
 
190
234
  To save one section, write an operation to a regular JSON file inside
191
- `/home/boxes` (at most 512 KiB), then run:
235
+ `/home/boxes` (at most 512 KiB), then pass its absolute path:
192
236
 
193
237
  ```bash
194
238
  dvb-onbox project settings set --settings-file /home/boxes/settings-edit.json --json
@@ -237,6 +281,7 @@ Project operations use these fields in addition to `section`:
237
281
  | `member_files` | `expectedDefinitionScopeId`, `expectedDefinitionDesiredRevision`, `expectedMemberDesiredRevision` from `memberFilesRevision`; `updates` with `fileId` and `valueAction` (`kind: "delete"`, `kind: "accept"`, or `kind: "replace"` with `plaintextBase64` and `byteLength`). |
238
282
  | `environment_file` | `draft` for an ordinary project's environment file, as described below. For a managed project's personal values, use `env set|remove`. |
239
283
  | `environment_file_delete` | `contextId`, `expectedContextRevision` for an ordinary project's environment file. |
284
+ | `agent_settings` | `agent` (`claude` or `codex`), `content`, `expectedRevision`, as described below. In a member project, this saves the member's own settings. |
240
285
 
241
286
  Team Template operations use these fields in addition to `section`:
242
287
 
@@ -260,6 +305,7 @@ Team Template operations use these fields in addition to `section`:
260
305
  | `mcp_delete` | `mcpDefinitionId`, `expectedSaveEpoch`. |
261
306
  | `environment_file` | `draft` for a Team Template environment file, as described below. |
262
307
  | `environment_file_delete` | `contextId`, `expectedContextRevision`. |
308
+ | `agent_settings` | `agent` (`claude` or `codex`), `content`, `expectedRevision`, as described below. |
263
309
 
264
310
  An environment `draft` contains `contextId`, `expectedContextRevision`, `path`,
265
311
  `displayOrder`, `adoptionRevision`, `adoptionSourceSha256`,
@@ -286,6 +332,23 @@ saves. `set` does not publish a filesystem version. Source identity and machine
286
332
  size are creation settings; snapshots, publishing, account sign-in, and machine
287
333
  lifecycle retain their existing commands.
288
334
 
335
+ An `agent_settings` operation replaces one agent's whole document. `content`
336
+ is the complete text: a JSON object for Claude or TOML for Codex, and empty
337
+ text clears every setting. Start from the current `content` in the read
338
+ result, keep the settings the user didn't ask to change, and pass that
339
+ document's `revision` as `expectedRevision`, or 0 when the document is null.
340
+ boxes.dev stores Claude JSON with two-space indentation. Codex TOML is
341
+ stored as written, and people read and edit it in the desktop editor, so put
342
+ one key per line. Saving checks syntax and reserved keys, and checks each
343
+ document against the settings schema of the Claude Code or Codex version
344
+ boxes.dev installs. A value that would make the agent reject its settings
345
+ fails with `agent_settings_invalid` and a message naming the setting. A value
346
+ Claude Code would skip on its own, or a key that version doesn't recognize, is
347
+ saved, and the `--json` output's `settings.warnings` names it; tell the user,
348
+ because it is usually a mistake.
349
+ See **Agent Settings** in `threads-and-agents.md` for how boxes apply these
350
+ settings.
351
+
289
352
  Use `env set|remove` for environment values and `team-template member-files`
290
353
  for requirement definitions. These retain their own input and revision rules.
291
354
 
@@ -302,6 +302,11 @@ surrounding controls for diagnostics. Native mobile replay masks standard
302
302
  text-input fields before upload. Replays can contain ordinary displayed text,
303
303
  screen layout, movement, interactions, and other visual elements.
304
304
 
305
+ The desktop app also uploads its app log to the crash-reporting service. This
306
+ is the log it writes to `~/.devbox/logs/desktop-electron-main.log`, which
307
+ records app events, errors, and update progress. Support can read it without
308
+ asking the user to send the file.
309
+
305
310
  For the complete disclosure, retention details, and contact information, read
306
311
  the legal privacy policy at `https://boxes.dev/privacy`.
307
312
 
@@ -264,6 +264,25 @@ automatically. Header values can be entered under **Connection details**.
264
264
 
265
265
  Independent projects retain creation-time editable copies as described below.
266
266
 
267
+ ## Team Agent Settings
268
+
269
+ The **Agent settings** card on the Team Template page holds Claude and Codex
270
+ settings for projects that use the template. Only team admins can edit it, and
271
+ it can't be edited while the template is archived. How the settings reach
272
+ projects depends on the template's mode:
273
+
274
+ - **Managed projects** follow the team settings live. Every devbox combines
275
+ them with the member's own settings from that project's **Agent settings**
276
+ card, and the member's value wins where both set the same option. A saved
277
+ team change reaches existing devboxes within a minute without saving a new
278
+ environment version.
279
+ - **Independent projects** receive a copy when they are created. Later team
280
+ changes don't reach existing projects, and each owner edits their own copy.
281
+
282
+ The template's editing machine does not receive these settings. See
283
+ `threads-and-agents.md` for how boxes.dev writes the settings on each box, how
284
+ lists combine, and which keys are reserved.
285
+
267
286
  ## Settings For New Projects
268
287
 
269
288
  The **Settings for new projects** card controls everything else a new project
@@ -407,6 +407,71 @@ because its native inventory and marketplace actions require a personal
407
407
  Template box. A user or agent can still use the agent's native Plugin tooling
408
408
  on an exact devbox; that installation is local to that devbox.
409
409
 
410
+ ## Agent Settings
411
+
412
+ The **Agent settings** card in **Project settings** keeps Claude and Codex
413
+ settings the same on every box in a project. The **Claude** tab holds a JSON
414
+ object in the format of Claude's `settings.json`, and the **Codex** tab holds
415
+ TOML in the format of Codex's `config.toml`. After **Save**, boxes.dev writes
416
+ the saved entries into `~/.claude/settings.json` or `~/.codex/config.toml` on
417
+ the Template box and every devbox in the project. Running boxes update within
418
+ a minute, sleeping boxes update when they wake, and new devboxes start with
419
+ the current settings, so no snapshot is needed.
420
+
421
+ boxes.dev changes only the entries saved in the card. Everything else in a
422
+ box's file stays, including entries written by a person, an agent, or another
423
+ boxes.dev feature. Objects merge key by key, so saving `env.EXAMPLE` keeps the
424
+ box's other `env` values. A Claude list such as `permissions.allow` adds the
425
+ saved items to the box's list, while a Codex list replaces the box's list.
426
+ Removing an entry from the card removes it from every box; a value the box had
427
+ before boxes.dev managed that entry does not come back. A managed entry edited
428
+ directly on a box is changed back within about a minute. If a box's file is
429
+ not valid JSON or TOML, boxes.dev leaves it unchanged.
430
+
431
+ The repository's own `.claude/settings.json` or `.codex/config.toml` takes
432
+ precedence over these settings, as do Claude's `.claude/settings.local.json`
433
+ and settings boxes.dev applies to every agent launch. Claude reads some
434
+ settings, such as `autoCompactWindow`, only when a session starts, so running
435
+ Claude sessions keep their old values. Codex reads `config.toml` when each
436
+ thread starts, so changes apply to new Codex threads.
437
+
438
+ Saving checks syntax, a 64 KB size limit, and keys other features manage:
439
+ Claude `enabledPlugins` and `extraKnownMarketplaces` and Codex `plugins` belong
440
+ to **Integrations → Plugins**, Codex `mcp_servers` belongs to
441
+ **Integrations → MCPs**, and boxes.dev sets Codex `projects` and `hooks` itself.
442
+ TOML dates, infinite numbers, and NaN can't be saved. Settings are also
443
+ checked against the settings schema of the Claude Code or Codex version
444
+ boxes.dev installs. A value that would make Codex refuse its whole
445
+ configuration or make Claude Code ignore the whole settings file, such as
446
+ `model_auto_compact_token_limit = "300000"` where Codex expects a number or
447
+ `"cleanupPeriodDays": "thirty"` for Claude Code, can't be saved; the card
448
+ names the setting and what the agent needs. Claude Code skips wrong values in
449
+ some settings (such as `effortLevel`) and reads the rest of the file, so those
450
+ save with a warning. A key that version doesn't recognize also saves with a
451
+ warning, because a newer version may know it and both agents ignore keys they
452
+ don't know.
453
+
454
+ Saving stores Claude JSON with two-space indentation, whoever saved it, and
455
+ stores Codex TOML as written. Each tab saves separately. If the same tab was
456
+ saved somewhere else after the editor loaded it, the card says **These
457
+ settings were changed elsewhere** and offers **Load latest**; make the change
458
+ again on the loaded text.
459
+
460
+ In a Team Template member project, the card also shows the template's settings
461
+ under **Team settings from <template name>**, which members can read but not
462
+ edit. Every devbox in the project combines the team settings with the member's
463
+ own. Where both set the same option, the member's value is used; Claude lists
464
+ include the items from both, and a member's Codex list replaces the team's.
465
+ Team admins edit the team settings on the Team Template page, and changes reach
466
+ existing devboxes within a minute. An ordinary project created from a Team
467
+ Template receives a copy of the template's settings when it is created; later
468
+ team changes don't reach it, and its owner edits that copy like any other
469
+ project's settings. See `team-template.md`.
470
+
471
+ Agents on a box can read and save these settings with
472
+ `dvb-onbox project settings` and `dvb-onbox team-template settings`; see
473
+ `onbox-agent-tools.md`.
474
+
410
475
  ## Draft And Startup States
411
476
 
412
477
  New threads can appear as drafts before the first prompt is sent. During
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@boxes-dev/dvb-runtime",
3
- "version": "1.0.1070",
3
+ "version": "1.0.1071",
4
4
  "description": "Runtime for the boxes.dev CLI. Install @boxes-dev/dvb to use the CLI.",
5
5
  "homepage": "https://boxes.dev",
6
6
  "type": "module",
@@ -77,5 +77,5 @@
77
77
  "e2b": "^2.18.0",
78
78
  "ink-testing-library": "^4.0.0"
79
79
  },
80
- "devboxReleasedAt": "2026-10-13T02:41:11Z"
80
+ "devboxReleasedAt": "2026-10-13T20:26:52Z"
81
81
  }