@boxes-dev/dvb-runtime 1.0.1014 → 1.0.1016
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/agent-init-guides/env-files.md +29 -3
- package/dist/agent-init-guides/flow.md +14 -1
- package/dist/agent-init-guides/manifest.md +4 -0
- package/dist/bin/dvb.mjs +2046 -1961
- package/dist/bin/dvbd.mjs +8 -8
- package/dist/product-docs/SKILL.md +4 -0
- package/dist/product-docs/references/agent-tools.md +3 -3
- package/dist/product-docs/references/automations.md +10 -6
- package/dist/product-docs/references/aws.md +4 -3
- package/dist/product-docs/references/billing-and-limits.md +6 -4
- package/dist/product-docs/references/core-concepts.md +3 -3
- package/dist/product-docs/references/desktop-workbench.md +17 -4
- package/dist/product-docs/references/files-git-and-review.md +8 -5
- package/dist/product-docs/references/fork-workflows.md +21 -9
- package/dist/product-docs/references/glossary.md +5 -2
- package/dist/product-docs/references/linear.md +10 -7
- package/dist/product-docs/references/member-managed-files.md +5 -2
- package/dist/product-docs/references/mobile.md +2 -0
- package/dist/product-docs/references/onbox-agent-tools.md +4 -3
- package/dist/product-docs/references/ports-terminal-and-runtime.md +15 -5
- package/dist/product-docs/references/project-setup.md +20 -10
- package/dist/product-docs/references/security-and-data.md +43 -26
- package/dist/product-docs/references/slack.md +8 -6
- package/dist/product-docs/references/tailscale.md +3 -0
- package/dist/product-docs/references/team-template.md +30 -41
- package/dist/product-docs/references/threads-and-agents.md +32 -15
- package/dist/product-docs/references/troubleshooting.md +36 -23
- package/package.json +2 -2
|
@@ -123,37 +123,54 @@ Existing boxes.dev threads remain.
|
|
|
123
123
|
Disconnecting GitHub removes the stored GitHub user tokens from boxes.dev and
|
|
124
124
|
stops pull-request actions until the user reconnects. Repository access granted
|
|
125
125
|
to the GitHub App is managed separately through **Manage repos**.
|
|
126
|
-
|
|
127
|
-
|
|
128
|
-
|
|
129
|
-
|
|
130
|
-
|
|
131
|
-
|
|
132
|
-
|
|
133
|
-
|
|
134
|
-
|
|
135
|
-
|
|
136
|
-
|
|
137
|
-
|
|
138
|
-
|
|
126
|
+
Disconnecting the main GitHub connection also removes optional personal access
|
|
127
|
+
and schedules that authorization for revocation with GitHub. **Disconnect
|
|
128
|
+
personal access** performs the personal-access removal and revocation without
|
|
129
|
+
disconnecting the main GitHub connection.
|
|
130
|
+
|
|
131
|
+
When automatic Git access uses the GitHub App, the connected user's App
|
|
132
|
+
credential remains encrypted at rest in boxes.dev. When Git needs access, the
|
|
133
|
+
machine requests that credential through a local helper. boxes.dev first checks
|
|
134
|
+
that the exact repository is associated with the project and that the connected
|
|
135
|
+
user still has write access. The token can exist in the boxes.dev service, local
|
|
136
|
+
service, Git process, and snapshot process memory, but is not written to the
|
|
137
|
+
remote URL or a managed credential file.
|
|
138
|
+
|
|
139
|
+
Repository selection is an issuance boundary, not a downscope on the App token
|
|
140
|
+
itself. Code running on the box can request and inspect the App credential,
|
|
141
|
+
whose access is the intersection of the connected user's repositories and the
|
|
142
|
+
repositories and permissions granted to the boxes.dev GitHub App. Current App
|
|
139
143
|
connections use GitHub access tokens that last eight hours. boxes.dev refreshes
|
|
140
144
|
them centrally with GitHub's rotating refresh credential, which remains
|
|
141
145
|
encrypted in boxes.dev and is not copied to Template boxes or devboxes. A user
|
|
142
146
|
who connected before this change may see a one-time connection update; their
|
|
143
147
|
existing access keeps working until they complete it. After that update,
|
|
144
148
|
boxes.dev waits for outstanding machine cache leases to drain before retiring
|
|
145
|
-
the replaced long-lived token. Disconnecting
|
|
146
|
-
future helper issuance after its bounded cache
|
|
147
|
-
revoke
|
|
148
|
-
operation to the connected user.
|
|
149
|
+
the replaced long-lived token. Disconnecting the main GitHub connection or
|
|
150
|
+
removing App access stops future App helper issuance after its bounded cache
|
|
151
|
+
lease, but does not itself revoke an App token already returned to a process.
|
|
152
|
+
GitHub attributes the Git operation to the connected user.
|
|
153
|
+
|
|
154
|
+
Optional personal access uses the official GitHub CLI authorization the user
|
|
155
|
+
approved. Before boxes.dev issues this credential, the personal authorization
|
|
156
|
+
must match the main GitHub identity and pass the exact repository checks for the
|
|
157
|
+
operation. Those checks do not narrow the credential itself: code running on
|
|
158
|
+
the machine can inspect the full token, whose permissions come from the GitHub
|
|
159
|
+
CLI authorization rather than the GitHub App grants. Personal tokens can be
|
|
160
|
+
expiring or non-expiring. **Disconnect personal access** removes the saved
|
|
161
|
+
authorization and schedules its revocation with GitHub; a copy can remain
|
|
162
|
+
usable until GitHub completes the revocation.
|
|
149
163
|
|
|
150
164
|
Connecting or reconnecting GitHub enables **GitHub CLI in devboxes** by default
|
|
151
165
|
under **Integrations → GitHub**. This account-wide preference lets `gh`, coding
|
|
152
166
|
agents, aliases, extensions, and other same-user code request the connected
|
|
153
|
-
identity on current and future Template boxes and devboxes. Before issuing
|
|
154
|
-
boxes.dev
|
|
155
|
-
the current project.
|
|
156
|
-
|
|
167
|
+
identity on current and future Template boxes and devboxes. Before issuing a
|
|
168
|
+
managed credential, boxes.dev checks that one authorization can access every
|
|
169
|
+
known GitHub repository in the current project. It prefers App access and can
|
|
170
|
+
use the user's separately authorized personal access when the App does not
|
|
171
|
+
provide the required repository access. If neither authorization passes those
|
|
172
|
+
checks, boxes.dev returns no managed token and leaves `gh` in ordinary
|
|
173
|
+
machine-local mode for that project.
|
|
157
174
|
|
|
158
175
|
boxes.dev does not write the managed credential to native `gh` configuration
|
|
159
176
|
or a managed credential file, but it can exist in the local service, `gh`,
|
|
@@ -202,11 +219,11 @@ interact with local services inside either machine.
|
|
|
202
219
|
|
|
203
220
|
A Team Template member project has no personal Template box. Team admins author
|
|
204
221
|
its shared saved files in separate Team Template editing machines, and members
|
|
205
|
-
cannot access those machines through their projects.
|
|
206
|
-
|
|
207
|
-
|
|
208
|
-
|
|
209
|
-
prepared pool.
|
|
222
|
+
cannot access those machines through their projects. Prepared devboxes belong
|
|
223
|
+
to one member and project. The team-authored startup script runs immediately
|
|
224
|
+
before the member's startup script, with the same prepared member credentials
|
|
225
|
+
and files available to both. Team admins are trusted authors of that code.
|
|
226
|
+
Once assigned to a draft, the devbox never returns to a prepared pool.
|
|
210
227
|
|
|
211
228
|
Anything available inside the selected machine can usually be read or changed by
|
|
212
229
|
the agent running there. This includes checked-out code, local env files, local
|
|
@@ -11,7 +11,8 @@ parts.
|
|
|
11
11
|
|
|
12
12
|
You need:
|
|
13
13
|
|
|
14
|
-
- a boxes.dev
|
|
14
|
+
- a boxes.dev project with a usable Template box snapshot or saved Team Template
|
|
15
|
+
version;
|
|
15
16
|
- team admin access in boxes.dev to connect the Slack workspace;
|
|
16
17
|
- your own Slack identity linked to your boxes.dev user;
|
|
17
18
|
- permission in Slack to install apps, or a Slack admin who can approve the
|
|
@@ -130,14 +131,15 @@ To start a thread in a teammate's workspace:
|
|
|
130
131
|
The teammate mention must immediately follow `@boxes.dev`, and a request must
|
|
131
132
|
follow the teammate mention. The teammate must have allowed you through their
|
|
132
133
|
default Slack receiver's access setting. The new agent thread belongs to that
|
|
133
|
-
teammate and uses their automation,
|
|
134
|
+
teammate and uses their automation, saved project environment, devbox, credentials, and
|
|
134
135
|
usage. It does not copy either teammate's existing devbox filesystem.
|
|
135
136
|
|
|
136
137
|
boxes.dev starts each automation run on a fresh devbox from the latest
|
|
137
|
-
Template box snapshot
|
|
138
|
-
|
|
139
|
-
|
|
140
|
-
|
|
138
|
+
Template box snapshot for an ordinary project, or the current saved Team
|
|
139
|
+
Template version for a member project. The agent sees the automation prompt
|
|
140
|
+
plus Slack context, including the triggering message and available Slack
|
|
141
|
+
thread messages. If Slack context is incomplete, boxes.dev can start with
|
|
142
|
+
partial context instead of waiting forever.
|
|
141
143
|
|
|
142
144
|
Separate Slack threads or DMs can start separate automation runs at the same
|
|
143
145
|
time, subject to awake devbox capacity. If Slack retries the same event,
|
|
@@ -72,6 +72,9 @@ Tailscale integration page. boxes.dev uses the team connection to confirm that:
|
|
|
72
72
|
- Tailscale policy gives that user, directly or through a group, effective
|
|
73
73
|
access to the configured tag.
|
|
74
74
|
|
|
75
|
+
After verification succeeds, choose **Enable Tailscale** to enable the project.
|
|
76
|
+
Verification alone does not enable the integration.
|
|
77
|
+
|
|
75
78
|
This verification uses Tailscale's policy engine, so direct users, groups,
|
|
76
79
|
SCIM-synced groups, wildcards, and autogroups continue to be managed in
|
|
77
80
|
Tailscale. GitHub-only and passkey-only Tailscale login names are not supported
|
|
@@ -129,29 +129,27 @@ script row states its timing, the directory it runs in, and the template's
|
|
|
129
129
|
repository paths, and each script is edited in place with **Add script** or
|
|
130
130
|
**Edit script**, then **Save script** or **Cancel**.
|
|
131
131
|
|
|
132
|
-
|
|
133
|
-
version contains exactly one repository
|
|
134
|
-
|
|
135
|
-
|
|
132
|
+
For managed projects, both startup scripts run inside the repository when the
|
|
133
|
+
saved version contains exactly one repository. With zero or multiple
|
|
134
|
+
repositories, they run in the project root, normally `/home/boxes`.
|
|
135
|
+
Teardown scripts continue to run in the project root.
|
|
136
136
|
|
|
137
137
|
For a managed template the startup sequence is:
|
|
138
138
|
|
|
139
|
-
1. Start from the saved template.
|
|
140
|
-
2.
|
|
141
|
-
|
|
142
|
-
|
|
143
|
-
|
|
144
|
-
|
|
145
|
-
|
|
146
|
-
|
|
147
|
-
|
|
148
|
-
5. **Member startup script** (default for new projects). It runs once per new
|
|
149
|
-
devbox, before the first agent turn, with the member's configured GitHub
|
|
150
|
-
access and files ready. It is copied into each new project, and members
|
|
151
|
-
edit their own copy afterward; saving the default does not change existing
|
|
152
|
-
projects. A failure shows a warning and the devbox still starts.
|
|
139
|
+
1. Start from the saved template and prepare the member's durable environment.
|
|
140
|
+
2. The prepared devbox may wait until that member needs it.
|
|
141
|
+
3. boxes.dev checks the member's configured connections and files.
|
|
142
|
+
4. **Team startup script** (optional, team-owned). It runs with the same member
|
|
143
|
+
environment as the member startup script, immediately before it. Saving
|
|
144
|
+
applies to future devboxes for every managed project using the template.
|
|
145
|
+
5. **Member startup script** (default for new projects). It is copied into each
|
|
146
|
+
new project, and members edit their own copy afterward; saving the default
|
|
147
|
+
does not change existing projects.
|
|
153
148
|
6. The first agent turn starts.
|
|
154
149
|
|
|
150
|
+
A script error or timeout shows a warning. The next script and agent still
|
|
151
|
+
start, and other members can continue creating devboxes.
|
|
152
|
+
|
|
155
153
|
An independent template shows the same sequence without the team stages,
|
|
156
154
|
starting from the project's own Template box. Another thread on an existing
|
|
157
155
|
devbox, or waking one, does not run the sequence again.
|
|
@@ -162,14 +160,13 @@ Each devbox runs the team teardown captured when it was prepared; saving that
|
|
|
162
160
|
script applies to later preparations. Unused or failed preparations may skip
|
|
163
161
|
the member teardown script.
|
|
164
162
|
|
|
165
|
-
|
|
166
|
-
|
|
167
|
-
|
|
168
|
-
|
|
169
|
-
|
|
163
|
+
Team startup failures appear on the affected member's devbox, with details
|
|
164
|
+
collapsed until opened. Admins can choose **Review startup script**; other
|
|
165
|
+
members can contact their team admin. Saving a correction applies to future
|
|
166
|
+
devboxes and does not rerun startup on the current one.
|
|
167
|
+
|
|
168
|
+
Team teardown failures remain available on the template page. Saving a script
|
|
170
169
|
records it; it does not run it or publish a new saved version.
|
|
171
|
-
When a later run of the same saved team script succeeds, its earlier failure
|
|
172
|
-
disappears from the page.
|
|
173
170
|
|
|
174
171
|
## Environment And Member Files
|
|
175
172
|
|
|
@@ -306,7 +303,7 @@ When editing is finished, choose one of these actions:
|
|
|
306
303
|
are saved before teardown. The confirmation requires typing `DISCARD`.
|
|
307
304
|
|
|
308
305
|
Members can continue creating projects from the current saved version while an
|
|
309
|
-
admin edits a future version. Admins can choose **
|
|
306
|
+
admin edits a future version. Admins can choose **Restore this version** for an
|
|
310
307
|
older ready version under **Previous versions**. boxes.dev prepares that saved
|
|
311
308
|
environment in the background and keeps the current version active until the
|
|
312
309
|
older one is ready; the page shows preparation progress or a retryable failure.
|
|
@@ -362,21 +359,13 @@ the only startup status. Once the thread is running, only failed per-devbox
|
|
|
362
359
|
setup such as Tailscale appears above the composer; setup that is still applying
|
|
363
360
|
stays in the background without an extra checklist.
|
|
364
361
|
|
|
365
|
-
If the
|
|
366
|
-
|
|
367
|
-
|
|
368
|
-
|
|
369
|
-
|
|
370
|
-
|
|
371
|
-
|
|
372
|
-
After repeated startup failures, **Devbox creation is paused** will explain
|
|
373
|
-
why new devboxes cannot start. A team admin can use **Review startup script**
|
|
374
|
-
to open the **Team preparation script** under **When a new devbox is created**,
|
|
375
|
-
review it, and use **Retry saved script**.
|
|
376
|
-
Your draft and attachments will remain available while the team resolves it.
|
|
377
|
-
|
|
378
|
-
If boxes.dev cannot prepare the saved template or finish setup after the startup
|
|
379
|
-
script succeeds, the notice will explain which part failed. Open **View details**
|
|
362
|
+
If the team startup script fails or times out, the devbox still starts. Its
|
|
363
|
+
warning identifies the team script and lets you open or copy its details.
|
|
364
|
+
Admins can choose **Review startup script**; other members should contact
|
|
365
|
+
their team admin. A member startup failure has its own result, so both remain
|
|
366
|
+
inspectable if both scripts fail.
|
|
367
|
+
|
|
368
|
+
If boxes.dev cannot prepare the saved template or finish setup, the notice will explain which part failed. Open **View details**
|
|
380
369
|
and use **Copy details** to share the diagnostic with your team admin or boxes.dev
|
|
381
370
|
support. These setup errors do not necessarily mean the startup script needs to
|
|
382
371
|
change. If waiting for preparation times out, the notice will say that completion
|
|
@@ -221,13 +221,15 @@ and the destination devbox enrolls with its own identity.
|
|
|
221
221
|
|
|
222
222
|
Open **Integrations → MCPs** in the desktop app to manage remote MCP servers in
|
|
223
223
|
one list. Choose **Add MCP**, then paste either the server URL or the Codex or
|
|
224
|
-
Claude setup command supplied by the provider
|
|
224
|
+
Claude setup command supplied by the provider, and choose **Continue**.
|
|
225
|
+
boxes.dev detects the supported
|
|
225
226
|
remote transport and the authentication method, so the form asks only for the
|
|
226
227
|
name, the scope, and which agents to add the connection to. The URL, the
|
|
227
228
|
authentication mode, and the name the agents use sit under **Advanced**, which
|
|
228
229
|
opens on its own when a header or API key still has to be typed in. New
|
|
229
230
|
connections default to **This project**; choose **All projects** only when the
|
|
230
|
-
same server and account should be available everywhere.
|
|
231
|
+
same server and account should be available everywhere. Choose the agents under
|
|
232
|
+
**Add to**, then choose **Add MCP** to save and authorize the connection.
|
|
231
233
|
|
|
232
234
|
Codex and Claude are enabled independently from the same connection row. OAuth
|
|
233
235
|
opens a local browser sign-in for the selected agent, so enabling both agents
|
|
@@ -423,8 +425,10 @@ boxes.dev applies the new sign-in to every devbox and the notice clears on its
|
|
|
423
425
|
own. For an MCP installed directly on the Template box, reauthorize it under
|
|
424
426
|
**Template-managed MCPs**, then take a snapshot so new devboxes will have it;
|
|
425
427
|
existing devboxes keep running without that MCP. In a Team Template member
|
|
426
|
-
project, a Template admin
|
|
427
|
-
|
|
428
|
+
project, a Template admin repairs a machine-local MCP inherited in the saved
|
|
429
|
+
environment. Centrally managed definitions copied from Team Template defaults
|
|
430
|
+
still use the member's own per-agent sign-in and **Reauthorize** action.
|
|
431
|
+
Dismissing the notice hides that MCP server's warning for every
|
|
428
432
|
devbox in the project, including after reloads. The warning will return if the
|
|
429
433
|
server starts successfully and its authorization expires again. boxes.dev does
|
|
430
434
|
not show raw MCP startup errors in the thread.
|
|
@@ -460,7 +464,8 @@ When the agent is working, the composer may stay available for follow-ups. Some
|
|
|
460
464
|
follow-ups are queued and delivered after the current turn. They stay in the
|
|
461
465
|
same user-bubble queue used during startup and reconnect. Queued follow-ups can
|
|
462
466
|
be edited, deleted, or restored. During an active Codex turn, `Steer now`
|
|
463
|
-
|
|
467
|
+
interrupts the current turn and starts the oldest queued follow-up. Remaining
|
|
468
|
+
messages stay queued in order.
|
|
464
469
|
|
|
465
470
|
For Claude, choose **Queue** to wait for the current work to finish or **Steer**
|
|
466
471
|
to send a correction without interrupting a running tool. Claude will use a
|
|
@@ -484,10 +489,17 @@ handing them to the runtime, so delivery after server receipt does not depend
|
|
|
484
489
|
on keeping the app open.
|
|
485
490
|
Keep the app open until any attachment uploads finish and the message reaches
|
|
486
491
|
the server; messages saved only on your device will resume when you reopen
|
|
487
|
-
their thread.
|
|
488
|
-
|
|
489
|
-
|
|
490
|
-
|
|
492
|
+
their thread. Temporary delivery failures before agent submission retry the
|
|
493
|
+
same message while later messages wait. After three failed attempts, the first
|
|
494
|
+
message shows **Send failed**, and a **Message send failed** notice above the
|
|
495
|
+
composer offers **Retry** and **Edit message** (or **Edit messages**, when
|
|
496
|
+
several are waiting). **Retry** retries that message in place; waiting for
|
|
497
|
+
startup or reconnection does not consume those attempts.
|
|
498
|
+
Use **Edit message** or **Edit messages** to cancel pending delivery, including
|
|
499
|
+
while attachments upload. The captured messages return in order as one draft,
|
|
500
|
+
with attachments, before existing composer text. Newer submissions stay queued.
|
|
501
|
+
If returning to draft is interrupted or fails, choose **Edit message** or
|
|
502
|
+
**Edit messages** again to resume it.
|
|
491
503
|
If you quit before an upload finishes, you may need to attach the files again;
|
|
492
504
|
boxes.dev will name any attachments it couldn't restore.
|
|
493
505
|
|
|
@@ -781,12 +793,17 @@ Interrupting asks the agent to stop the current turn. It does not delete the
|
|
|
781
793
|
thread. After a turn stops, the user can send another prompt, inspect changes,
|
|
782
794
|
or decide whether to keep or discard the devbox.
|
|
783
795
|
|
|
784
|
-
|
|
785
|
-
|
|
786
|
-
|
|
787
|
-
|
|
788
|
-
|
|
789
|
-
|
|
796
|
+
On desktop and mobile, **Stop** interrupts the active response and preserves
|
|
797
|
+
queued follow-ups for both Codex and Claude. This includes messages boxes.dev
|
|
798
|
+
is still preparing or retrying: they stay scheduled and run in order when the
|
|
799
|
+
agent is ready. **Steer now** brings queued work forward by interrupting the
|
|
800
|
+
response; preparation and uploads still have to finish.
|
|
801
|
+
|
|
802
|
+
**Edit message** or **Edit messages** explicitly cancels messages still waiting
|
|
803
|
+
for delivery and restores their text and attachments as one ordered draft.
|
|
804
|
+
Messages sent after choosing that action stay scheduled. Messages already
|
|
805
|
+
accepted into the agent's queue use its existing edit/delete controls. Startup
|
|
806
|
+
cancellation, before an active response exists, still cancels the pending start.
|
|
790
807
|
|
|
791
808
|
Claude steers already accepted by Claude are different: Stop may leave them
|
|
792
809
|
waiting for Claude's next response, and they cannot be taken back through the
|
|
@@ -22,7 +22,8 @@ the existing setup state.
|
|
|
22
22
|
|
|
23
23
|
## Desktop App Looks Stale Or Stuck
|
|
24
24
|
|
|
25
|
-
The desktop app's
|
|
25
|
+
The desktop app's **Help and feedback** button beside the account menu at the
|
|
26
|
+
bottom of the sidebar lists the most
|
|
26
27
|
common quick fixes; the steps below match what it shows.
|
|
27
28
|
|
|
28
29
|
If thread content or another desktop view looks stale, stuck, or slightly
|
|
@@ -71,10 +72,13 @@ If remote setup pauses at a recoverable step, the setup UI can offer **Retry
|
|
|
71
72
|
setup**. Use that when the issue looks temporary or the UI says the step is
|
|
72
73
|
retryable.
|
|
73
74
|
|
|
74
|
-
|
|
75
|
-
|
|
76
|
-
|
|
77
|
-
|
|
75
|
+
For a local-folder setup's remote Git access failure, choose **Fix Git access**.
|
|
76
|
+
boxes.dev removes the incomplete Template box and returns to Finalize Bundle,
|
|
77
|
+
keeping the approved review and other bundle choices. Restore the named GitHub
|
|
78
|
+
account's repository access, switch to and verify SSH, or skip Git access before
|
|
79
|
+
continuing. For SSH, register the displayed public key with the Git host and
|
|
80
|
+
verify it. Use **Rebuild bundle** when setup specifically asks to prepare the
|
|
81
|
+
upload again; deleting the project is not required for Git repair.
|
|
78
82
|
|
|
79
83
|
If Create from GitHub's automatic access cannot clone a selected repository,
|
|
80
84
|
follow the specific recovery shown: reconnect the GitHub account used for the
|
|
@@ -102,12 +106,14 @@ GitHub account or grant the boxes.dev App access to every named repository, and
|
|
|
102
106
|
then retry. boxes.dev does not switch to an older Team Template saved version
|
|
103
107
|
or to SSH for this project type.
|
|
104
108
|
|
|
105
|
-
|
|
106
|
-
|
|
107
|
-
|
|
108
|
-
|
|
109
|
-
|
|
110
|
-
|
|
109
|
+
Team startup scripts run after Send, once the member's files and credentials
|
|
110
|
+
are ready. A script failure or timeout shows a warning; the member's own
|
|
111
|
+
startup script and agent turn continue. Open **View details** and use **Copy
|
|
112
|
+
details** to share the failure with a team admin. An admin can choose **Review
|
|
113
|
+
startup script** and correct it under **When a new devbox is created**.
|
|
114
|
+
Corrections apply to future devboxes; saving does not rerun the script on the
|
|
115
|
+
current machine. A startup-script warning does not pause devbox creation or
|
|
116
|
+
block other members.
|
|
111
117
|
|
|
112
118
|
Optional setup such as an MCP connection can warn without blocking the first
|
|
113
119
|
thread. Follow the warning's own sign-in or retry action. GitHub access needed
|
|
@@ -146,6 +152,12 @@ directly there are under **Template-managed MCPs** in the same place. Team
|
|
|
146
152
|
Template member projects omit that inventory. If sign-in fails, follow the
|
|
147
153
|
recovery message on that MCP's card.
|
|
148
154
|
|
|
155
|
+
When you send to an existing Claude thread in the desktop app, a slow MCP
|
|
156
|
+
reconnection can delay the message while Claude gets ready. boxes.dev will
|
|
157
|
+
keep the message queued and continue automatically when preparation finishes,
|
|
158
|
+
even if it takes longer than a minute. You don't need to send it again. If
|
|
159
|
+
sign-in or another error needs attention, follow the message's recovery action.
|
|
160
|
+
|
|
149
161
|
If **Template-managed MCPs** cannot load, use **Retry**. A dash in an agent's
|
|
150
162
|
count means its inventory is unavailable, and rows kept from an earlier read
|
|
151
163
|
are marked as previous results. A sleeping Template box shows a disconnected
|
|
@@ -246,7 +258,7 @@ If the ports menu says it is waiting for the selected runtime or waiting for an
|
|
|
246
258
|
initial port snapshot, give the runtime a moment to report running services.
|
|
247
259
|
|
|
248
260
|
If a visible port is not forwarded because the local port is already in use,
|
|
249
|
-
use **Use next available
|
|
261
|
+
use **Use next available** when offered, or stop the local process that is
|
|
250
262
|
holding the port.
|
|
251
263
|
|
|
252
264
|
If there are no forwarded ports, make sure the app or service is actually
|
|
@@ -309,18 +321,19 @@ commands become available.
|
|
|
309
321
|
When the setting is on and the current project's repository access is ready,
|
|
310
322
|
do not repair authentication by running `gh auth login`, `gh auth logout`, `gh
|
|
311
323
|
auth refresh`, or `gh auth switch`; manage that identity from boxes.dev. When
|
|
312
|
-
the setting is off, GitHub is not connected to boxes.dev, or the App
|
|
313
|
-
access
|
|
314
|
-
configuration and environment instead. In the
|
|
315
|
-
to run `gh auth login` on that machine.
|
|
316
|
-
automatic Git fetch, pull, or push for a
|
|
317
|
-
method.
|
|
324
|
+
the setting is off, GitHub is not connected to boxes.dev, or neither the App nor
|
|
325
|
+
authorized personal access can reach every known repository in this project,
|
|
326
|
+
`gh` uses its ordinary local configuration and environment instead. In the
|
|
327
|
+
missing-access case, it is safe to run `gh auth login` on that machine.
|
|
328
|
+
Disabling GitHub CLI does not disable automatic Git fetch, pull, or push for a
|
|
329
|
+
project that uses that separate access method.
|
|
318
330
|
|
|
319
331
|
If a repository or API request is still rejected while `gh` is enabled, use
|
|
320
|
-
**Manage repository access** to
|
|
321
|
-
|
|
322
|
-
|
|
323
|
-
|
|
332
|
+
**Manage repository access** to check App access, and reconnect GitHub if the
|
|
333
|
+
page requests it. If your organization cannot approve the App, choose **Use
|
|
334
|
+
personal access** and authorize the official GitHub CLI. boxes.dev can manage
|
|
335
|
+
the CLI identity only when either the App or personal authorization can access
|
|
336
|
+
every known repository in the project.
|
|
324
337
|
|
|
325
338
|
## Billing Or Limit Blocks
|
|
326
339
|
|
|
@@ -404,7 +417,7 @@ triggers depend on a healthy workspace connection and linked user identity.
|
|
|
404
417
|
|
|
405
418
|
## When To Contact Support
|
|
406
419
|
|
|
407
|
-
Contact
|
|
420
|
+
Contact hi@boxes.dev when:
|
|
408
421
|
|
|
409
422
|
- Setup repeatedly fails after retrying upload/setup or starting over.
|
|
410
423
|
- A Template box or devbox cannot wake and no billing or capacity fix is
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@boxes-dev/dvb-runtime",
|
|
3
|
-
"version": "1.0.
|
|
3
|
+
"version": "1.0.1016",
|
|
4
4
|
"type": "module",
|
|
5
5
|
"license": "UNLICENSED",
|
|
6
6
|
"imports": {
|
|
@@ -77,5 +77,5 @@
|
|
|
77
77
|
"e2b": "^2.18.0",
|
|
78
78
|
"ink-testing-library": "^4.0.0"
|
|
79
79
|
},
|
|
80
|
-
"devboxReleasedAt": "2026-09-
|
|
80
|
+
"devboxReleasedAt": "2026-09-22T19:51:31Z"
|
|
81
81
|
}
|