@boxes-dev/dvb-runtime 1.0.1066 → 1.0.1068

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
@@ -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]="69a5c6a9-80c5-56fe-a38e-2b80f6682217")}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]="ac796f29-1a11-5a49-8449-1955c0948204")}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";
@@ -64674,9 +64674,9 @@ var init_sentry = __esm({
64674
64674
  uncaughtExceptionMonitorInstalled = false;
64675
64675
  currentDevboxSentryUser = null;
64676
64676
  readBuildMetadata = () => {
64677
- const rawPackageVersion = "1.0.1066";
64678
- const rawGitSha = "264816c4f2dbdb6e253743fa1b1c9220d63d69e2";
64679
- const rawSentryRelease = "boxes-dev-dvb@1.0.1066+264816c4f2dbdb6e253743fa1b1c9220d63d69e2";
64677
+ const rawPackageVersion = "1.0.1068";
64678
+ const rawGitSha = "2568b3433ede13bc0c6b1399d95ffa38a55bacac";
64679
+ const rawSentryRelease = "boxes-dev-dvb@1.0.1068+2568b3433ede13bc0c6b1399d95ffa38a55bacac";
64680
64680
  const packageVersion = typeof rawPackageVersion === "string" ? rawPackageVersion : void 0;
64681
64681
  const gitSha = typeof rawGitSha === "string" ? rawGitSha : void 0;
64682
64682
  const sentryRelease = typeof rawSentryRelease === "string" ? rawSentryRelease : void 0;
@@ -66893,7 +66893,7 @@ var init_packageVersion = __esm({
66893
66893
  return path8.join(process.cwd(), "dvb");
66894
66894
  };
66895
66895
  readEmbeddedPackageVersion = () => {
66896
- const raw = "1.0.1066";
66896
+ const raw = "1.0.1068";
66897
66897
  return trimVersion(raw);
66898
66898
  };
66899
66899
  readNearestPackageMetadata = (basePath) => {
@@ -80046,4 +80046,4 @@ smol-toml/dist/index.js:
80046
80046
  *)
80047
80047
  */
80048
80048
 
80049
- //# debugId=69a5c6a9-80c5-56fe-a38e-2b80f6682217
80049
+ //# debugId=ac796f29-1a11-5a49-8449-1955c0948204
@@ -414,7 +414,10 @@ claiming that permission is missing.
414
414
  When the App has read-only Actions access, reviewed `gh workflow run` and
415
415
  `gh run rerun` commands will suggest personal sign-in. This advice does not
416
416
  block, retry, or replay the command. After approval, rerun the command explicitly.
417
- Other GitHub failures do not automatically start authorization. If approval is
417
+ Other GitHub failures do not automatically start authorization. A command that
418
+ needs a permission the App lacks fails with GitHub's `Resource not accessible
419
+ by integration` error; see "GitHub CLI Command Is Denied" in
420
+ `troubleshooting.md`. If approval is
418
421
  denied, a code expires, or the wrong account was used, run `gh auth login` again
419
422
  and approve with the displayed account.
420
423
 
@@ -351,7 +351,11 @@ Configure agents in the desktop app. Each agent has its own list of saved
351
351
  logins and API keys, and the checked row is the one your devboxes use. Tap
352
352
  **Add** beside an agent to sign in or save an API key. Tap a saved row to
353
353
  choose **Use this account**, **Re-authenticate** or **Edit API key**, **Check
354
- now**, or **Remove**.
354
+ now**, or **Remove**. An older Claude account labeled **Setup token** offers
355
+ **Switch to claude.ai login** instead of **Re-authenticate**. Once a claude.ai
356
+ login is saved, the **Allow claude.ai connectors** switch below the Claude
357
+ accounts controls whether new Claude sessions can use the connectors added on
358
+ claude.ai.
355
359
 
356
360
  To sign in to Codex, tap **Log in with ChatGPT**. The app shows a one-time
357
361
  code, and **Open ChatGPT** copies it and opens the ChatGPT device sign-in page.
@@ -363,10 +367,13 @@ approve access. Claude will show a code; copy it, return to the app, paste it,
363
367
  and tap **Continue**. Closing either sign-in cancels it.
364
368
 
365
369
  When the active Codex or Claude account needs you to sign in again, or its API
366
- key was rejected, a banner appears at the top of the app. **Reconnect** opens
367
- that agent's sign-in, or opens Agent accounts when both agents need attention
368
- or a key needs replacing. Dismissing the banner hides it until the app restarts
369
- or another account starts failing.
370
+ key was rejected, a banner appears at the top of the app. A claude.ai login
371
+ also shows one three days before its sign-in deadline, which comes about
372
+ every four weeks. **Reconnect**
373
+ opens that agent's sign-in, or opens Agent accounts when both agents need
374
+ attention or a key needs replacing. Dismissing the banner hides it until the
375
+ app restarts or another account starts failing; dismissing a sign-in reminder
376
+ does not hide a later failure.
370
377
 
371
378
  ## Mobile Versus Desktop
372
379
 
@@ -280,8 +280,11 @@ page once the upload starts, whether setup is running or stopped, deletes the
280
280
  Template box, if one was created, and the setup state saved on the computer,
281
281
  including the manifest; the project folder is not affected. If setup
282
282
  stops after the thread starts, the workbench banner shows the error and the
283
- same retry command. A failure while bundling, before the upload starts,
284
- appears only in the agent's `dvb agent-init` output. The agent's command
283
+ same retry command. When the cause is an unexpected error in boxes.dev, the
284
+ page and banner describe it in plain terms and suggest emailing hi@boxes.dev if
285
+ setup stops at the same step after a retry; the agent's `dvb agent-init
286
+ status` still shows the technical error. A failure while bundling, before the
287
+ upload starts, appears only in the agent's `dvb agent-init` output. The agent's command
285
288
  needs to be running when the Template box asks for the bundle's decrypt key;
286
289
  if the Template box has waited more than a minute, the setup page says setup
287
290
  is waiting for the coding agent and asks the user to have it run `dvb
@@ -396,6 +399,29 @@ devboxes. On macOS, Configure agents is in the boxes.dev app menu. Saving a new
396
399
  API key does not replace a working subscription that is already selected; the
397
400
  user selects the key to switch to it.
398
401
 
402
+ **Log in with Claude** saves a claude.ai login, the same kind of sign-in
403
+ Claude Code gets from `/login` on a computer. Claude on Template boxes and
404
+ devboxes then has the account's claude.ai features: skills and plugins synced
405
+ from claude.ai and the connectors the user added there, such as Gmail.
406
+ boxes.dev keeps the sign-in current, but Claude requires a new sign-in about
407
+ every four weeks; Claude sets the exact date at each sign-in. Three days
408
+ before that deadline, the account's row shows **Sign in again by** a date and
409
+ the mobile app shows a reminder banner; after it passes, Claude reports that
410
+ the sign-in expired until the user signs in again. Accounts connected before claude.ai logins were available show
411
+ **Setup token**. They keep working without claude.ai features, and the row's
412
+ **Switch to claude.ai login** action signs in again and converts that saved
413
+ account to a claude.ai login. An older account saved without a Claude account
414
+ ID gets a new row for the login instead, which becomes active; the user can
415
+ then remove the old row. Desktop app versions older than this feature can only
416
+ save setup tokens, so their menus show **Re-authenticate** instead; update the
417
+ desktop app, or switch from the mobile app. Claude API keys are unchanged.
418
+
419
+ Once a claude.ai login is saved, Configure agents and mobile Agent accounts
420
+ show **Allow claude.ai connectors**, which is on by default. Turning it off
421
+ keeps claude.ai connectors out of new Claude sessions, including automation
422
+ and Slack runs that use the account; synced skills and plugins still load.
423
+ Sessions that are already running keep their connectors until they restart.
424
+
399
425
  Each saved subscription row in desktop Configure agents shows a small bar for
400
426
  the weekly limit's remaining usage. A 5-hour bar appears below it only when
401
427
  that limit is low (below 20% left) or the account has no weekly limit. Hovering
@@ -102,6 +102,14 @@ key, depending on the agent. boxes.dev runs the real agent tools the user
102
102
  authorizes; it does not replace them with a separate model account. If an agent
103
103
  auth flow is broken or stale, users can reconnect from Configure agents.
104
104
 
105
+ For a claude.ai login, boxes.dev keeps the login's long-lived renewal
106
+ credential and renews the sign-in centrally. Template boxes and devboxes
107
+ receive only Claude's current short-lived access, written where Claude Code
108
+ reads its own login. A claude.ai login also lets Claude use the connectors the
109
+ user added on claude.ai, such as Gmail, so an agent on a box can reach those
110
+ services; **Allow claude.ai connectors** in Configure agents or Agent accounts
111
+ turns that off for new sessions.
112
+
105
113
  Agent credentials should be treated like other development credentials. If a
106
114
  user no longer wants an agent credential available in boxes.dev, they should
107
115
  disconnect or rotate it through the relevant agent account and
@@ -154,7 +154,8 @@ usage. It does not copy either teammate's existing devbox filesystem.
154
154
 
155
155
  An allowed teammate's request has the same reach as the owner's own request:
156
156
  the agent can use anything the owner's devbox can reach, including code,
157
- credentials, and connected accounts. Owners should allow only teammates they
157
+ credentials, and connected accounts, such as the owner's claude.ai connectors
158
+ when Claude uses a claude.ai login. Owners should allow only teammates they
158
159
  would trust with that access, including on named commands that allow
159
160
  teammates.
160
161
 
@@ -344,6 +344,8 @@ use the Team Template's current saved files instead.
344
344
  ## Editing And Saving
345
345
 
346
346
  Open a Team Template, then choose **Take control** to start an editing session.
347
+ If the editing machine can't start, the detail page says so until the next
348
+ attempt, and the saved version stays unchanged.
347
349
  The focused, full-window editor uses the same workbench arrangement as a
348
350
  project: Team Template threads on the left, the selected Codex or Claude
349
351
  conversation in the middle, and the Terminal, Files, Git, or Browser tool on
@@ -228,8 +228,11 @@ Open **Integrations → MCPs** in the desktop app to manage remote MCP servers i
228
228
  one list. Choose **Add MCP**, then paste either the server URL or the Codex or
229
229
  Claude setup command supplied by the provider, and choose **Continue**.
230
230
  boxes.dev detects the supported
231
- remote transport and the authentication method, so the form asks only for the
232
- name, the scope, and which agents to add the connection to. The URL, the
231
+ remote transport and the authentication method, so the form usually asks only
232
+ for the name, the scope, and which agents to add the connection to. When a
233
+ server offers OAuth but also works without an account, the form also shows
234
+ **Sign-in** with **Sign in** and **Don't sign in**; choosing **Don't sign in**
235
+ saves the connection with no authentication. The URL, the
233
236
  authentication mode, and the name the agents use sit under **Advanced**, which
234
237
  opens on its own when a header or API key still has to be typed in. New
235
238
  connections default to **This project**; choose **All projects** only when the
@@ -241,8 +244,10 @@ authorize the connection.
241
244
  Codex and Claude are enabled independently from the same connection row. OAuth
242
245
  opens a local browser sign-in for the selected agent, so enabling both agents
243
246
  usually requires one provider consent for Codex and another for Claude. API-key
244
- headers and servers with no authentication do not open an OAuth flow. boxes.dev
245
- keeps centrally managed definitions and credentials current on every applicable
247
+ headers and servers with no authentication do not open an OAuth flow. When setup
248
+ found that an OAuth server also works without an account, its row offers **Use
249
+ without signing in** while no agent is signed in; choosing it switches the
250
+ connection to no authentication. boxes.dev keeps centrally managed definitions and credentials current on every applicable
246
251
  Template box and devbox, including future and sleeping machines, without a
247
252
  snapshot. A project-scoped connection can use a different account from a
248
253
  connection in another project.
@@ -159,6 +159,15 @@ Codex can be connected through ChatGPT login or an API key. Claude can be
159
159
  connected through Claude login or an API key. After reconnecting, retry the
160
160
  thread or start a new one.
161
161
 
162
+ Likewise, do not run `/login` or `/logout` in Claude on a managed machine:
163
+ boxes.dev manages Claude's sign-in there. A claude.ai login needs a new
164
+ sign-in about every four weeks; reconnect it from Configure agents or Agent
165
+ accounts when the reminder appears. If Claude on a box lacks the skills,
166
+ plugins, or connectors you have on claude.ai, check that the active Claude
167
+ account says **claude.ai login** rather than **Setup token** (use **Switch to
168
+ claude.ai login** from its menu) and, for connectors, that **Allow claude.ai
169
+ connectors** is on. Start a new Claude session after changing either.
170
+
162
171
  If an MCP server needs auth, open **Integrations → MCPs** and use the agent chip
163
172
  on that connection. In a project with a Template box, MCP servers installed
164
173
  directly there are under **Template-managed MCPs** in the same place. Team
@@ -362,6 +371,32 @@ permissions. Without personal access, boxes.dev checks that the App can reach
362
371
  every known project repository before issuing its credential. With personal
363
372
  access, GitHub enforces the user's permissions on each CLI command.
364
373
 
374
+ ## GitHub CLI Command Is Denied
375
+
376
+ If `gh` is signed in but GitHub rejects a command with `HTTP 403: Resource not
377
+ accessible by integration`, the command used boxes.dev GitHub App access, and
378
+ the App lacks the permission that command needs. Repeat a `gh api` request with
379
+ `-i` to see the `X-Accepted-GitHub-Permissions` response header, which names the
380
+ missing permission, such as `actions=write` or `issues=write`. The App can view
381
+ Actions runs, but it can't start, rerun, or cancel them, enable or disable
382
+ workflows, or create issues. Only `gh workflow run` and `gh run rerun` print a
383
+ sign-in suggestion; other commands, including `gh api` requests, show only
384
+ GitHub's error.
385
+
386
+ To let `gh` use the user's own GitHub permissions, connect optional personal
387
+ access. In **Account** settings or **Integrations → GitHub**, choose **Enable**
388
+ under **Full GitHub CLI access (optional)**. Alternatively, run `gh auth login`
389
+ on the Template box or devbox. It will print a one-time code and a GitHub
390
+ approval URL, then wait until the user approves with the GitHub account
391
+ connected to boxes.dev. An agent that runs it should give the user the code and
392
+ URL. After approval, managed `gh` will prefer personal access on all of the
393
+ user's Template boxes and devboxes; retry the original command.
394
+
395
+ Personal access can't exceed the user's own GitHub role. Some organizations
396
+ also need to approve the official GitHub CLI; if Integrations warns that
397
+ personal access can't reach a repository, follow that warning's **GitHub
398
+ permissions** action.
399
+
365
400
  ## Billing Or Limit Blocks
366
401
 
367
402
  Common billing blocks include:
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@boxes-dev/dvb-runtime",
3
- "version": "1.0.1066",
3
+ "version": "1.0.1068",
4
4
  "description": "Runtime for the boxes.dev CLI. Install @boxes-dev/dvb to use the CLI.",
5
5
  "homepage": "https://boxes.dev",
6
6
  "type": "module",
@@ -77,5 +77,5 @@
77
77
  "e2b": "^2.18.0",
78
78
  "ink-testing-library": "^4.0.0"
79
79
  },
80
- "devboxReleasedAt": "2026-10-11T01:33:37Z"
80
+ "devboxReleasedAt": "2026-10-12T14:26:27Z"
81
81
  }