@boxes-dev/dvb-runtime 1.0.1117 → 1.0.1118

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
@@ -1,6 +1,6 @@
1
1
  #!/usr/bin/env node
2
2
 
3
- !function(){try{var e="undefined"!=typeof window?window:"undefined"!=typeof global?global:"undefined"!=typeof globalThis?globalThis:"undefined"!=typeof self?self:{},n=(new e.Error).stack;n&&(e._sentryDebugIds=e._sentryDebugIds||{},e._sentryDebugIds[n]="d1495133-92a8-5a9b-ad94-6837cfa5aec7")}catch(e){}}();
3
+ !function(){try{var e="undefined"!=typeof window?window:"undefined"!=typeof global?global:"undefined"!=typeof globalThis?globalThis:"undefined"!=typeof self?self:{},n=(new e.Error).stack;n&&(e._sentryDebugIds=e._sentryDebugIds||{},e._sentryDebugIds[n]="d7754666-9161-5ad3-887d-5c1fc3238541")}catch(e){}}();
4
4
  import { createRequire as __dvbCreateRequire } from "node:module";
5
5
  import { dirname as __dvbDirname } from "node:path";
6
6
  import { fileURLToPath as __dvbFileURLToPath } from "node:url";
@@ -70565,9 +70565,9 @@ var init_sentry = __esm({
70565
70565
  uncaughtExceptionMonitorInstalled = false;
70566
70566
  currentDevboxSentryUser = null;
70567
70567
  readBuildMetadata = () => {
70568
- const rawPackageVersion = "1.0.1117";
70569
- const rawGitSha = "5bc562be7ab3ff9894b62798adcf85aa7c664978";
70570
- const rawSentryRelease = "boxes-dev-dvb@1.0.1117+5bc562be7ab3ff9894b62798adcf85aa7c664978";
70568
+ const rawPackageVersion = "1.0.1118";
70569
+ const rawGitSha = "62386b015598fbd4d96c48b1d9f719511b410839";
70570
+ const rawSentryRelease = "boxes-dev-dvb@1.0.1118+62386b015598fbd4d96c48b1d9f719511b410839";
70571
70571
  const packageVersion = typeof rawPackageVersion === "string" ? rawPackageVersion : void 0;
70572
70572
  const gitSha = typeof rawGitSha === "string" ? rawGitSha : void 0;
70573
70573
  const sentryRelease = typeof rawSentryRelease === "string" ? rawSentryRelease : void 0;
@@ -76241,7 +76241,7 @@ var init_packageVersion = __esm({
76241
76241
  return path18.join(process.cwd(), "dvb");
76242
76242
  };
76243
76243
  readEmbeddedPackageVersion = () => {
76244
- const raw = "1.0.1117";
76244
+ const raw = "1.0.1118";
76245
76245
  return trimVersion(raw);
76246
76246
  };
76247
76247
  readNearestPackageMetadata = (basePath) => {
@@ -263792,7 +263792,7 @@ var init_parse6 = __esm({
263792
263792
  // src/devbox/agentInit/commandCore.ts
263793
263793
  import fs51 from "node:fs/promises";
263794
263794
  import path64 from "node:path";
263795
- var resolveAgentInitProject, resolveProjectPathFlag, readManifestTextIfPresent;
263795
+ var buildProjectCheckError, resolveAgentInitProject, resolveProjectPathFlag, readManifestTextIfPresent;
263796
263796
  var init_commandCore = __esm({
263797
263797
  "src/devbox/agentInit/commandCore.ts"() {
263798
263798
  "use strict";
@@ -263802,6 +263802,13 @@ var init_commandCore = __esm({
263802
263802
  init_statePaths();
263803
263803
  init_parse6();
263804
263804
  init_progressReport();
263805
+ buildProjectCheckError = (projectPath, error55) => {
263806
+ const message = typeof error55?.["message"] === "string" ? error55["message"] : "The selected project folder cannot be initialized.";
263807
+ const action = typeof error55?.["action"] === "string" ? ` ${error55["action"]}` : "";
263808
+ return new Error(
263809
+ `Project check failed: ${message}${action} Checked folder: ${projectPath}`
263810
+ );
263811
+ };
263805
263812
  resolveAgentInitProject = async ({
263806
263813
  alias = null,
263807
263814
  onSnapshot = null,
@@ -263828,8 +263835,7 @@ var init_commandCore = __esm({
263828
263835
  selectedPath: projectPath
263829
263836
  });
263830
263837
  if (!localValidation.ok || !localValidation.repo) {
263831
- const message = typeof localValidation.error?.["message"] === "string" ? localValidation.error["message"] : "The selected project folder cannot be initialized.";
263832
- throw new Error(`Project check failed: ${message}`);
263838
+ throw buildProjectCheckError(projectPath, localValidation.error);
263833
263839
  }
263834
263840
  const localStatePaths = resolveAgentInitStatePaths({
263835
263841
  accountScope: context34.accountScope,
@@ -263858,8 +263864,7 @@ var init_commandCore = __esm({
263858
263864
  ...selection
263859
263865
  });
263860
263866
  if (!validation.ok || !validation.repo) {
263861
- const message = typeof validation.error?.["message"] === "string" ? validation.error["message"] : "The selected project folder cannot be initialized.";
263862
- throw new Error(`Project check failed: ${message}`);
263867
+ throw buildProjectCheckError(projectPath, validation.error);
263863
263868
  }
263864
263869
  const repo = validation.repo;
263865
263870
  recordAgentInitProgressProject({
@@ -302472,4 +302477,4 @@ react/cjs/react-jsx-runtime.development.js:
302472
302477
  *)
302473
302478
  */
302474
302479
 
302475
- //# debugId=d1495133-92a8-5a9b-ad94-6837cfa5aec7
302480
+ //# debugId=d7754666-9161-5ad3-887d-5c1fc3238541
package/dist/bin/dvbd.mjs CHANGED
@@ -64833,9 +64833,9 @@ var init_sentry = __esm({
64833
64833
  uncaughtExceptionMonitorInstalled = false;
64834
64834
  currentDevboxSentryUser = null;
64835
64835
  readBuildMetadata = () => {
64836
- const rawPackageVersion = "1.0.1117";
64837
- const rawGitSha = "5bc562be7ab3ff9894b62798adcf85aa7c664978";
64838
- const rawSentryRelease = "boxes-dev-dvb@1.0.1117+5bc562be7ab3ff9894b62798adcf85aa7c664978";
64836
+ const rawPackageVersion = "1.0.1118";
64837
+ const rawGitSha = "62386b015598fbd4d96c48b1d9f719511b410839";
64838
+ const rawSentryRelease = "boxes-dev-dvb@1.0.1118+62386b015598fbd4d96c48b1d9f719511b410839";
64839
64839
  const packageVersion = typeof rawPackageVersion === "string" ? rawPackageVersion : void 0;
64840
64840
  const gitSha = typeof rawGitSha === "string" ? rawGitSha : void 0;
64841
64841
  const sentryRelease = typeof rawSentryRelease === "string" ? rawSentryRelease : void 0;
@@ -67387,7 +67387,7 @@ var init_packageVersion = __esm({
67387
67387
  return path8.join(process.cwd(), "dvb");
67388
67388
  };
67389
67389
  readEmbeddedPackageVersion = () => {
67390
- const raw = "1.0.1117";
67390
+ const raw = "1.0.1118";
67391
67391
  return trimVersion(raw);
67392
67392
  };
67393
67393
  readNearestPackageMetadata = (basePath) => {
@@ -116,9 +116,12 @@ New teams that sign up at boxes.dev/conductor will receive one month of Pro
116
116
  free, and new teams that sign up at boxes.dev/alien or boxes.dev/launch-yc
117
117
  will receive three months. The account that creates the team will get the
118
118
  first Pro seat, including 300 box-hours each month. Extra usage will require
119
- prepaid credits. Only boxes.dev/launch-yc asks for a card, which is charged
120
- only if the team keeps Pro. Pro will end when the offer does unless a team admin
121
- chooses **Keep plan** in Billing; continuing will use the normal Pro price.
119
+ prepaid credits. Only boxes.dev/launch-yc asks for a card, to prevent abuse of
120
+ the offer. Choose **Continue without a card** to take the smaller trial with
121
+ 20 free box-hours instead. Adding a card will not enable automatic charges
122
+ for extra usage or renew Pro automatically. Pro will end when the offer does
123
+ unless a team admin chooses **Keep plan** in Billing; continuing will use the
124
+ normal Pro price.
122
125
  The offer does not replace an existing account's or team's billing.
123
126
 
124
127
  ## Overage Credits
@@ -176,7 +176,7 @@ To add a review comment:
176
176
  1. Open Files for the thread you want to review.
177
177
  2. If the file is editable, switch the file header from Edit to Comment.
178
178
  3. Click a line or drag a line range.
179
- 4. Write the comment and choose Done.
179
+ 4. Write the comment and choose Add to chat.
180
180
 
181
181
  For Markdown files, you can also comment while reading Preview. Select text in
182
182
  a paragraph or heading and choose Comment to attach the comment to that
@@ -193,15 +193,29 @@ popped out, saved comments also appear in the review pane, where you can select,
193
193
  edit, delete, and return to the source line or rendered comment.
194
194
 
195
195
  When comments exist, the composer shows a Code review attachment with the number
196
- of files and comments. Sending includes the selected lines and a small amount of
197
- nearby context rather than an entire large file, and uses the review format
198
- expected by the selected Claude or Codex agent. The sent user message appears in
199
- the transcript as a structured Code review card with its files, line ranges,
200
- selected snippets, comments, and any accompanying message.
196
+ of files and comments. Choose it to list the comments waiting to be sent,
197
+ grouped by file. From the list you can edit or delete a comment, or choose it to
198
+ show it in place: Files opens plain-file comments and Git/Review opens comments
199
+ on uncommitted changes. Comments on a commit, a commit range, or a pull request
200
+ can be edited and deleted from the list; to see them in place, select that
201
+ commit, range, or pull request in Git/Review. The attachment's remove button
202
+ asks for confirmation, then discards the whole review.
203
+
204
+ Sending includes the selected lines and a small amount of nearby context rather
205
+ than an entire large file, and uses the review format expected by the selected
206
+ Claude or Codex agent. The sent user message appears in the transcript as a
207
+ structured Code review card with its files, line ranges, selected snippets,
208
+ comments, and any accompanying message. Choose a comment's file and line range
209
+ in the card to open those lines in Files.
201
210
 
202
211
  Use Git/Review when you want to comment on a specific added, removed, or
203
212
  changed diff line.
204
213
 
214
+ The mobile app's file viewer can add comments on a file or its uncommitted
215
+ diff to the same kind of Code review attachment; see `mobile.md`. Pending
216
+ comments are kept separately on each device, so comments started on mobile
217
+ don't appear in the desktop composer.
218
+
205
219
  ## Git/Review Pane
206
220
 
207
221
  Open Git/Review from the desktop titlebar. Git/Review contains repository
@@ -373,6 +373,29 @@ directly from the thread. Image previews fit the available
373
373
  screen and support pinch zoom and panning with inertial flings and elastic edge
374
374
  settling.
375
375
 
376
+ When the file viewer was opened from a thread, tapping a line in a text file or
377
+ its diff starts a code review comment for that thread, the same kind desktop's
378
+ Files and Git/Review add. While the new comment is open, tapping another line
379
+ selects a range; in a diff, the range stays within one hunk. **Add to chat**
380
+ saves the comment under its lines and adds it to the composer's **Code
381
+ review** attachment. Tapping a saved comment opens it for editing, with a
382
+ delete button. Tapping the attachment lists the comments by file: a comment
383
+ opens at its lines in the file viewer, and each one can be edited or deleted
384
+ in the list. The attachment's X removes the whole review after a confirmation.
385
+ While a message is sending, review comments can't be added, edited, or deleted.
386
+ Sending includes the review in the message in the same format desktop uses, and
387
+ a review can be sent without other text. Unsent comments stay on the phone and
388
+ don't sync with desktop. Mobile can comment only on a file's contents and its
389
+ uncommitted changes, not on commits, ranges, or pull requests.
390
+
391
+ Sent reviews from either app appear in the mobile transcript as a **Code
392
+ review** card: comments grouped by file, each with its line label, up to three
393
+ lines of the selected code, and the comment, followed by the typed message.
394
+ Reviews with more than three comments show the first three and a **Show all**
395
+ control. A line label opens those lines in the file viewer. Codex reviews of
396
+ plain-file lines carry no code, so those comments show none. While thread search
397
+ highlights a match inside a review, that message shows its full text instead.
398
+
376
399
  In a devbox thread, tapping the **Devbox** pill in the header opens the
377
400
  devbox's status and a read-only list of its Git changes. The status names the
378
401
  state behind the pill's colored dot, such as **Running**, **Sleeping**,
@@ -386,8 +409,8 @@ a repository has unresolved merge conflicts.
386
409
 
387
410
  Large downloads may open through the browser, and they arrive with the file's
388
411
  real name and extension so your phone can open them in the right app. Full
389
- file browsing, uploads, inline review, Git staging, commits, and history are
390
- desktop workbench workflows.
412
+ file browsing, uploads, review comments on commits, ranges, and pull requests,
413
+ Git staging, commits, and history are desktop workbench workflows.
391
414
 
392
415
  ## Terminal
393
416
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@boxes-dev/dvb-runtime",
3
- "version": "1.0.1117",
3
+ "version": "1.0.1118",
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-11-09T06:42:54Z"
80
+ "devboxReleasedAt": "2026-11-09T20:46:55Z"
81
81
  }