@boxes-dev/dvb-runtime 1.0.1124 → 1.0.1126

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.
@@ -132,9 +132,9 @@ When the manifest uses managed GitHub access, `start` also checks whether
132
132
  boxes.dev can already use the project's GitHub repositories. If it reports a
133
133
  GitHub access problem, follow its printed fix before you investigate, so the
134
134
  user can finish on GitHub while you work. When the boxes.dev GitHub App can't
135
- access a repository, ask the user to choose App access or SSH first (see
136
- Phase 3), and run `dvb agent-init github connect` only if they choose App
137
- access. `check` verifies access again before launch.
135
+ access a repository, tell the user about App access and SSH, then run
136
+ `dvb agent-init github connect` in the background without waiting for their
137
+ choice (see Phase 3). `check` verifies access again before launch.
138
138
 
139
139
  Read any worktree, project-overlap, or skipped-repository explanations printed by `start`.
140
140
  Explain them to the user during review and confirm the intended project scope.
@@ -167,18 +167,19 @@ project's repositories, which can take several minutes; re-run check when it
167
167
  succeeds. If it stops after 20 minutes without progress, for example while an
168
168
  organization owner reviews the request, run it again once the user is ready.
169
169
 
170
- If the boxes.dev GitHub App can't access a repository, ask the user how the
171
- project should pull and push. App access needs the App installed for the
170
+ If the boxes.dev GitHub App can't access a repository, first tell the user
171
+ how the project can pull and push. App access needs the App installed for the
172
172
  repository's owner, and an organization owner may need to approve it. SSH uses
173
173
  a key added to the user's own GitHub account. Either one covers pull and push;
174
174
  automatic pull request updates and follow-ups need App access. With SSH, the
175
175
  user can give the App access later for those features and keep SSH for pull
176
- and push. For App access, run `dvb agent-init github connect` in the
177
- background; it opens GitHub, prints which account the user should choose, and
178
- waits for the user to finish there. If an installation needs an
179
- update, follow the exact action printed by check. Set `githubAccess: ssh` and
180
- the GitHub `gitSsh` rows to setup only when the user chooses SSH, and keep the
181
- user's choice when access changes later. GitLab and other origins continue to
176
+ and push. Then run `dvb agent-init github connect` in the background without
177
+ waiting for their answer; it opens GitHub, prints which account the user
178
+ should choose, and waits for the user to finish there. If an installation
179
+ needs an update, follow the exact action printed by check. Set
180
+ `githubAccess: ssh` and the GitHub `gitSsh` rows to setup only when the user
181
+ chooses SSH, stop the waiting command, and keep the user's choice when access
182
+ changes later. GitLab and other origins continue to
182
183
  use their seeded `gitSsh` entries.
183
184
 
184
185
  Separately, `dvb agent-init github cli status` shows whether boxes.dev will
@@ -213,6 +214,15 @@ branch or use a clean local branch from the Template snapshot for both setup
213
214
  and new devboxes; omit the generated remote Git block only for that latter
214
215
  choice. Do not invent a remote branch or publish one.
215
216
 
217
+ The repository may include setup scripts or agent instructions written for
218
+ another tool, such as a Conductor workspace setup script or a dev container.
219
+ They show what the project needs, but they often depend on that tool's
220
+ environment variables, secret store, or worktree layout, which boxes.dev
221
+ doesn't provide. When a script depends on that environment, put its portable
222
+ steps, such as toolchain installs, locked dependency installs, and code
223
+ generation, in `setupNotes` instead of running it unchanged or calling it from
224
+ startup or maintenance.
225
+
216
226
  Review `devboxLifecycle` even when its seeded Git refresh is correct. Add a
217
227
  teardown script only for cleanup that must happen before a devbox is removed.
218
228
  The generated Git block declares each selected repository's starting branch,
@@ -220,14 +230,17 @@ normally its remote default branch such as `main`. Keep those paths aligned with
220
230
  `project.repositories` after narrowing the project. boxes.dev saves these
221
231
  defaults separately and checks out fresh remote code before additional startup
222
232
  commands. Confirm unknown branches instead of using the Template box's current
223
- branch as the default. Keep dependency and service commands after the generated
224
- block; do not add another Git reset or branch switch there.
225
-
226
- Recommend Template maintenance when the project has dependencies, generated
227
- code, or tooling that change over time; most projects do. New devboxes start
228
- from the Template box's latest snapshot. Maintenance keeps that snapshot
229
- current: it updates the Template box on the selected starting branch, installs
230
- locked dependencies, and refreshes tooling, then boxes.dev saves a new snapshot.
233
+ branch as the default. Keep quick dependency and service commands after the
234
+ generated block; startup runs on every new devbox within its timeout, so
235
+ one-time installs belong in `setupNotes`. Do not add another Git reset or
236
+ branch switch there.
237
+
238
+ Recommend Template maintenance for most projects. New devboxes start from the
239
+ Template box's latest snapshot, and maintenance keeps that snapshot from going
240
+ stale: it updates the Template box on the selected starting branch and installs
241
+ locked dependencies, then boxes.dev saves a new snapshot. Keep the script
242
+ small. Add code generation or a tooling refresh only when the project needs it
243
+ to stay current, and don't call a full first-time setup script from it.
231
244
  Design `templateMaintenance.script` and its exact GitHub watch paths together.
232
245
  Watch the lockfiles, toolchain version files, and generated-code inputs that
233
246
  make the script necessary. Don't watch application source; each matching push
@@ -236,8 +249,7 @@ access independently of the `githubAccess` transport choice. Follow the
236
249
  script requirements in the manifest guide. Setup leaves the maintenance
237
250
  schedule off and saves fresh baselines. The remote setup agent tests the
238
251
  script twice on the Template box before boxes.dev saves it. If the user
239
- declines maintenance or the project has nothing to keep current, keep
240
- `templateMaintenance: null` and say why in your review.
252
+ declines maintenance, keep `templateMaintenance: null`.
241
253
 
242
254
  For `project.instanceType`, present every live option seeded in the manifest,
243
255
  ask the user which one they want, record that key, and remove its marker. The
@@ -18,11 +18,12 @@ gitSsh:
18
18
  Managed access uses the user's existing boxes.dev GitHub connection for the
19
19
  Template box and future devboxes. If needed, run `dvb agent-init github
20
20
  connect`, let the user finish in the browser, and rerun `check`. When a repo
21
- is not covered by the boxes.dev GitHub App, ask the user whether to give the
22
- App access or use SSH. For App access, the same command opens the GitHub page
23
- that grants access; an organization owner may need to approve it. Check
24
- prints the exact GitHub action when a
25
- repo is not writable or an installation needs updated access. Do not put any returned URL, connection
21
+ is not covered by the boxes.dev GitHub App, tell the user they can give the
22
+ App access or use SSH, then run the same command in the background without
23
+ waiting for their answer. It opens the GitHub page that grants access; an
24
+ organization owner may need to approve it. If the user chooses SSH, stop the
25
+ command and use the SSH setup below. Check prints the exact GitHub action
26
+ when a repo is not writable or an installation needs updated access. Do not put any returned URL, connection
26
27
  id, repository id, or token in the manifest. Managed access can push changes
27
28
  under `.github/workflows` after every affected installation accepts the shown
28
29
  update. Keep the GitHub `gitSsh` rows at `mode: skip` and
@@ -114,13 +114,15 @@ manifest; `check` derives them from current boxes.dev GitHub access.
114
114
 
115
115
  Treat `templateMaintenance.script` and its `watches` as one design problem.
116
116
  Write the script for the dependency, generated-file, or tooling changes that
117
- will actually require upkeep, then watch the smallest exact paths that signal
118
- those changes, such as lockfiles and toolchain version files. Don't watch
119
- application source; each matching push wakes the Template box. Each
120
- `repository` is a detected project-relative repository path (`.` for the
121
- root); each watched path is exact and relative to that repository. Maintenance
122
- watches always require current boxes.dev GitHub App read access, even when
123
- `githubAccess` uses SSH or skips Git transport.
117
+ will actually require upkeep. Keep it small, usually a branch update and a
118
+ locked dependency install like the example below; it keeps the Template box
119
+ from going stale and doesn't repeat first-time setup. Then watch the smallest
120
+ exact paths that signal those changes, such as lockfiles and toolchain version
121
+ files. Don't watch application source; each matching push wakes the Template
122
+ box. Each `repository` is a detected project-relative repository path (`.` for
123
+ the root); each watched path is exact and relative to that repository.
124
+ Maintenance watches always require current boxes.dev GitHub App read access,
125
+ even when `githubAccess` uses SSH or skips Git transport.
124
126
 
125
127
  A maintenance script must:
126
128
 
@@ -165,8 +167,7 @@ under the maintenance runner's environment and saves any correction it makes;
165
167
  setup does not start a maintenance run. A later watched change, **Run now** in
166
168
  **Template maintenance** on the Template box page, or a schedule the user
167
169
  enables can start the first run.
168
- Keep `templateMaintenance: null` when the user declines maintenance or the
169
- Template box needs no ongoing upkeep.
170
+ Keep `templateMaintenance: null` only when the user declines maintenance.
170
171
  Use a nonempty teardown script only when devbox removal genuinely needs cleanup;
171
172
  it is not a second maintenance hook.
172
173
 
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]="c3a26375-a35b-59f3-817e-cc924e78c797")}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]="dcd2bdc6-2856-5137-856d-e6285eab649f")}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";
@@ -70599,9 +70599,9 @@ var init_sentry = __esm({
70599
70599
  uncaughtExceptionMonitorInstalled = false;
70600
70600
  currentDevboxSentryUser = null;
70601
70601
  readBuildMetadata = () => {
70602
- const rawPackageVersion = "1.0.1124";
70603
- const rawGitSha = "a3a2a57d8f49746d693292b4dba145d53943ca0f";
70604
- const rawSentryRelease = "boxes-dev-dvb@1.0.1124+a3a2a57d8f49746d693292b4dba145d53943ca0f";
70602
+ const rawPackageVersion = "1.0.1126";
70603
+ const rawGitSha = "683747375c07cccbbafcab51cbeb89fff6258653";
70604
+ const rawSentryRelease = "boxes-dev-dvb@1.0.1126+683747375c07cccbbafcab51cbeb89fff6258653";
70605
70605
  const packageVersion = typeof rawPackageVersion === "string" ? rawPackageVersion : void 0;
70606
70606
  const gitSha = typeof rawGitSha === "string" ? rawGitSha : void 0;
70607
70607
  const sentryRelease = typeof rawSentryRelease === "string" ? rawSentryRelease : void 0;
@@ -75395,7 +75395,7 @@ image.
75395
75395
  - **Base**: Ubuntu 24.04 (repo-owned E2B template baseline)
75396
75396
  - **User**: \`boxes\`
75397
75397
  - **Home**: \`/home/boxes\`
75398
- - **Shell**: bash (zsh, tmux, and common CLI tooling are installed)
75398
+ - **Shell**: bash (tmux and common CLI tooling are installed)
75399
75399
  - **Privilege model**: use \`sudo\` when system-level changes are required
75400
75400
 
75401
75401
  ### Pre-installed Tooling Baseline
@@ -75505,6 +75505,11 @@ Then apply the setup plan in \`{{setup_path}}\`:
75505
75505
  - Read the whole setup plan before changing the machine. If it has a non-empty
75506
75506
  \`agentInstructions\` field, treat that as user-provided setup guidance and
75507
75507
  follow it unless it conflicts with these safety instructions.
75508
+ - Setup scripts and agent instructions written for another tool, such as a
75509
+ Conductor workspace script or a dev container, may depend on that tool's
75510
+ environment variables, secret store, or worktree layout, which this Template
75511
+ box doesn't have. Use them to learn what the project needs, and follow the
75512
+ setup plan where they disagree with it.
75508
75513
  {{repository_setup_block}}
75509
75514
  - Install required tools/runtimes that are listed.
75510
75515
  - Prefer project-local installs (e.g., package manager installs in the project or the relevant indexed repo) over global installs.
@@ -76275,7 +76280,7 @@ var init_packageVersion = __esm({
76275
76280
  return path18.join(process.cwd(), "dvb");
76276
76281
  };
76277
76282
  readEmbeddedPackageVersion = () => {
76278
- const raw = "1.0.1124";
76283
+ const raw = "1.0.1126";
76279
76284
  return trimVersion(raw);
76280
76285
  };
76281
76286
  readNearestPackageMetadata = (basePath) => {
@@ -264960,7 +264965,7 @@ var init_githubAccess = __esm({
264960
264965
  ok: false,
264961
264966
  issue: githubIssue(
264962
264967
  `boxes.dev does not have GitHub App repository access for: ${missing.join(", ") || "this project"}.`,
264963
- offerSshAlternative ? "Ask the user whether this project should pull and push through the boxes.dev GitHub App or with their own SSH key. For App access, run `dvb agent-init github connect` to give boxes.dev access to each listed repository on GitHub; an organization owner may need to approve it. For SSH, set `githubAccess: ssh` and follow `dvb agent-init guide git-ssh`; automatic pull request updates and follow-ups will still need App access. Then re-run check." : "Run `dvb agent-init github connect` to open GitHub and give boxes.dev access to each listed repository. An organization owner may need to approve the request. Then re-run check."
264968
+ offerSshAlternative ? "First tell the user they can give the boxes.dev GitHub App access to each listed repository, which an organization owner may need to approve, or use an SSH key for pull and push instead; automatic pull request updates and follow-ups need App access. Then run `dvb agent-init github connect` in the background without waiting for their answer. It opens GitHub and waits until boxes.dev has access. If the user chooses SSH, stop it, set `githubAccess: ssh`, and follow `dvb agent-init guide git-ssh`. Re-run check once access is ready." : "Run `dvb agent-init github connect` to open GitHub and give boxes.dev access to each listed repository. An organization owner may need to approve the request. Then re-run check."
264964
264969
  ),
264965
264970
  missingAccess: {
264966
264971
  appInstallationUrl,
@@ -266724,7 +266729,7 @@ var init_gitSsh = __esm({
266724
266729
 
266725
266730
  // src/devbox/commands/agentInit/githubConnect.ts
266726
266731
  import { setTimeout as delay3 } from "node:timers/promises";
266727
- var SIGN_IN_POLL_MS, REPOSITORY_ACCESS_POLL_MS, GITHUB_CONNECT_WAIT_TIMEOUT_MS, SSH_ALTERNATIVE, startAgentInitGithubConnection, isGithubConnectionReady, readInstallUrl, evaluateGithubStep, openGithubPage, isTerminalWaitError, connectAgentInitGithub;
266732
+ var SIGN_IN_POLL_MS, REPOSITORY_ACCESS_POLL_MS, GITHUB_CONNECT_WAIT_TIMEOUT_MS, SSH_ALTERNATIVE, startAgentInitGithubConnection, isGithubConnectionReady, readInstallUrl, signInStep, evaluateGithubStep, openGithubPage, isTerminalWaitError, connectAgentInitGithub;
266728
266733
  var init_githubConnect = __esm({
266729
266734
  "src/devbox/commands/agentInit/githubConnect.ts"() {
266730
266735
  "use strict";
@@ -266781,17 +266786,30 @@ var init_githubConnect = __esm({
266781
266786
  installUrl: typeof fields["installUrl"] === "string" ? fields["installUrl"] : null
266782
266787
  };
266783
266788
  };
266789
+ signInStep = (projectLayoutRepos) => ({
266790
+ kind: "sign_in",
266791
+ repositories: projectLayoutRepos.flatMap((repo) => {
266792
+ const coordinates = resolveGithubRepositoryFromOrigin(repo.origin);
266793
+ return coordinates ? [`${coordinates.owner}/${coordinates.name}`] : [];
266794
+ })
266795
+ });
266784
266796
  evaluateGithubStep = async ({
266785
266797
  client,
266786
- loadRepositories
266798
+ loadProjectLayoutRepos,
266799
+ loadGithubDependencies
266787
266800
  }) => {
266788
266801
  const connectionResult = await client.getGithubConnection({});
266789
- if (!isGithubConnectionReady(connectionResult)) return { kind: "sign_in" };
266802
+ if (!isGithubConnectionReady(connectionResult)) {
266803
+ return signInStep(await loadProjectLayoutRepos());
266804
+ }
266790
266805
  const inventoryResult = await client.listGithubRepositories({});
266791
266806
  const inventoryRetry = agentInitGithubInventoryRetry(inventoryResult);
266792
- if (inventoryRetry === "sign_in") return { kind: "sign_in" };
266807
+ if (inventoryRetry === "sign_in") {
266808
+ return signInStep(await loadProjectLayoutRepos());
266809
+ }
266793
266810
  if (inventoryRetry !== null) return { kind: "retry", ...inventoryRetry };
266794
- const { projectLayoutRepos, githubDependencies } = await loadRepositories();
266811
+ const projectLayoutRepos = await loadProjectLayoutRepos();
266812
+ const githubDependencies = await loadGithubDependencies?.();
266795
266813
  let resolution = resolveAgentInitManagedGithubAccess({
266796
266814
  connectionResult,
266797
266815
  inventoryResult,
@@ -266862,8 +266880,8 @@ var init_githubConnect = __esm({
266862
266880
  kind: "blocked",
266863
266881
  issue: {
266864
266882
  ...resolution.issue,
266865
- message: `${repositories} belongs to @${page.ownerLogin}'s personal account.`,
266866
- fix: `Ask @${page.ownerLogin} to give boxes.dev access to it on GitHub.${ssh}`
266883
+ message: repositoryFullNames.length === 1 ? `${repositories} belongs to @${page.ownerLogin}'s personal account, so only @${page.ownerLogin} can give boxes.dev access to it.` : `${repositories} belong to @${page.ownerLogin}'s personal account, so only @${page.ownerLogin} can give boxes.dev access to them.`,
266884
+ fix: `Tell the user to ask @${page.ownerLogin} to give boxes.dev access on GitHub. If @${page.ownerLogin} is the user's own account, they can instead disconnect GitHub on their boxes.dev Account page and connect it as @${page.ownerLogin}; then re-run \`dvb agent-init github connect\`.${ssh}`
266867
266885
  }
266868
266886
  };
266869
266887
  }
@@ -266904,9 +266922,10 @@ var init_githubConnect = __esm({
266904
266922
  now = Date.now,
266905
266923
  timeoutMs = GITHUB_CONNECT_WAIT_TIMEOUT_MS
266906
266924
  }) => {
266907
- const loadRepositories = async () => ({
266908
- projectLayoutRepos: await loadProjectLayoutRepos(),
266909
- githubDependencies: await loadGithubDependencies?.()
266925
+ const evaluate = () => evaluateGithubStep({
266926
+ client,
266927
+ loadProjectLayoutRepos,
266928
+ loadGithubDependencies
266910
266929
  });
266911
266930
  let currentWait = null;
266912
266931
  let currentWaitKey = null;
@@ -266918,7 +266937,7 @@ var init_githubConnect = __esm({
266918
266937
  );
266919
266938
  return "timed_out";
266920
266939
  };
266921
- let step = await evaluateGithubStep({ client, loadRepositories });
266940
+ let step = await evaluate();
266922
266941
  for (; ; ) {
266923
266942
  if (step.kind === "ready") {
266924
266943
  print(step.message);
@@ -266946,7 +266965,7 @@ var init_githubConnect = __esm({
266946
266965
  }
266947
266966
  } else {
266948
266967
  lastRetryMessage = null;
266949
- const wait = step.kind === "sign_in" ? { step: "sign_in" } : step.wait;
266968
+ const wait = step.kind === "sign_in" ? { step: "sign_in", repositories: step.repositories } : step.wait;
266950
266969
  pollMs = step.kind === "sign_in" ? SIGN_IN_POLL_MS : REPOSITORY_ACCESS_POLL_MS;
266951
266970
  const waitKey = JSON.stringify(wait);
266952
266971
  if (waitKey !== currentWaitKey) {
@@ -266982,7 +267001,7 @@ var init_githubConnect = __esm({
266982
267001
  await sleep9(Math.min(pollMs, remainingMs));
266983
267002
  if (step.kind === "retry" && pollMs >= remainingMs) return stopWaiting();
266984
267003
  try {
266985
- step = await evaluateGithubStep({ client, loadRepositories });
267004
+ step = await evaluate();
266986
267005
  } catch (error55) {
266987
267006
  if (isTerminalWaitError(error55)) throw error55;
266988
267007
  step = {
@@ -268443,9 +268462,13 @@ var init_seed = __esm({
268443
268462
  );
268444
268463
  push("# The generated Git block declares each repository's default branch.");
268445
268464
  push(
268446
- "# Keep its paths in sync with project.repositories. Add application setup"
268465
+ "# Keep its paths in sync with project.repositories. After that block, add"
268447
268466
  );
268448
- push("# after that block. Use teardown only for cleanup before removal.");
268467
+ push(
268468
+ "# only quick per-devbox steps, such as a locked dependency install. Put"
268469
+ );
268470
+ push("# one-time setup in setupNotes instead. Use teardown only for cleanup");
268471
+ push("# before removal.");
268449
268472
  const unknownDefaults = startupScript ? [] : repos.filter((repo) => !repo.origin || !repo.originDefaultBranch);
268450
268473
  if (unknownDefaults.length > 0) {
268451
268474
  const names = unknownDefaults.map(
@@ -268474,17 +268497,23 @@ var init_seed = __esm({
268474
268497
  push(" teardownTimeoutSeconds: 30");
268475
268498
  push(' teardownScript: ""');
268476
268499
  push("");
268477
- push("# Template box maintenance, recommended for most projects. Design the");
268478
- push("# script and GitHub watch paths together: watch lockfiles and tooling");
268479
268500
  push(
268480
- "# files, not application source. The script fast-forwards the selected"
268501
+ "# Template box maintenance, recommended for most projects. It keeps the"
268502
+ );
268503
+ push(
268504
+ "# Template box from going stale, so keep the script small: fast-forward"
268505
+ );
268506
+ push(
268507
+ "# the selected branch and install locked dependencies without prompts."
268481
268508
  );
268482
268509
  push(
268483
- "# branch, installs without prompts, and fails clearly on local changes"
268510
+ "# Don't call a full first-time setup script from it. Design the script"
268484
268511
  );
268512
+ push("# and GitHub watch paths together: watch lockfiles and tooling files,");
268485
268513
  push(
268486
- "# or another branch. Setup tests it twice, saves a fresh baseline, and"
268514
+ "# not application source. The script fails clearly on local changes or"
268487
268515
  );
268516
+ push("# another branch. Setup tests it twice, saves a fresh baseline, and");
268488
268517
  push("# leaves the schedule off. See the manifest guide for requirements.");
268489
268518
  push(
268490
268519
  "# Set timeoutSeconds to an integer from 1 through 480 (at most 8 minutes)."
@@ -302558,4 +302587,4 @@ react/cjs/react-jsx-runtime.development.js:
302558
302587
  *)
302559
302588
  */
302560
302589
 
302561
- //# debugId=c3a26375-a35b-59f3-817e-cc924e78c797
302590
+ //# debugId=dcd2bdc6-2856-5137-856d-e6285eab649f
package/dist/bin/dvbd.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]="1b7f906b-cd22-5abd-ba0e-247f6e62494e")}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]="5ddc7bf8-894e-5416-96fb-174e8e132a1f")}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";
@@ -64833,9 +64833,9 @@ var init_sentry = __esm({
64833
64833
  uncaughtExceptionMonitorInstalled = false;
64834
64834
  currentDevboxSentryUser = null;
64835
64835
  readBuildMetadata = () => {
64836
- const rawPackageVersion = "1.0.1124";
64837
- const rawGitSha = "a3a2a57d8f49746d693292b4dba145d53943ca0f";
64838
- const rawSentryRelease = "boxes-dev-dvb@1.0.1124+a3a2a57d8f49746d693292b4dba145d53943ca0f";
64836
+ const rawPackageVersion = "1.0.1126";
64837
+ const rawGitSha = "683747375c07cccbbafcab51cbeb89fff6258653";
64838
+ const rawSentryRelease = "boxes-dev-dvb@1.0.1126+683747375c07cccbbafcab51cbeb89fff6258653";
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.1124";
67390
+ const raw = "1.0.1126";
67391
67391
  return trimVersion(raw);
67392
67392
  };
67393
67393
  readNearestPackageMetadata = (basePath) => {
@@ -84919,4 +84919,4 @@ smol-toml/dist/index.js:
84919
84919
  *)
84920
84920
  */
84921
84921
 
84922
- //# debugId=1b7f906b-cd22-5abd-ba0e-247f6e62494e
84922
+ //# debugId=5ddc7bf8-894e-5416-96fb-174e8e132a1f
@@ -113,19 +113,20 @@ If a team member is not a team admin, billing controls usually show status and
113
113
  tell the member to contact a team admin.
114
114
 
115
115
  New teams that sign up at boxes.dev/conductor will receive one month of Pro
116
- free, and new teams that sign up at boxes.dev/alien or boxes.dev/launch-yc
117
- will receive three months. The account that creates the team will get the
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, to prevent abuse of
120
- the offer. Choose **Continue without a card** to take the smaller trial with
121
- 20 free box-hours instead. Each card can claim the offer for only one team,
122
- and the card's bank needs to confirm its security code. If the bank doesn't,
123
- the user can add a different card or continue with the trial. Adding a card
124
- will not enable automatic charges
125
- for extra usage or renew Pro automatically. Pro will end when the offer does
126
- unless a team admin chooses **Keep plan** in Billing; continuing will use the
127
- normal Pro price.
128
- The offer does not replace an existing account's or team's billing.
116
+ free. The account that creates the team will get the first Pro seat, including
117
+ 300 box-hours each month. Extra usage will require prepaid credits. Pro will
118
+ end when the offer does unless a team admin chooses **Keep plan** in Billing;
119
+ continuing will use the normal Pro price. The offer does not replace an
120
+ existing account's or team's billing.
121
+
122
+ The three-month Pro offers at boxes.dev/launch-yc and boxes.dev/alien are
123
+ closed to new teams, and both addresses open the boxes.dev homepage. Teams that
124
+ already claimed one keep it on the same terms. The boxes.dev/launch-yc offer
125
+ required a card, which is not charged automatically for extra usage or to renew
126
+ Pro. Each card could claim it for only one team. If the offer didn't attach
127
+ when the team was created, or boxes.dev later can't accept the card used for
128
+ it, a banner will ask the user to add a card to claim Pro until the original
129
+ offer would have ended.
129
130
 
130
131
  ## Overage Credits
131
132
 
@@ -159,6 +160,55 @@ If credits are low, the product warns users. If credits are depleted and the
159
160
  team is past included usage, compute can be blocked until a team admin buys
160
161
  credits, fixes auto-reload, updates payment, or changes plan.
161
162
 
163
+ ## Mobile Devices
164
+
165
+ Agents on a team's devboxes can build the user's iOS and Android apps on cloud
166
+ Xcode and Gradle builders and run them on cloud iPhone simulators and Android
167
+ emulators. A team admin turns this on for the whole team with the **Mobile
168
+ devices** switch in Team Billing on the website or in **Settings → Billing &
169
+ usage** in the desktop app. Members who aren't team admins see that section
170
+ only while devices are on. The first time a team turns devices on, it receives
171
+ a one-time $10 credit. Turning devices off stops running devices within a
172
+ couple of minutes.
173
+
174
+ Devices are paid from the team's usage credits for each minute they run, and
175
+ every started minute counts as a full minute:
176
+
177
+ - iPhone simulator: $0.10 a minute.
178
+ - Android emulator: $0.05 a minute.
179
+ - Xcode builder: up to $0.10 a minute.
180
+ - Gradle builder: up to $0.05 a minute.
181
+
182
+ Builders cost less while they aren't building. Devices work on every plan, and
183
+ on paid plans they share credits with box-hour overage. A trial team can't buy
184
+ credits, so its devices can use only the one-time credit until a team admin
185
+ chooses a paid plan.
186
+
187
+ A simulator or emulator stops after 3 minutes without activity or 30 minutes
188
+ after it starts, and a builder after 10 idle minutes or an hour. An agent can
189
+ raise these limits when it starts a device, up to an hour idle and 2 hours in
190
+ total. A device open in the desktop Devices pane counts as active. All of a
191
+ devbox's devices stop when the devbox sleeps, and each devbox can run one
192
+ device of each kind at a time.
193
+
194
+ Before a device starts, the team's credits need to cover running it until its
195
+ time limit, for example $3 for an iPhone simulator with the default 30-minute
196
+ limit. Amounts set aside for other devices that haven't been charged yet don't
197
+ count as available. The team pays only for the minutes the device ran, and the
198
+ charge is posted a few minutes after the device stops. When credits are too
199
+ low, the agent's request fails with a message saying whether a team admin can
200
+ buy credits or needs to choose a plan; if auto-reload is on, boxes.dev also
201
+ starts a reload.
202
+
203
+ The Mobile devices section lists prices and **Pending device charges**. Team
204
+ admins also see **Recent sessions**, with each device's member, project, run
205
+ time, and charge. While a device runs, the desktop sidebar's usage popover
206
+ shows its run time and estimated cost so far.
207
+
208
+ While devices are on, agents on the team's devboxes get the
209
+ `boxes-mobile-devices` skill and drive devices with the `lim` command. While
210
+ they're off, `lim` returns 403 and a team admin needs to turn them on.
211
+
162
212
  ## Awake Devbox Limits
163
213
 
164
214
  Awake devbox limits count customer-active awake devboxes. A devbox that is
@@ -24,13 +24,19 @@ The workbench has a few persistent areas:
24
24
  thread is selected and hidden when the left pane
25
25
  is too narrow to fit it. A thread inside a collapsed automation stays hidden
26
26
  until you expand that automation. The
27
- content pane's title bar starts with box status, metrics, and ports when
28
- a Template box or devbox is selected, and ends with the
29
- Terminal/Files/Git/Review/Browser pane control as icon-only buttons that show
27
+ content pane's title bar starts with box status, metrics, and ports when a
28
+ Template box or devbox is selected. The Git branch sits on the right beside
29
+ the tool buttons. Open the branch to enter Git/Review. Its summary shows
30
+ clean status, changed lines, conflicts, or commits ahead; hover over it for
31
+ pending changes. The titlebar ends with the Terminal/Files/Browser pane
32
+ control as icon-only buttons that show
30
33
  their names on hover; update notices appear in the middle when available.
31
34
  If the app loses its connection, an Offline or Reconnecting badge appears
32
35
  beside the pane control and clears on its own once boxes.dev is reachable
33
36
  again.
37
+ A devbox's status control shows **Ready**, **Asleep**, **Waking…**,
38
+ **Connecting**, or **Snapshotting…** as its state changes. When there are no ports, **Ports**
39
+ shows only its icon.
34
40
  - The left pane starts with the project selector, Project settings,
35
41
  and thread search. Below them, **New thread**, **New automation**,
36
42
  **Integrations**, and **Coordinator** when available open their respective
@@ -65,11 +71,14 @@ The workbench has a few persistent areas:
65
71
  near-full-window overlays.
66
72
 
67
73
  The titlebar pane control switches the aux pane between Terminal, Files,
68
- Git/Review, and Browser. The app menu can show or hide the Agent pane. At least
74
+ Git/Review, and Browser, plus Devices while the team has mobile devices on
75
+ (see [Devices](#devices)). The app menu can show or hide the Agent pane. At least
69
76
  one main area stays visible. A new devbox starts with no aux pane open. The
70
77
  Template box and each devbox then remember their last aux-pane choice
71
78
  independently, so returning to a box restores its previous pane. Pane widths
72
- can be resized. Showing Terminal reattaches the box's open terminal
79
+ can be resized. Opening a tool preserves the left sidebar's width when the
80
+ window has room for the conversation and tool at their minimum widths.
81
+ Showing Terminal reattaches the box's open terminal
73
82
  sessions, or starts one if it has none, and closing the last terminal tab
74
83
  closes the pane.
75
84
 
@@ -786,6 +795,31 @@ empty. The agent receives each comment with a DOM-aware element reference,
786
795
  including the page URL, selectors, accessibility identity, visible text, and
787
796
  element geometry.
788
797
 
798
+ ## Devices
799
+
800
+ While the team has mobile devices on (see `billing-and-limits.md`), the
801
+ titlebar pane control includes **Devices**. The Devices pane shows the live
802
+ screen of the iPhone simulator or Android emulator that an agent is running on
803
+ the selected devbox, and a dot on the button marks a running device. The button
804
+ also stays visible while a device is still running after devices were turned
805
+ off.
806
+
807
+ The pane starts view-only. **Interact** sends the user's clicks and typing to
808
+ the device, and **Stop** stops it. When an agent runs both an iPhone simulator
809
+ and an Android emulator, buttons at the top of the pane switch between them.
810
+ Running Xcode and Gradle builders have no screen; a hammer icon at the top of
811
+ the pane lists them, and its menu can stop each one. The pane can pop out into
812
+ a near-full-window overlay. Closing the pane doesn't stop a device.
813
+
814
+ When an app on the device starts using the microphone or camera, the pane asks
815
+ the user whether to share theirs, for example "An app on the iPhone simulator
816
+ wants to use your microphone." The answer lasts until the device stops or the
817
+ window reloads. After **Allow**, macOS may also ask for access. Until the user
818
+ allows it, the app hears silence and sees black frames.
819
+
820
+ The mobile app doesn't show devices. Agents can show screenshots and
821
+ recordings of the app in the thread instead.
822
+
789
823
  ## Ports
790
824
 
791
825
  The ports control in the titlebar shows a singular or plural count of localhost
@@ -67,8 +67,8 @@ Use this terminology consistently:
67
67
  - `fork-workflows.md`: when to use a devbox, how devbox work starts, file
68
68
  movement on devboxes, testing, merging or pushing changes, and cleanup.
69
69
  - `desktop-workbench.md`: the desktop app layout, thread list, transcript pane,
70
- Template box page, terminal pane, files, ports, box controls, and settings
71
- entry points.
70
+ Template box page, terminal pane, files, ports, the Devices pane, box
71
+ controls, and settings entry points.
72
72
  - `ui-references.md`: supported inline references for showing users where
73
73
  desktop controls, settings, and other threads live while explaining them.
74
74
  - `files-git-and-review.md`: file viewer, diffs, media/download handling,
@@ -119,8 +119,8 @@ Use this terminology consistently:
119
119
  snapshot identity rotation, native cleanup, incident removal, and version-one
120
120
  limits.
121
121
  - `billing-and-limits.md`: plans, box-hours, awake boxes, awake devbox
122
- limits, project limits, usage, overages, checkout, and billing portal
123
- behavior.
122
+ limits, project limits, usage, overages, mobile devices (iPhone simulators,
123
+ Android emulators, and builders), checkout, and billing portal behavior.
124
124
  - `security-and-data.md`: setup uploads, secrets, auth storage at a product
125
125
  level, machine trust model, project deletion, account deletion, and support
126
126
  boundaries.
@@ -252,17 +252,30 @@ Template box and save a snapshot without a thread on the Template box:
252
252
  dvb-onbox template-box exec -- git -C /home/boxes/example status --short
253
253
  dvb-onbox template-box exec --cwd /home/boxes/example -- direnv allow
254
254
  dvb-onbox template-box run --script-file /home/boxes/setup-change.sh \
255
- --idempotency-key <stable-key> --json
255
+ --timeout-seconds 480 --idempotency-key <stable-key> --json
256
256
  dvb-onbox template-box snapshot --json
257
257
  ```
258
258
 
259
259
  Each command wakes a sleeping Template box and runs as its `boxes` user.
260
260
  `exec` runs one noninteractive command for up to 120 seconds with 1 MiB of
261
- output per stream. `run` sends a regular script file of up to 3 MiB to `bash`,
262
- runs it for up to 8 minutes, and returns up to 4 MiB per output stream; use it
263
- to write files on the Template box. Split longer work into scripts that each
264
- finish within that limit. `snapshot` waits for the new snapshot that
265
- future devboxes will use. Take one only when the user wants the change to reach
261
+ output per stream. `run` sends a regular script file of up to 3 MiB to `bash`
262
+ and returns up to 4 MiB per output stream; use it to write files on the
263
+ Template box. The default 8-minute timeout suits most scripts. Set a longer
264
+ `--timeout-seconds`, up to 3600, only for a script you expect to take more than
265
+ 8 minutes, and keep it close to the expected time, because a script that hangs
266
+ will keep the Template box awake until its timeout. `run` waits up to 5 minutes
267
+ for the script, or for `--wait-seconds` (up to 3600); pass a value below your shell tool's timeout. If the script is still
268
+ running when the wait ends, `run` fails with `command_running` and a request
269
+ ID, and the script keeps running on the Template box, which stays awake until
270
+ it finishes. To wait again and get the output, run
271
+ `dvb-onbox template-box result --request-id <request-id> --json`. boxes.dev
272
+ returns the output only once, so a later `result` reports
273
+ `output_unavailable`. If `run` is interrupted before it prints a result, run
274
+ the same command again with the same idempotency key; boxes.dev won't start
275
+ the script a second time, and `run` will wait for the original run instead.
276
+ A Template box on an older version of boxes.dev allows
277
+ only 8 minutes, and `run` says so when you ask for longer. `snapshot` waits
278
+ for the new snapshot that future devboxes will use. Take one only when the user wants the change to reach
266
279
  future devboxes. Ordinary shell commands still act on the current devbox.
267
280
 
268
281
  ## Project And Team Template Settings
@@ -2981,17 +2994,34 @@ dvb-onbox team-template create status --idempotency-key <stable-key> --json
2981
2994
  dvb-onbox team-template edit-box status --edit-box <edit-box-id> --json
2982
2995
  ```
2983
2996
 
2984
- Use the target commands below to finish the filesystem setup. For a bounded
2985
- script that may take longer than two minutes, use a regular file and a stable
2986
- key; it runs through the same attested target access and accepts up to 8
2987
- minutes, 3 MiB of script input, and 4 MiB per output stream. Split longer work
2988
- into scripts that each finish within that limit:
2997
+ Use the target commands below to finish the filesystem setup. For a script
2998
+ that may take longer than two minutes, use a regular file and a stable key.
2999
+ `edit-box run` sends it through the same attested target access, accepts up to
3000
+ 3 MiB of script input, and returns up to 4 MiB per output stream:
2989
3001
 
2990
3002
  ```bash
2991
3003
  dvb-onbox team-template edit-box run --edit-box <edit-box-id> \
2992
3004
  --script-file /home/boxes/setup-team-template.sh \
2993
- --idempotency-key <stable-key> --json
2994
- ```
3005
+ --timeout-seconds 480 --idempotency-key <stable-key> --json
3006
+ ```
3007
+
3008
+ The default 8-minute timeout suits most scripts. Set a longer
3009
+ `--timeout-seconds`, up to 3600, only for a script you expect to take more than
3010
+ 8 minutes, and keep it close to the expected time, because a script that hangs
3011
+ will keep the edit box awake until its timeout.
3012
+
3013
+ `run` waits up to 5 minutes for the script, or for `--wait-seconds` (up to
3014
+ 3600); pass a value below your shell tool's timeout. If the script is still
3015
+ running when the wait ends, `run` fails with `command_running` and a request
3016
+ ID, and the script keeps running on the edit box, which stays awake until it
3017
+ finishes. To wait again and get the output, run
3018
+ `dvb-onbox team-template edit-box result --request-id <request-id> --json`.
3019
+ boxes.dev returns the output only once, so a later `result` reports
3020
+ `output_unavailable`. If `run` is interrupted before it prints a result, run
3021
+ the same command again with the same idempotency key; boxes.dev won't start
3022
+ the script a second time, and `run` will wait for the original run instead.
3023
+ An edit box on an older version of
3024
+ boxes.dev allows only 8 minutes, and `run` says so when you ask for longer.
2995
3025
 
2996
3026
  Read back every credential-free setting with `team-template show`. If research
2997
3027
  changes the intended settings, check the revised whole spec and apply it with
@@ -3055,7 +3085,10 @@ target fails without choosing another template.
3055
3085
  Several `exec`, `edit-box run`, and `push` commands can run on the same editing
3056
3086
  machine at once, and the machine stays awake while they run. When a command
3057
3087
  reaches its time limit, boxes.dev stops the command and the background
3058
- processes it started, then reports exit code 124 with `timedOut: true`.
3088
+ processes it started, then reports exit code 124 with `timedOut: true`. When
3089
+ access to the editing session ends, boxes.dev stops any `edit-box run` script
3090
+ that is still running, and `run` or `result` reports that the command was
3091
+ stopped.
3059
3092
 
3060
3093
  `push` copies one regular file from the source project Template box into the
3061
3094
  Team Template checkout. Both paths must be absolute and below `/home/boxes`.
@@ -3067,7 +3100,8 @@ failed transfer does not leave a partial destination file.
3067
3100
  If a connection is lost after a command starts, boxes.dev does not run it a
3068
3101
  second time. The command reports a request ID and may say that its output is
3069
3102
  unavailable; verify filesystem state before deciding whether another command
3070
- is appropriate. Retrying the same `push` request after an uncertain response
3103
+ is appropriate. For `edit-box run`, `edit-box result --request-id <request-id>`
3104
+ returns the result if it hasn't been read yet. Retrying the same `push` request after an uncertain response
3071
3105
  recovers its recorded result instead of writing the destination twice.
3072
3106
 
3073
3107
  ### Work on a Team Template from a member devbox
@@ -3099,7 +3133,8 @@ dvb-onbox team-template push --template <team-template-id> \
3099
3133
  --source /home/boxes/file-on-devbox \
3100
3134
  --destination /home/boxes/file-in-team-template
3101
3135
  dvb-onbox team-template edit-box run --edit-box <edit-box-id> \
3102
- --script-file /home/boxes/setup-change.sh --idempotency-key <stable-key> --json
3136
+ --script-file /home/boxes/setup-change.sh --timeout-seconds 480 \
3137
+ --idempotency-key <stable-key> --json
3103
3138
  dvb-onbox team-template edit-box status --edit-box <edit-box-id> --json
3104
3139
  dvb-onbox team-template edit-box save --edit-box <edit-box-id> \
3105
3140
  --idempotency-key <stable-key> --json
@@ -365,6 +365,9 @@ until the user finishes each step on GitHub and boxes.dev can access every
365
365
  repository, so the agent doesn't need the user to say they're done. The setup
366
366
  page names the step: a **Connect GitHub** button while the user signs in, and
367
367
  the repositories and an **Open GitHub** link while boxes.dev needs access.
368
+ When `check` is blocked on GitHub while GitHub isn't connected or needs
369
+ reconnecting, the page shows a **Connect GitHub** or **Reconnect GitHub**
370
+ button; after signing in, the user asks the agent to re-run `check`.
368
371
  When GitHub returns the user to **Account** after an App install, update, or
369
372
  request, Account says what happened and tells a user in setup to go back to
370
373
  their coding agent. `dvb agent-init check` verifies the exact writable
@@ -405,7 +408,9 @@ boxes.dev recognizes that generated block, saves its branch defaults separately,
405
408
  and prepares the checkout before running any remaining startup commands. Normally
406
409
  configure the project's starting branch, usually `main`, so new devboxes fetch
407
410
  fresh remote code. Keep the generated block aligned with the chosen setup
408
- branch when adding application setup commands after it. If the chosen branch
411
+ branch. Commands after it run on every new devbox within the startup timeout,
412
+ so keep them to quick steps such as a locked dependency install; one-time
413
+ setup belongs on the Template box. If the chosen branch
409
414
  exists only locally, explain that it cannot be fetched and confirm whether to
410
415
  use its clean committed state from the Template snapshot instead. Omit the
411
416
  generated block for that choice; unfinished work remains saved separately.
@@ -417,15 +422,17 @@ A missing remote default does not require publishing a branch; the user can
417
422
  choose a local branch as above. After setup, clearing the startup script does
418
423
  not remove saved branch defaults.
419
424
 
420
- Template maintenance starts unconfigured. When the repository needs ongoing
421
- environment updates, the coding agent should author the maintenance script and
422
- its GitHub watches together so the watched files match the work the script
423
- performs. Declared watches need boxes.dev GitHub App pull access and a current
424
- default branch even when project Git uses SSH. The launch review reports the
425
- lifecycle timeouts, maintenance timeout, watch and path counts, and that the
426
- repeating schedule is off, baselines are fresh, and setup will not run the
427
- maintenance script. Script bodies stay in the reviewed manifest instead of
428
- being repeated in the summary.
425
+ Template maintenance starts unconfigured. The coding agent should recommend it
426
+ for most projects and keep the script small, usually updating the starting
427
+ branch and installing locked dependencies so the Template box doesn't go
428
+ stale. It should author the maintenance script and its GitHub watches together
429
+ so the watched files match the work the script performs. Declared watches
430
+ need boxes.dev GitHub App pull access and a current default branch even when
431
+ project Git uses SSH. The launch review reports the lifecycle timeouts,
432
+ maintenance timeout, watch and path counts, and that the repeating schedule is
433
+ off, baselines are fresh, and setup will not run the maintenance script.
434
+ Script bodies stay in the reviewed manifest instead of being repeated in the
435
+ summary.
429
436
 
430
437
  After the Template box is registered, setup applies the reviewed lifecycle and
431
438
  maintenance configuration before completion. If a declared repository loses
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@boxes-dev/dvb-runtime",
3
- "version": "1.0.1124",
3
+ "version": "1.0.1126",
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-10T20:43:34Z"
80
+ "devboxReleasedAt": "2026-11-11T22:19:37Z"
81
81
  }