@boxes-dev/dvb-runtime 1.0.1051 → 1.0.1052

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
@@ -64612,9 +64612,9 @@ var init_sentry = __esm({
64612
64612
  uncaughtExceptionMonitorInstalled = false;
64613
64613
  currentDevboxSentryUser = null;
64614
64614
  readBuildMetadata = () => {
64615
- const rawPackageVersion = "1.0.1051";
64616
- const rawGitSha = "a146f896d6bb73d0ee0446cd7d2f7fbf92250dd8";
64617
- const rawSentryRelease = "boxes-dev-dvb@1.0.1051+a146f896d6bb73d0ee0446cd7d2f7fbf92250dd8";
64615
+ const rawPackageVersion = "1.0.1052";
64616
+ const rawGitSha = "6e5360aed3f79e9b0b4d34adaaea7b174277c4d7";
64617
+ const rawSentryRelease = "boxes-dev-dvb@1.0.1052+6e5360aed3f79e9b0b4d34adaaea7b174277c4d7";
64618
64618
  const packageVersion = typeof rawPackageVersion === "string" ? rawPackageVersion : void 0;
64619
64619
  const gitSha = typeof rawGitSha === "string" ? rawGitSha : void 0;
64620
64620
  const sentryRelease = typeof rawSentryRelease === "string" ? rawSentryRelease : void 0;
@@ -66821,7 +66821,7 @@ var init_packageVersion = __esm({
66821
66821
  return path8.join(process.cwd(), "dvb");
66822
66822
  };
66823
66823
  readEmbeddedPackageVersion = () => {
66824
- const raw = "1.0.1051";
66824
+ const raw = "1.0.1052";
66825
66825
  return trimVersion(raw);
66826
66826
  };
66827
66827
  readNearestPackageMetadata = (basePath) => {
@@ -4,9 +4,11 @@ The boxes.dev CLI is `dvb`. It is useful when you prefer terminal workflows,
4
4
  need direct shell access, want to copy a file into a machine, or want to manage
5
5
  machine lifecycle from scripts.
6
6
 
7
- The desktop app is the primary setup path for most new users. CLI setup is
8
- separate from desktop sign-in: if you sign in on desktop and later run CLI
9
- commands, the CLI may ask you to sign in again.
7
+ Most new users set up their first project by giving the setup prompt from the
8
+ boxes.dev website to a coding agent on their computer, which installs and
9
+ signs in the CLI (see Set Up A Project). CLI sign-in is separate from desktop
10
+ sign-in: if you sign in on desktop and later run CLI commands, the CLI may ask
11
+ you to sign in again.
10
12
 
11
13
  For exact flags, run `dvb --help` or `dvb <command> --help`.
12
14
 
@@ -53,10 +55,11 @@ Never install or run `dvb` on a boxes.dev machine: it can destabilize or
53
55
  permanently break that machine, and boxes.dev is not responsible for recovering
54
56
  a machine knowingly modified this way.
55
57
 
56
- Production installs are:
58
+ Production installs of the standalone build, which includes its own runtime,
59
+ for macOS or Linux on x64 or arm64:
57
60
 
58
61
  ```bash
59
- npm install -g @boxes-dev/dvb
62
+ npm install -g @boxes-dev/cli
60
63
  ```
61
64
 
62
65
  or:
@@ -65,6 +68,9 @@ or:
65
68
  curl -fsSL https://boxes.dev/install.sh | sh
66
69
  ```
67
70
 
71
+ With Node.js 22 or newer, `npm install -g @boxes-dev/dvb` installs a build
72
+ that uses the local Node.js runtime instead.
73
+
68
74
  ## Sign In And Agent Setup
69
75
 
70
76
  Use:
@@ -75,7 +81,9 @@ dvb setup
75
81
 
76
82
  This signs the CLI into boxes.dev and configures coding agents for CLI-created
77
83
  or CLI-managed work. It can also be used later to repair or update CLI agent
78
- auth.
84
+ auth. Someone setting up their first project doesn't need it: the setup
85
+ prompt signs the CLI in, and `dvb agent-init accounts` connects their coding
86
+ agents.
79
87
 
80
88
  Use `dvb setup --agents` when you only need to revisit coding-agent auth. For
81
89
  Codex auth on managed machines, use this command on your own computer instead of
@@ -92,14 +100,18 @@ Useful account commands:
92
100
 
93
101
  ## Set Up A Project
94
102
 
95
- The desktop app is the default project setup path. Terminal-first users can ask
96
- a coding agent working in the local repository to run:
103
+ The default project setup path has a coding agent working in the local
104
+ repository run:
97
105
 
98
106
  ```bash
99
107
  dvb agent-init
100
108
  ```
101
109
 
102
- The command gives the agent a read-only investigation and planning workflow.
110
+ The setup prompt on the website's **Get started** page adds a login code
111
+ (`dvb agent-init --login-code <code>`) so the CLI signs in without a separate
112
+ browser sign-in. The command gives the agent a read-only investigation and
113
+ planning workflow, and `dvb agent-init accounts` opens a browser page where
114
+ the user connects Codex or Claude Code before launch.
103
115
  The agent prepares a manifest with you, checks it, and asks for explicit
104
116
  approval before `dvb agent-init run` uploads files or creates a Template box.
105
117
  The current version-3 manifest also lets the agent design startup and teardown
@@ -313,10 +313,10 @@ Mobile settings include:
313
313
  in the browser.
314
314
 
315
315
  Someone opening your invite link can sign up with Google in their phone
316
- browser. After signing up on a phone, they will see that setup happens on
317
- their Mac, where to find the setup steps in their email, and a link to install
318
- the mobile app. Signing up on a computer continues straight to first-project
319
- setup in the web app.
316
+ browser. After signing up on a phone, they will see that their coding agent
317
+ will set up the project on the computer where their code lives, with actions
318
+ to email, copy, or share a link to the setup page. Signing up on a computer
319
+ continues straight to the web app's **Get started** page.
320
320
 
321
321
  Thread text size defaults to **Medium** for transcript and message text on this
322
322
  device. Choose **Compact**, **Medium**, or **Large** in **Settings → Appearance**.
@@ -33,27 +33,31 @@ locally: it clones one or more selected repositories into a new Template box,
33
33
  without env files, secrets, or untracked local work, and leaves environment
34
34
  setup to the user.
35
35
 
36
- Signing in on the website before any project exists lands on a get-started
37
- page with the ways to set up: use the desktop app (recommended; on a phone or
38
- iPad, boxes.dev offers to email the Mac app link instead of a direct
39
- download), copy a ready-made prompt that has a coding agent run the
40
- agent-driven terminal setup, or **Create from GitHub** directly in that
41
- browser. The GitHub path is the one that can be completed entirely from a
42
- phone.
43
-
44
- On Windows and Linux browsers that boxes.dev can confidently identify, the
45
- website's first-project and **New project** choosers show that the desktop app
46
- isn't available for that platform, without the download/open controls or
47
- **Recommended** label. Macs and browsers whose platform is uncertain keep
48
- **Download for Mac**. This does not change the coding-agent or GitHub paths.
49
-
50
- After **Download for Mac**, the website keeps the install and **Open the app**
51
- steps visible; it acknowledges the click but cannot verify that macOS finished
52
- the download or installation. When a user copies the coding-agent prompt, the
53
- same page confirms the copy and can show when the CLI connects, prepares the
54
- project, waits for launch approval, and starts launching. The coding agent still
55
- owns the setup work, and `dvb agent-init status` remains the source for its exact
56
- next action.
36
+ Signing in on the website before any project exists lands on **Get started**,
37
+ which has three steps:
38
+
39
+ 1. **Connect GitHub**, which is optional and shows as done once GitHub is
40
+ connected.
41
+ 2. **Set up your project with your coding agent**: a ready-made prompt to
42
+ paste into Codex or Claude Code in the project folder, which has the agent
43
+ run the agent-driven terminal setup. The prompt includes a login code that
44
+ signs the agent's CLI in to the same boxes.dev account. Each code works
45
+ once and expires within 30 minutes, and the page always shows a current
46
+ one.
47
+ 3. **Get the desktop app**: the agent gives the user the Mac app link once
48
+ setup starts, and **Download for Mac now** is available right away. On
49
+ Windows and Linux browsers that boxes.dev can confidently identify, this
50
+ step says the desktop app is Mac-only and links to the mobile app instead.
51
+
52
+ On a phone, the second step becomes **Continue on your computer**, with
53
+ actions to email, copy, or share a link to the page, and the desktop step is
54
+ left out. The first project is set up by the coding agent; **Create from
55
+ GitHub** is offered when the user adds a later project.
56
+
57
+ When a user copies the prompt, the page confirms the copy and can show when
58
+ the CLI connects, prepares the project, waits for launch approval, and starts
59
+ launching. The coding agent still owns the setup work, and `dvb agent-init
60
+ status` remains the source for its exact next action.
57
61
 
58
62
  After setup, the website's **Projects** page lists projects and their last-used
59
63
  activity. Choose a project name or **Open in desktop app** to continue in the
@@ -281,10 +285,42 @@ client remains preferred. Missing database variables, authentication problems,
281
285
  missing MySQL clients, and PostgreSQL servers newer than the available client
282
286
  are reported before the full bundle is built.
283
287
 
284
- The user must be logged in first (`dvb setup`), and launch requires the same
285
- billing activation as desktop setup. The machine created this way is a normal
286
- Template box: it appears in the desktop app, supports devboxes, and behaves
287
- identically from then on.
288
+ The prompt from **Get started**, the website's **New project** page, or the
289
+ desktop app's **Set up with your coding agent** card has the agent run `dvb
290
+ agent-init --login-code <code>`, which signs the CLI in without another
291
+ browser sign-in. If the code has expired or was already used, the CLI keeps an
292
+ existing CLI sign-in when it has one. Otherwise, `dvb agent-init login` opens
293
+ Google sign-in in the browser, prints the link, and waits for the user to
294
+ finish. Over SSH,
295
+ the browser can't reach the CLI, so the agent asks the user to copy a fresh
296
+ prompt instead.
297
+
298
+ Next, `dvb agent-init accounts` opens **Connect your accounts** in the
299
+ browser. There the user connects Codex, Claude Code, or both, and can connect
300
+ GitHub and Slack. Codex and Claude Code use their normal browser sign-in,
301
+ which returns to the CLI on the user's computer, and **Use an API key** saves
302
+ a key instead. **Done** becomes available once a coding agent is connected,
303
+ and the command waits until the user chooses it. Over SSH, the command prints
304
+ a link for the user to open and exits: on that page, Codex shows a one-time
305
+ code to enter on ChatGPT, Claude Code asks for the code Claude shows, and the
306
+ user tells the agent when they're done. **Use a code instead** switches a
307
+ local page to the same code flows for setups where browser sign-in can't
308
+ reach the CLI, such as a container. `dvb agent-init check` requires at least
309
+ one connected coding agent.
310
+
311
+ Once the setup thread starts on the Template box, `dvb agent-init run` tells
312
+ the agent where the user can follow it. On a Mac with the desktop app
313
+ installed, the agent offers to open it with `dvb agent-init open-desktop`,
314
+ which opens the Template box on the setup thread. On a Mac without the app,
315
+ the agent gives the download link, and on other computers or over SSH, it
316
+ points to the mobile app. When setup finishes, the agent lists the same
317
+ choices along with `dvb agents <project>`, which opens the Template box's
318
+ agent threads in the terminal (`--workspace` keeps the thread list beside the
319
+ open agent).
320
+
321
+ Launch requires the same billing activation as desktop setup. The machine
322
+ created this way is a normal Template box: it appears in the desktop app,
323
+ supports devboxes, and behaves identically from then on.
288
324
 
289
325
  ## Agent Auth
290
326
 
@@ -394,13 +430,14 @@ creation until a project is deleted or billing changes allow another project.
394
430
 
395
431
  ## Create From GitHub
396
432
 
397
- On the logged-in website, including from a mobile browser, choose **Create from
398
- GitHub** and connect a GitHub account. After a user has set up their first
399
- project, the desktop app also offers **Create from GitHub** under **Other
400
- setup options** when they start another project, marked **Manual setup**
401
- because it suits only repositories that need little setup. The desktop
402
- first-project flow leaves this option out so it can guide new users through
403
- copying their local development environment instead.
433
+ After a user has set up their first project, **Create from GitHub** is
434
+ available when they add another one: under **New project** on the logged-in
435
+ website, including from a mobile browser, and under **Other setup options** in
436
+ the desktop app, marked **Manual setup** because it suits only repositories
437
+ that need little setup. Choose it and connect a GitHub account. The website's
438
+ **Get started** page and the desktop first-project flow leave this option out
439
+ so they can guide new users through copying their local development
440
+ environment instead.
404
441
  Connecting first authorizes the user's GitHub identity. If the boxes.dev GitHub
405
442
  App is not installed yet, setup then makes installation the required next step:
406
443
  choose the personal account or organization that owns the repositories and
@@ -847,10 +884,10 @@ support.
847
884
 
848
885
  To upload another local project, use **New project...** in the titlebar project
849
886
  selector or **File > New Project...** in the desktop app. On the website,
850
- **New project** opens the same three setup paths offered before the first
851
- project exists. For a repository that is not on the user's computer, **Create
852
- from GitHub** clones another GitHub-backed ordinary project instead, with the
853
- same manual environment setup afterwards. Each ordinary project made through
887
+ **New project** offers the coding-agent prompt and **Create from GitHub**. For
888
+ a repository that is not on the user's computer, **Create from GitHub** clones
889
+ another GitHub-backed ordinary project instead, with the same manual
890
+ environment setup afterwards. Each ordinary project made through
854
891
  these paths gets its own setup flow and Template box. A Team Template's
855
892
  **Member projects** path is the exception: it creates an independent project
856
893
  without a personal Template box and uses the Team Template's current saved
@@ -89,11 +89,23 @@ compute; the former team's payment method and credits remain on that team.
89
89
  ## Finding And Managing Team Templates
90
90
 
91
91
  Team admins can open **Team Templates** from the desktop project selector or
92
- **Manage team**. The project-selector submenu links directly to each
93
- non-archived template and includes **New Team Template...** and **View all Team
94
- Templates**. The collection shows each named template separately, including
95
- its description, machine size, latest saved version, and editing status. Team
96
- admins can also reveal archived templates here.
92
+ from **Manage team** → **Manage Team Templates**. The project-selector submenu
93
+ links directly to each non-archived template and includes **New Team
94
+ Template...** and **View all Team Templates**. The collection shows each named
95
+ template separately, including its description, machine size, latest saved
96
+ version, and editing status. Team admins can also reveal archived templates
97
+ here.
98
+
99
+ The collection and each template's detail page also work in a web browser, so
100
+ an admin can keep a template open beside the desktop workbench. In the desktop
101
+ app, **Open in browser** opens the current Team Templates page in the default
102
+ browser. On the website, **Team** in the header opens Team Settings, where
103
+ **Manage Team Templates** opens the collection. A browser can change everything
104
+ on the detail page except the editing session itself: creating a template,
105
+ GitHub setup, **Take control**, continuing an editing session, and **Resolve**
106
+ all need the desktop app on a Mac. In their place, a browser on a Mac shows
107
+ **Open in desktop app**, which opens the same template in the desktop app;
108
+ phones, tablets, Windows, and Linux show a note instead.
97
109
 
98
110
  **Project settings** for a project made from a Team Template names that
99
111
  template. A managed project shows the template it uses, and an independent
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@boxes-dev/dvb-runtime",
3
- "version": "1.0.1051",
3
+ "version": "1.0.1052",
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",
@@ -79,5 +79,5 @@
79
79
  "e2b": "^2.18.0",
80
80
  "ink-testing-library": "^4.0.0"
81
81
  },
82
- "devboxReleasedAt": "2026-10-03T17:57:33Z"
82
+ "devboxReleasedAt": "2026-10-03T19:33:55Z"
83
83
  }