@boxes-dev/dvb-runtime 1.0.1051 → 1.0.1053

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.
@@ -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
@@ -203,8 +207,15 @@ files need a named file selection if you want to copy them.
203
207
  The desktop app's Project step leads with **Set up with your coding agent**,
204
208
  followed by a Team Template when the team has one. The local-folder and GitHub
205
209
  options are fallbacks under **Other setup options** at the bottom of the step,
206
- with the local folder first. **Use coding agent** expands the card to show the
207
- prompt to copy into Codex or Claude Code in the local project folder. Once
210
+ with the local folder first. The prompt and **Copy prompt** are visible
211
+ immediately. Paste the prompt into Codex or Claude Code in the local project
212
+ folder. During first-run setup, the card also shows when the CLI connects and
213
+ prepares the project, including after a reload. For a later project, the card
214
+ confirms the copy and setup progress appears once uploading begins.
215
+
216
+ The folder wizard's steps and **Continue** appear only after a local folder
217
+ is selected. **Other setup options** remembers whether it was open across
218
+ reloads in the same app session. Once
208
219
  the agent's `dvb agent-init run` starts uploading, the Project step's setup
209
220
  choices are replaced by that project's setup status: the project name and four
210
221
  stages (uploading the project files, creating the Template box, unpacking the
@@ -281,10 +292,43 @@ client remains preferred. Missing database variables, authentication problems,
281
292
  missing MySQL clients, and PostgreSQL servers newer than the available client
282
293
  are reported before the full bundle is built.
283
294
 
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.
295
+ The prompt from **Get started**, the website's **New project** page, or the
296
+ desktop app's **Set up with your coding agent** card has the agent run `dvb
297
+ agent-init --login-code <code>`, which signs the CLI in without another
298
+ browser sign-in. If the code has expired or was already used, the CLI keeps an
299
+ existing CLI sign-in when it has one. Otherwise, `dvb agent-init login` opens
300
+ Google sign-in in the browser, prints the link, and waits for the user to
301
+ finish. Over SSH,
302
+ the browser can't reach the CLI, so the agent asks the user to copy a fresh
303
+ prompt instead.
304
+
305
+ Next, `dvb agent-init accounts` opens **Connect your accounts** in the
306
+ browser. There the user connects Codex, Claude Code, or both, and can connect
307
+ GitHub and Slack. Codex and Claude Code use their normal browser sign-in in
308
+ the same tab, which returns to the page through the CLI on the user's
309
+ computer; neither agent needs to be installed there. **Use an API key** saves
310
+ a key instead. **Done** becomes available once a coding agent is connected,
311
+ and the command waits until the user chooses it. Over SSH, the command prints
312
+ a link for the user to open and exits: on that page, Codex shows a one-time
313
+ code to enter on ChatGPT, Claude Code asks for the code Claude shows, and the
314
+ user tells the agent when they're done. **Use a code instead** switches a
315
+ local page to the same code flows for setups where browser sign-in can't
316
+ reach the CLI, such as a container. `dvb agent-init check` requires at least
317
+ one connected coding agent.
318
+
319
+ Once the setup thread starts on the Template box, `dvb agent-init run` tells
320
+ the agent where the user can follow it. On a Mac with the desktop app
321
+ installed, the agent offers to open it with `dvb agent-init open-desktop`,
322
+ which opens the Template box on the setup thread. On a Mac without the app,
323
+ the agent gives the download link, and on other computers or over SSH, it
324
+ points to the mobile app. When setup finishes, the agent lists the same
325
+ choices along with `dvb agents <project>`, which opens the Template box's
326
+ agent threads in the terminal (`--workspace` keeps the thread list beside the
327
+ open agent).
328
+
329
+ Launch requires the same billing activation as desktop setup. The machine
330
+ created this way is a normal Template box: it appears in the desktop app,
331
+ supports devboxes, and behaves identically from then on.
288
332
 
289
333
  ## Agent Auth
290
334
 
@@ -394,13 +438,14 @@ creation until a project is deleted or billing changes allow another project.
394
438
 
395
439
  ## Create From GitHub
396
440
 
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.
441
+ After a user has set up their first project, **Create from GitHub** is
442
+ available when they add another one: under **New project** on the logged-in
443
+ website, including from a mobile browser, and under **Other setup options** in
444
+ the desktop app, marked **Manual setup** because it suits only repositories
445
+ that need little setup. Choose it and connect a GitHub account. The website's
446
+ **Get started** page and the desktop first-project flow leave this option out
447
+ so they can guide new users through copying their local development
448
+ environment instead.
404
449
  Connecting first authorizes the user's GitHub identity. If the boxes.dev GitHub
405
450
  App is not installed yet, setup then makes installation the required next step:
406
451
  choose the personal account or organization that owns the repositories and
@@ -847,10 +892,10 @@ support.
847
892
 
848
893
  To upload another local project, use **New project...** in the titlebar project
849
894
  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
895
+ **New project** offers the coding-agent prompt and **Create from GitHub**. For
896
+ a repository that is not on the user's computer, **Create from GitHub** clones
897
+ another GitHub-backed ordinary project instead, with the same manual
898
+ environment setup afterwards. Each ordinary project made through
854
899
  these paths gets its own setup flow and Template box. A Team Template's
855
900
  **Member projects** path is the exception: it creates an independent project
856
901
  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
@@ -0,0 +1,66 @@
1
+ # Point to the desktop UI in a reply
2
+
3
+ Agents can include references to boxes.dev controls and settings in conversation
4
+ replies. These appear as blue inline pills in the desktop app, beside the
5
+ explanation of what the user can do there.
6
+
7
+ ## How references behave
8
+
9
+ Hover a pill to see where the item lives and what clicking will do. A visible
10
+ item may also get a quiet preview outline. Click to reveal the item, scroll it
11
+ into view, and briefly highlight it. Settings sections and integration pages
12
+ can open; controls such as Git, New automation, and Share are highlighted so
13
+ the user can choose their next action. A reference never presses the highlighted
14
+ control, changes a permission, or creates a resource.
15
+
16
+ Navigation follows the app's ordinary behavior, including Auto-wake when
17
+ opening Template box details. After a settings or detail-page detour, **Back
18
+ to thread** returns to the conversation at its bottom. An older reply's exact
19
+ scroll position is not restored. Escape or another interaction dismisses the
20
+ highlight; reduced-motion preferences remove the travel animation and glint.
21
+
22
+ References are relative to the conversation's project and devbox. Specific
23
+ thread, automation, and Project URL references can identify other items in
24
+ that same project. Thread references reveal a sidebar row without selecting
25
+ it. Rows nested under automation runs are not supported yet.
26
+
27
+ On mobile, tap a reference for its location in the desktop app. Shared and
28
+ read-only conversations cannot reveal the viewer's own controls. If an item
29
+ is missing or unavailable, the app will explain that; unknown destinations
30
+ appear as plain text. Older clients and command-line readers may display the
31
+ ordinary Markdown destination instead of a pill.
32
+
33
+ ## Writing references
34
+
35
+ In a boxes.dev conversation reply, use a normal Markdown link with a supported
36
+ destination, for example:
37
+
38
+ ```md
39
+ Add persistent variables in [Environment files](boxes:environment-files).
40
+ Review [Agent permissions](boxes:agent-permissions) for this devbox.
41
+ Enable [Message other agents](boxes:agent-permissions/message-agents) if you want agents to collaborate.
42
+ ```
43
+
44
+ Use the UI's name or a short, natural noun phrase as the label. Link the first
45
+ useful mention rather than every repeated mention, and keep the sentence
46
+ understandable without the link. Explain the user's next step in the prose;
47
+ clicking a reference only reveals its destination. Avoid “click here.”
48
+
49
+ Use only destinations listed below. Replace entity placeholders with exact IDs
50
+ already returned by authorized boxes.dev tools; never guess an ID or derive
51
+ one from a title. Static names and permission/provider keys are case-sensitive.
52
+ Do not add query parameters, fragments, encodings, or action arguments.
53
+
54
+ Use these links only in boxes.dev conversation prose. Do not put them in Slack
55
+ or Linear replies sent through tools, commit messages, PR bodies, repository
56
+ files, or executable code. A code example remains literal and does not become
57
+ a clickable reference. No extra tool call is needed to show a reference.
58
+
59
+ ## Supported destinations
60
+
61
+ The published skill includes the current destination table here. Availability
62
+ depends on the project, box kind, agent, permissions, and the UI currently
63
+ offered to the viewer. Use the normal feature documentation to explain those
64
+ requirements; a reference does not grant access or enable a missing feature.
65
+
66
+ <!-- UI_REFERENCE_CATALOG -->
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.1053",
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",
@@ -34,15 +34,13 @@
34
34
  "dist/agent-init-guides",
35
35
  "dist/codex",
36
36
  "dist/managed-codex-install",
37
- "dist/boxes-mosh",
38
37
  "dist/postgres-tools",
39
38
  "dist/product-docs",
40
39
  "dist/prompts"
41
40
  ],
42
41
  "scripts": {
43
- "build": "../../node_modules/@typescript/native/bin/tsc -b --checkers 1 --builders 1 && npm run build:bundle && npm run build:prompts && npm run build:boxes-mosh && npm run build:postgres-tools",
42
+ "build": "../../node_modules/@typescript/native/bin/tsc -b --checkers 1 --builders 1 && npm run build:bundle && npm run build:prompts && npm run build:postgres-tools",
44
43
  "build:bundle": "node ./scripts/build-bundle.mjs",
45
- "build:boxes-mosh": "node ../../../../scripts/package-boxes-mosh-surface.mjs --surface cli --output dist/boxes-mosh --allow-missing-materialized",
46
44
  "build:postgres-tools": "node ../../../../scripts/package-postgres-tools-surface.mjs --surface cli --output dist/postgres-tools --allow-missing-materialized",
47
45
  "build:prompts": "rm -rf dist/product-docs && mkdir -p dist/prompts dist/codex dist/managed-codex-install dist/agent-init-guides dist/product-docs && cp -R src/devbox/commands/init/codex/prompts/* dist/prompts/ && cp -R src/devbox/commands/init/codex/schema/* dist/codex/ && cp -R ../../../../shared/devboxCore/assets/managed-codex-install/* dist/managed-codex-install/ && cp -R ../../../../shared/devboxCore/assets/agent-init-guides/* dist/agent-init-guides/ && cp -R ../../../../apps/sprite-daemon/assets/skills/boxes-product-docs/. dist/product-docs/",
48
46
  "prepack": "npm run clean && npm run build",
@@ -79,5 +77,5 @@
79
77
  "e2b": "^2.18.0",
80
78
  "ink-testing-library": "^4.0.0"
81
79
  },
82
- "devboxReleasedAt": "2026-10-03T17:57:33Z"
80
+ "devboxReleasedAt": "2026-10-04T22:46:11Z"
83
81
  }
@@ -1,9 +0,0 @@
1
- 02fa8fb934723971b88bb1a5c2488a479340b1f6bbf52df2c1988cb4c447d2e0 darwin-x64/notices.tar.gz
2
- 27797d0b939cd0c48ef0eae1c4c034d4a7e31dc6866d6fad688d162324adab10 darwin-arm64/mosh-client
3
- 3486778118d2ac84b09fcbc12c46e7dd6d2071519d31eec7d758dac81aca8dc2 darwin-x64/mosh-client
4
- 6aa8f7a121c9705c313b986133da13d51c114745343e28eecc15cbcbda0b4221 darwin-arm64/notices.tar.gz
5
- 700f16a3f6a0df292020de0ec6b647881be12c57146457a3028be8158e15cb46 linux-x64/notices.tar.gz
6
- 72d709843f7d9815ded8254327d41c237e223965a35d2446c2d210033dfb6ea1 linux-arm64/mosh-client
7
- 92c6384031a5828e8a0fa2bac0d2a97eba718c81dea773b7776d89bb1abb9002 source/boxes-mosh-source-829ce1ba6667ce0b5cfa797ae6bb4edefd8f53cd.tar.gz
8
- a20d0298999e903c90df13a399508fe235039f16927698706172905351467dc5 linux-x64/mosh-client
9
- cf33d7f8b0ba7015b53e3c0232b9796012406957520ee4f5f0bde8decf4cf473 linux-arm64/notices.tar.gz
@@ -1,70 +0,0 @@
1
- {
2
- "schemaVersion": 1,
3
- "repository": "https://github.com/nbdrco/boxes-mosh",
4
- "releaseTag": "v1.4.0-boxes.4",
5
- "forkCommit": "829ce1ba6667ce0b5cfa797ae6bb4edefd8f53cd",
6
- "forkVersion": "1.4.0-boxes.4",
7
- "signalingProtocolVersion": 1,
8
- "source": {
9
- "path": "boxes-mosh-source-829ce1ba6667ce0b5cfa797ae6bb4edefd8f53cd.tar.gz",
10
- "sha256": "92c6384031a5828e8a0fa2bac0d2a97eba718c81dea773b7776d89bb1abb9002"
11
- },
12
- "targets": {
13
- "linux-x64": {
14
- "client": {
15
- "path": "boxes-mosh-1.4.0-boxes.4-linux-x64-mosh-client",
16
- "sha256": "a20d0298999e903c90df13a399508fe235039f16927698706172905351467dc5"
17
- },
18
- "server": {
19
- "path": "boxes-mosh-1.4.0-boxes.4-linux-x64-mosh-server",
20
- "sha256": "7ea19b91d3337e37d48f678b4ebb7725caaf63295f8cd2847aa3d3ec973c0a07"
21
- },
22
- "notices": {
23
- "path": "boxes-mosh-1.4.0-boxes.4-linux-x64-notices.tar.gz",
24
- "sha256": "700f16a3f6a0df292020de0ec6b647881be12c57146457a3028be8158e15cb46"
25
- }
26
- },
27
- "linux-arm64": {
28
- "client": {
29
- "path": "boxes-mosh-1.4.0-boxes.4-linux-arm64-mosh-client",
30
- "sha256": "72d709843f7d9815ded8254327d41c237e223965a35d2446c2d210033dfb6ea1"
31
- },
32
- "server": {
33
- "path": "boxes-mosh-1.4.0-boxes.4-linux-arm64-mosh-server",
34
- "sha256": "de66a6437fdf2652883b2faff7c3615468e2d8dfd254778d37fb7751bcc33da0"
35
- },
36
- "notices": {
37
- "path": "boxes-mosh-1.4.0-boxes.4-linux-arm64-notices.tar.gz",
38
- "sha256": "cf33d7f8b0ba7015b53e3c0232b9796012406957520ee4f5f0bde8decf4cf473"
39
- }
40
- },
41
- "darwin-x64": {
42
- "client": {
43
- "path": "boxes-mosh-1.4.0-boxes.4-darwin-x64-mosh-client",
44
- "sha256": "3486778118d2ac84b09fcbc12c46e7dd6d2071519d31eec7d758dac81aca8dc2"
45
- },
46
- "server": {
47
- "path": "boxes-mosh-1.4.0-boxes.4-darwin-x64-mosh-server",
48
- "sha256": "d7b3c2994e75b5851b7f2eb7c7d8f29b4ac8351bc8420c5316a766165850401d"
49
- },
50
- "notices": {
51
- "path": "boxes-mosh-1.4.0-boxes.4-darwin-x64-notices.tar.gz",
52
- "sha256": "02fa8fb934723971b88bb1a5c2488a479340b1f6bbf52df2c1988cb4c447d2e0"
53
- }
54
- },
55
- "darwin-arm64": {
56
- "client": {
57
- "path": "boxes-mosh-1.4.0-boxes.4-darwin-arm64-mosh-client",
58
- "sha256": "27797d0b939cd0c48ef0eae1c4c034d4a7e31dc6866d6fad688d162324adab10"
59
- },
60
- "server": {
61
- "path": "boxes-mosh-1.4.0-boxes.4-darwin-arm64-mosh-server",
62
- "sha256": "78bac507f1a43f6a58eee40f6e6c55576f00a76984ad9e6d379a067391568d1e"
63
- },
64
- "notices": {
65
- "path": "boxes-mosh-1.4.0-boxes.4-darwin-arm64-notices.tar.gz",
66
- "sha256": "6aa8f7a121c9705c313b986133da13d51c114745343e28eecc15cbcbda0b4221"
67
- }
68
- }
69
- }
70
- }