@boxes-dev/dvb-runtime 1.0.1091 → 1.0.1093

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.
@@ -117,12 +117,26 @@ configured, the page shows a short summary with a **Set up maintenance**
117
117
  button that opens the form. The script runs as the `boxes` user in the
118
118
  project's working directory, with a user-selected timeout of up to eight
119
119
  minutes. **Run now** is available after the policy is saved.
120
+
121
+ A maintenance script should fetch and fast-forward each repository it depends
122
+ on to its default branch, then install locked dependencies and refresh
123
+ generated files or tooling without prompts. It should exit nonzero with a
124
+ clear message when a checkout has uncommitted changes or is on another
125
+ branch, when a required value is missing, or when an update fails; a script
126
+ that skips its update and exits 0 saves a stale snapshot. Credentials belong
127
+ in managed environment files, not in the script. The runner starts from a
128
+ login shell, then runs the script with noninteractive bash and
129
+ `set -e -o pipefail`, with `HOME=/home/boxes` and `/opt/devbox-tools/bin` first
130
+ on PATH. Interactive `~/.bashrc` setup, such as nvm's shell hook, does not
131
+ load. Agent setup tests a proposed script twice in this environment before
132
+ saving it.
120
133
  Automatic scheduling is optional; the supported cadences are every 6 hours,
121
134
  every 12 hours, nightly, and weekly.
122
135
 
123
136
  With the separate **Edit template maintenance** Agent permission, a managed
124
137
  agent on the Template box can use `dvb-onbox project maintenance get/apply` to
125
- author the script and complete GitHub watch set together. The command copies a
138
+ author the script and complete GitHub watch set together, and `run` to start
139
+ the saved script and follow its result. The command copies a
126
140
  script and version-1 watch JSON file from regular files under `/home/boxes`,
127
141
  requires the revision returned by `get`, and requires explicit confirmation
128
142
  before removing an editable watch. It preserves the existing repeating
@@ -169,6 +183,25 @@ indicator. Provider-side detection failures stay visible on the affected watch
169
183
  without raising that red indicator; retry them and contact support if they
170
184
  persist.
171
185
 
186
+ The desktop workbench also shows the owner of an ordinary project a maintenance
187
+ attention banner. **Maintenance settings** opens the relevant card. A failed
188
+ or timed-out script offers **Ask an agent to fix it**, which creates a fresh,
189
+ unsent Template box draft with the full saved script, the failed run's script
190
+ if it differs, and the full recorded output tail. It does not enable Agent
191
+ permissions. Dismissing the banner hides it for seven days on that device and
192
+ does not acknowledge the failure or clear the Template row's attention icon.
193
+
194
+ When no maintenance policy exists, a default-branch checkout at least 100
195
+ commits behind GitHub gets a separate reminder to pull or set up maintenance,
196
+ with an agent setup draft shortcut. The check uses the Template's last
197
+ observed HEAD and GitHub without waking the box. It skips unknown commits,
198
+ inaccessible repositories and other branches, and names the most-behind
199
+ repository when there are several. Any saved policy suppresses this reminder.
200
+ After dismissal it returns only after seven days and at least 100 additional
201
+ missing commits. Both dismissals are per viewer, Template and device. These
202
+ banners apply to ordinary projects; Team Template administration has its own
203
+ maintenance workflow.
204
+
172
205
  Maintenance and snapshot creation never overlap, but maintenance may interrupt
173
206
  someone actively using the Template box. Avoid editing or running important
174
207
  interactive work there while a maintenance run is expected.
@@ -241,6 +241,25 @@ start selected under **Add to**; a pasted Codex or Claude setup command selects
241
241
  only its agent. Adjust the selection, then choose **Add MCP** to save and
242
242
  authorize the connection.
243
243
 
244
+ Slack's official MCP server, `https://mcp.slack.com/mcp`, accepts OAuth sign-in
245
+ only from apps registered with Slack, so boxes.dev can't sign in to it. Pasting
246
+ that exact URL in **Add MCP** skips detection, opens **Advanced** with an
247
+ `Authorization` header, and links to the setup steps in the help center. The
248
+ header value is `Bearer ` followed by the user's own Slack user token
249
+ (`xoxp-`). That token comes from an internal or Marketplace Slack app in the
250
+ user's workspace with **Slack Model Context Protocol (MCP) Server** turned on
251
+ under **Agents**, the user token scopes for the wanted tools, and an
252
+ installation by that user; a workspace admin may need to approve the app.
253
+ boxes.dev doesn't renew these tokens, and an app with token rotation turned on
254
+ issues tokens that expire after 12 hours, so use an app without rotation.
255
+ After Slack revokes a token, replace the header value through the row's
256
+ **⋯ → Edit**. On a box, `codex mcp add slack --url
257
+ https://mcp.slack.com/mcp --bearer-token-env-var <VAR>` creates the same
258
+ header connection from a token in that environment variable. Sign-in to any
259
+ other OAuth server that offers neither dynamic client registration nor client
260
+ metadata documents fails with an error saying the provider requires a
261
+ registered app; use an access token header only if that provider issues one.
262
+
244
263
  The mobile app manages the same list under a project's **Project settings →
245
264
  MCPs**, including adding connections and signing in for each agent on the
246
265
  phone. See `mobile.md`.
@@ -373,8 +392,12 @@ blocked from native installation.
373
392
 
374
393
  **Add plugin** in the page header opens a dialog with a Codex tab and a Claude
375
394
  tab. Its single input searches the plugins offered by the marketplaces already
376
- configured on the Template box, and the same input also accepts a marketplace
377
- address or a pasted native command:
395
+ configured on the Template box. For Claude, boxes.dev adds Anthropic's official
396
+ marketplace (`claude-plugins-official`) to the Template box, so the Claude tab
397
+ has plugins to search without any setup, and devboxes get it from a Template
398
+ box snapshot. If the marketplace is removed, boxes.dev adds it back the next
399
+ time the Template box restarts or receives a boxes.dev update. The same input
400
+ also accepts a marketplace address or a pasted native command:
378
401
 
379
402
  - `https://github.com/owner/repo`, or the same address without `https://`
380
403
  - `codex plugin marketplace add <url>` or `claude plugin marketplace add <url>`
@@ -398,15 +421,31 @@ not a public GitHub repository or a plugin that bundles components like MCP
398
421
  servers, hooks, or required configuration that have to be set up on each box.
399
422
  **Install** becomes available once that check finishes.
400
423
 
424
+ When Codex on the Template box is signed in with ChatGPT, the Codex tab also
425
+ names that ChatGPT account by email, and a search there includes plugins from
426
+ OpenAI's catalog for that account. Those rows are labeled **ChatGPT account**.
427
+ Choosing one skips the source check: the plugin is added to the ChatGPT account
428
+ through Codex's own install, not to boxes.dev or the project, so it is neither
429
+ **Managed for this project** nor a **Template box** plugin and needs no
430
+ snapshot. Codex manages it like its other synced plugins, and Codex on the
431
+ Template box stops using it if it signs in to a different account or switches
432
+ to an API key. A plugin that bundles an app, such as Gmail, may still need
433
+ authorization for that app; the page says so after the install. With an
434
+ API-key sign-in the tab says that ChatGPT account plugins are not listed, and
435
+ the API-key catalog's plugins appear as ordinary Template box plugins. This
436
+ needs the Template box's managed Codex to be up to date; an older Codex shows
437
+ the tab without account plugins.
438
+
401
439
  Two collapsed sections hold read-only information and appear only when they have
402
440
  something to show. **Seen only on devboxes** names plugins that reported state
403
441
  places on an ordinary devbox but not on the Template box, along with the
404
442
  devboxes that last reported them. This is saved status only; opening or
405
443
  refreshing the page does not inspect, wake, or change those devboxes. **Synced
406
444
  by Codex** contains provider-backed plugins Codex reports for the signed-in
407
- account and workspace. Codex owns their installation and refresh behavior, and a
408
- Template snapshot is not required for them. A new Codex session is the reliable
409
- boundary for picking up a synced-plugin change.
445
+ account and workspace, including ChatGPT account plugins added from the Codex
446
+ tab, and names that ChatGPT account. Codex owns their installation and refresh
447
+ behavior, and a Template snapshot is not required for them. A new Codex session
448
+ is the reliable boundary for picking up a synced-plugin change.
410
449
 
411
450
  A **Template box** change affects the live Template box immediately, and the
412
451
  page then offers **Snapshot Template box** so future devboxes will inherit it.
@@ -111,7 +111,24 @@ If remote setup pauses at a recoverable step, the setup UI can offer **Retry
111
111
  setup**. Use that when the issue looks temporary or the UI says the step is
112
112
  retryable.
113
113
 
114
- For a local-folder setup's remote Git access failure, choose **Fix Git access**.
114
+ If remote setup cannot verify Git SSH access, the message names the Git host
115
+ and what setup observed:
116
+
117
+ - SSH sign-in succeeded, but the repository couldn't be read. Check the
118
+ repository URL and that the key's account or deploy key can read it.
119
+ - A follow-up SSH connection to the host failed, with the cause, such as
120
+ connection refused, reset, timed out, or host name not found. Check network or
121
+ VPN access from the Template box to that host and port.
122
+ - Sign-in didn't complete, although a follow-up check reached the host's SSH
123
+ server. The key may not be registered with the host, or the host key may have
124
+ changed. For agent-driven setup, `dvb agent-init diagnostics` includes the
125
+ SSH output for further diagnosis.
126
+
127
+ Then choose **Retry setup** to check the same key again. For agent-driven
128
+ setup, the coding agent on the user's computer should run `dvb agent-init
129
+ retry` in the project folder.
130
+
131
+ To change or skip Git access for a local-folder setup, choose **Fix Git access**.
115
132
  boxes.dev removes the incomplete Template box and returns to Finalize Bundle,
116
133
  keeping the approved review and other bundle choices. Restore the named GitHub
117
134
  account's repository access, switch to and verify SSH, or skip Git access before
@@ -15,9 +15,10 @@ control, changes a permission, or creates a resource.
15
15
 
16
16
  Navigation follows the app's ordinary behavior, including Auto-wake when
17
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.
18
+ to thread** returns to your place in the conversation. If you were following
19
+ the latest output, you'll return to the bottom. Escape or another interaction
20
+ dismisses the highlight; reduced-motion preferences remove the travel animation
21
+ and glint.
21
22
 
22
23
  References are relative to the conversation's project and devbox. Specific
23
24
  thread, automation, and Project URL references can identify other items in
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@boxes-dev/dvb-runtime",
3
- "version": "1.0.1091",
3
+ "version": "1.0.1093",
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-18T04:26:46Z"
80
+ "devboxReleasedAt": "2026-10-19T06:13:16Z"
81
81
  }