@boxes-dev/dvb-runtime 1.0.1062 → 1.0.1064
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/git-signing.md +7 -0
- package/dist/bin/dvb.mjs +241 -103
- package/dist/bin/dvbd.mjs +4 -4
- package/dist/product-docs/SKILL.md +8 -3
- package/dist/product-docs/references/agent-tools.md +3 -0
- package/dist/product-docs/references/cli.md +6 -6
- package/dist/product-docs/references/core-concepts.md +5 -3
- package/dist/product-docs/references/desktop-workbench.md +6 -0
- package/dist/product-docs/references/files-git-and-review.md +54 -20
- package/dist/product-docs/references/mobile.md +11 -1
- package/dist/product-docs/references/onbox-agent-tools.md +173 -22
- package/dist/product-docs/references/project-setup.md +87 -44
- package/dist/product-docs/references/security-and-data.md +14 -13
- package/dist/product-docs/references/template-box-environment.md +15 -9
- package/dist/product-docs/references/threads-and-agents.md +36 -12
- package/dist/product-docs/references/troubleshooting.md +11 -11
- package/package.json +2 -2
|
@@ -37,7 +37,9 @@ Signing in on the website before any project exists lands on **Get started**,
|
|
|
37
37
|
which has three steps:
|
|
38
38
|
|
|
39
39
|
1. **Connect GitHub**, which is optional and shows as done once GitHub is
|
|
40
|
-
connected.
|
|
40
|
+
connected. The completed step offers optional personal GitHub CLI access
|
|
41
|
+
for commands that need the user's own permissions. It can be skipped and
|
|
42
|
+
connected later in Integrations or with `gh auth login`.
|
|
41
43
|
2. **Set up your project with your coding agent**: a ready-made prompt to
|
|
42
44
|
paste into Codex or Claude Code in the project folder, which has the agent
|
|
43
45
|
run the agent-driven terminal setup. The prompt includes a login code that
|
|
@@ -76,7 +78,11 @@ The desktop local-folder setup wizard usually moves through these stages:
|
|
|
76
78
|
|
|
77
79
|
1. Account: sign in to boxes.dev, then optionally connect GitHub and Slack on
|
|
78
80
|
**Connect your accounts**. GitHub here is sign-in only; boxes.dev asks for
|
|
79
|
-
repository access later, once it knows the project's repositories.
|
|
81
|
+
repository access later, once it knows the project's repositories. After
|
|
82
|
+
connecting, choose optional personal authorization for CLI commands beyond
|
|
83
|
+
the App's permissions, including starting workflows; it never blocks setup.
|
|
84
|
+
The same follow-up appears in Account, GitHub project setup, local Git access
|
|
85
|
+
setup, and Team Template repository selection. Team
|
|
80
86
|
admins on a team without a Slack workspace see **Connect Slack** to install
|
|
81
87
|
it, anyone on a team with a workspace can link their Slack account, and
|
|
82
88
|
other members see no Slack row. Neither connection is required to continue.
|
|
@@ -224,37 +230,60 @@ followed by a Team Template when the team has one. The local-folder and GitHub
|
|
|
224
230
|
options are fallbacks under **Other setup options** at the bottom of the step,
|
|
225
231
|
with the local folder first. The prompt and **Copy prompt** are visible
|
|
226
232
|
immediately. Paste the prompt into Codex or Claude Code in the local project
|
|
227
|
-
folder.
|
|
228
|
-
when the CLI connects and
|
|
229
|
-
|
|
230
|
-
|
|
231
|
-
|
|
232
|
-
|
|
233
|
+
folder. Until the agent reaches the project, the card shows its progress, such
|
|
234
|
+
as when the CLI connects and when the user needs to connect accounts. Once the
|
|
235
|
+
CLI connects, the prompt moves behind **Setup prompt** below the progress.
|
|
236
|
+
|
|
237
|
+
When the agent first reports from the project, the Project step opens that
|
|
238
|
+
project's setup page. The page lists five stages: planning the setup with the
|
|
239
|
+
coding agent, uploading the project files (with a percentage), creating the
|
|
240
|
+
Template box, unpacking the files on the Template box, and starting setup on
|
|
241
|
+
the Template box. While the agent plans, the page shows when it prepares the
|
|
242
|
+
project, when the user needs to act, when the agent is fixing issues a check
|
|
243
|
+
found, when a setup command fails, and when the setup plan is ready for
|
|
244
|
+
approval. **Back** returns to the setup choices, and the page won't open on
|
|
245
|
+
its own again for that project. In **New project**, the page only opens on its
|
|
246
|
+
own for a setup started after the wizard opened.
|
|
247
|
+
|
|
248
|
+
Setups that a coding agent is running also appear under **Setups in
|
|
249
|
+
progress** on the Project step and in the titlebar project selector, with
|
|
250
|
+
their current status, such as **Plan ready for review** or **Waiting for
|
|
251
|
+
you**. Choose **View setup**, or the setup's entry in the project selector, to
|
|
252
|
+
open its setup page. Choosing a project folder that a coding agent is setting
|
|
253
|
+
up also opens its setup page, because continuing in the desktop wizard would
|
|
254
|
+
take over the agent's work. A setup stays listed until it finishes or is
|
|
255
|
+
deleted; before the upload starts, it also leaves the list if the agent hasn't
|
|
256
|
+
reported on it for a day.
|
|
257
|
+
|
|
258
|
+
The setup page for such a project says that setup is waiting for the coding
|
|
259
|
+
agent and suggests asking it to run `dvb agent-init status` and follow its
|
|
260
|
+
next step. The page updates when the agent runs its next setup command, such
|
|
261
|
+
as `dvb agent-init check`; `status` alone doesn't bring it back. When the user
|
|
262
|
+
reaches this page by choosing the project folder, it also offers **Delete
|
|
263
|
+
setup**, which deletes the setup progress saved on the computer. The agent's
|
|
264
|
+
manifest and the project folder are not affected. Choosing the folder again
|
|
265
|
+
then starts the desktop wizard, and a later setup command from the agent,
|
|
266
|
+
such as `dvb agent-init check`, makes the project the agent's setup again.
|
|
233
267
|
|
|
234
268
|
The folder wizard's steps and **Continue** appear only after a local folder
|
|
235
269
|
is selected. **Other setup options** remembers whether it was open across
|
|
236
|
-
reloads in the same app session.
|
|
237
|
-
the
|
|
238
|
-
|
|
239
|
-
|
|
240
|
-
|
|
241
|
-
|
|
242
|
-
|
|
243
|
-
|
|
244
|
-
follows a setup started while the wizard is open. The Project step does not
|
|
245
|
-
need to stay open for setup to continue.
|
|
246
|
-
|
|
247
|
-
If an agent-driven setup stops before its setup thread starts, the Project
|
|
248
|
-
step shows the error and asks the user to have their coding agent run
|
|
270
|
+
reloads in the same app session. When the setup thread starts on the Template
|
|
271
|
+
box, the desktop app opens it in the workbench. The workbench banner then
|
|
272
|
+
shows **Setup in progress** and **Finishing setup** until setup completes,
|
|
273
|
+
and new devboxes are unavailable until then. The setup page does not need to
|
|
274
|
+
stay open for setup to continue.
|
|
275
|
+
|
|
276
|
+
If an agent-driven setup stops before its setup thread starts, its setup page
|
|
277
|
+
shows the error and asks the user to have their coding agent run
|
|
249
278
|
`dvb agent-init retry` in the project folder. **Delete setup**, shown on the
|
|
250
|
-
|
|
251
|
-
was created, and the setup state saved on the computer,
|
|
252
|
-
manifest; the project folder is not affected. If setup
|
|
279
|
+
page once the upload starts, whether setup is running or stopped, deletes the
|
|
280
|
+
Template box, if one was created, and the setup state saved on the computer,
|
|
281
|
+
including the manifest; the project folder is not affected. If setup
|
|
253
282
|
stops after the thread starts, the workbench banner shows the error and the
|
|
254
283
|
same retry command. A failure while bundling, before the upload starts,
|
|
255
284
|
appears only in the agent's `dvb agent-init` output. The agent's command
|
|
256
285
|
needs to be running when the Template box asks for the bundle's decrypt key;
|
|
257
|
-
if the Template box has waited more than a minute, the
|
|
286
|
+
if the Template box has waited more than a minute, the setup page says setup
|
|
258
287
|
is waiting for the coding agent and asks the user to have it run `dvb
|
|
259
288
|
agent-init watch` in the project folder.
|
|
260
289
|
|
|
@@ -363,20 +392,34 @@ or **Settings → Agent accounts** in the mobile app to add another account or A
|
|
|
363
392
|
key, choose the active credential, edit an API
|
|
364
393
|
key, re-auth, remove a saved credential, or disconnect an agent. The active
|
|
365
394
|
Codex and Claude choices are independent and apply globally across the user's
|
|
366
|
-
devboxes. On macOS, Configure agents is in the boxes.dev app menu.
|
|
395
|
+
devboxes. On macOS, Configure agents is in the boxes.dev app menu. Saving a new
|
|
396
|
+
API key does not replace a working subscription that is already selected; the
|
|
397
|
+
user selects the key to switch to it.
|
|
398
|
+
|
|
399
|
+
Each saved subscription row in desktop Configure agents shows a small bar for
|
|
400
|
+
the weekly limit's remaining usage. A 5-hour bar appears below it only when
|
|
401
|
+
that limit is low (below 20% left) or the account has no weekly limit. Hovering
|
|
402
|
+
over the bars shows the same quota details as the thread composer, plus when
|
|
403
|
+
the reading was taken if it is more than 15 minutes old. Opening Configure
|
|
404
|
+
agents asks the providers for fresh readings of saved subscriptions; an
|
|
405
|
+
account whose saved sign-in has expired keeps its last reading until an agent
|
|
406
|
+
uses it again. API key rows show when the key was last used and today's tokens,
|
|
407
|
+
including cached tokens, from agent threads on boxes.dev.
|
|
367
408
|
|
|
368
409
|
With multiple subscriptions saved for an agent, desktop Configure agents offers
|
|
369
410
|
**Automatically rotate subscriptions when usage depleted**. Selecting a
|
|
370
411
|
subscription radio chooses the **Default** account while automatic selection
|
|
371
|
-
is enabled; **
|
|
412
|
+
is enabled; **Default** appears only while an automatic option is on, and
|
|
413
|
+
**Active** marks the account currently in use. boxes.dev prefers
|
|
372
414
|
the default whenever its usage is available, switches to another subscription
|
|
373
415
|
when it is exhausted, and returns after quota resets. A saved API key also
|
|
374
416
|
exposes **Automatically switch to API when all subscriptions are exhausted**,
|
|
375
417
|
which requires a separate opt-in and incurs the API provider's charges. Unknown
|
|
376
418
|
quota and authentication failures alone do not authorize API switching.
|
|
377
|
-
Choosing an API row directly returns that agent to manual selection.
|
|
378
|
-
|
|
379
|
-
|
|
419
|
+
Choosing an API row directly returns that agent to manual selection. Turning
|
|
420
|
+
on either automatic option while an API key is selected moves the agent to a
|
|
421
|
+
subscription unless every subscription is exhausted and API switching is on.
|
|
422
|
+
Codex and Claude settings are independent, global, and affect conversations started from either desktop or mobile. Mobile can
|
|
380
423
|
still select accounts manually; these automatic controls are configured on
|
|
381
424
|
desktop. Account changes retain conversation history; an agent already working
|
|
382
425
|
may finish its current turn first. They do not automatically replay a turn that
|
|
@@ -394,18 +437,18 @@ because OAuth providers authorize those agents separately.
|
|
|
394
437
|
|
|
395
438
|
For supported GitHub repositories, first-run desktop setup offers the GitHub
|
|
396
439
|
CLI choice in **Finalize Bundle → GitHub access**. Connecting or reconnecting
|
|
397
|
-
GitHub turns on **GitHub CLI
|
|
440
|
+
GitHub turns on **GitHub CLI access**, and the checkbox is selected by
|
|
398
441
|
default; clear it before continuing to turn the grant back off. The same
|
|
399
442
|
account-wide choice remains manageable under **Integrations → GitHub → GitHub
|
|
400
443
|
CLI in devboxes** and applies to all current and future Template boxes and
|
|
401
|
-
devboxes.
|
|
402
|
-
|
|
403
|
-
|
|
404
|
-
|
|
405
|
-
|
|
406
|
-
|
|
407
|
-
|
|
408
|
-
|
|
444
|
+
devboxes. Managed `gh` prefers connected personal access. Without it, boxes.dev
|
|
445
|
+
checks App access to every known project repository before supplying the App
|
|
446
|
+
credential. Optional personal sign-in is offered after the GitHub onboarding
|
|
447
|
+
step and in Integrations; `gh auth login` starts the same GitHub approval flow.
|
|
448
|
+
Manage disconnects in Integrations. This does not change repository remotes or
|
|
449
|
+
the project's Git pull/push access method. When the CLI choice is disabled or
|
|
450
|
+
GitHub is not connected, `gh` uses ordinary machine-local configuration and
|
|
451
|
+
native login behavior.
|
|
409
452
|
|
|
410
453
|
boxes.dev stores centrally managed remote MCP definitions and credentials,
|
|
411
454
|
refreshes OAuth when the provider supports it, and applies the current version
|
|
@@ -908,11 +951,11 @@ reopen setup at the step where it left off. The wizard row also offers
|
|
|
908
951
|
**Continue setup** and a delete button; deleting removes only the incomplete
|
|
909
952
|
setup state, and the local folder and its files won't be affected. A setup
|
|
910
953
|
waiting on a recoverable error shows **Needs attention** in the project
|
|
911
|
-
selector. Setups started by a coding agent with `dvb agent-init` are
|
|
912
|
-
|
|
913
|
-
Agent-Driven Setup From The Terminal)
|
|
914
|
-
stops, the user should ask the coding agent to run
|
|
915
|
-
the project folder.
|
|
954
|
+
selector. Setups started by a coding agent with `dvb agent-init` are listed
|
|
955
|
+
with their status instead, and choosing one opens its setup page (see
|
|
956
|
+
Agent-Driven Setup From The Terminal). The desktop app never resumes them
|
|
957
|
+
itself. If one stops, the user should ask the coding agent to run
|
|
958
|
+
`dvb agent-init retry` in the project folder.
|
|
916
959
|
|
|
917
960
|
Common recovery paths:
|
|
918
961
|
|
|
@@ -157,25 +157,26 @@ checks. Team Template editing uses repository-restricted App installation
|
|
|
157
157
|
credentials rather than an administrator's broad user credential.
|
|
158
158
|
|
|
159
159
|
Optional personal access uses the official GitHub CLI authorization the user
|
|
160
|
-
approved.
|
|
161
|
-
|
|
162
|
-
|
|
163
|
-
|
|
164
|
-
|
|
160
|
+
approved. The personal authorization must match the main GitHub identity.
|
|
161
|
+
Git and explicit pull-request operations retain their repository checks;
|
|
162
|
+
managed CLI commands use personal access and let GitHub enforce the user's
|
|
163
|
+
permissions on each request. These checks do not narrow the credential itself:
|
|
164
|
+
code running on the machine can inspect the full token, whose permissions come
|
|
165
|
+
from the GitHub CLI authorization rather than the GitHub App grants. Personal tokens can be
|
|
165
166
|
expiring or non-expiring. **Disconnect personal access** removes the saved
|
|
166
167
|
authorization and schedules its revocation with GitHub; a copy can remain
|
|
167
168
|
usable until GitHub completes the revocation.
|
|
168
169
|
|
|
169
|
-
Connecting or reconnecting GitHub enables **GitHub CLI
|
|
170
|
+
Connecting or reconnecting GitHub enables **GitHub CLI access** by default
|
|
170
171
|
under **Integrations → GitHub**. This account-wide preference lets `gh`, coding
|
|
171
172
|
agents, aliases, extensions, and other same-user code request the connected
|
|
172
|
-
identity on current and future Template boxes and devboxes.
|
|
173
|
-
|
|
174
|
-
|
|
175
|
-
|
|
176
|
-
|
|
177
|
-
|
|
178
|
-
|
|
173
|
+
identity on current and future Template boxes and devboxes. Managed `gh` prefers
|
|
174
|
+
the user's separately approved personal access. Without personal access,
|
|
175
|
+
boxes.dev checks that the App can reach every known project repository before
|
|
176
|
+
issuing its credential. Personal sign-in is optional and available from
|
|
177
|
+
onboarding, **Integrations → GitHub**, or `gh auth login`; it requests the
|
|
178
|
+
official GitHub CLI's broad repository, organization, gist, and workflow scopes.
|
|
179
|
+
Organization authorization and the user's GitHub permissions still apply.
|
|
179
180
|
|
|
180
181
|
boxes.dev does not write the managed credential to native `gh` configuration
|
|
181
182
|
or a managed credential file, but it can exist in the local service, `gh`,
|
|
@@ -58,16 +58,15 @@ for long-running processes and stop only the processes you started.
|
|
|
58
58
|
|
|
59
59
|
GitHub CLI authentication is an explicit user choice in **Finalize Bundle →
|
|
60
60
|
GitHub access** during first-run desktop setup for supported GitHub repositories
|
|
61
|
-
and remains manageable from **Integrations → GitHub → GitHub CLI
|
|
61
|
+
and remains manageable from **Integrations → GitHub → GitHub CLI access**.
|
|
62
62
|
Connecting or reconnecting GitHub turns it on by default; clear the setup
|
|
63
|
-
checkbox or turn off the Integrations setting to disable it. When enabled
|
|
64
|
-
|
|
65
|
-
|
|
66
|
-
|
|
67
|
-
|
|
68
|
-
|
|
69
|
-
|
|
70
|
-
user's ordinary machine-local configuration and environment. Aliases and
|
|
63
|
+
checkbox or turn off the Integrations setting to disable it. When enabled,
|
|
64
|
+
managed `gh` prefers connected personal access. Without personal access,
|
|
65
|
+
boxes.dev checks App access to every known project repository before supplying
|
|
66
|
+
its credential. Run `gh auth login` to connect optional personal access through
|
|
67
|
+
the GitHub approval code; manage disconnects in **Integrations → GitHub**.
|
|
68
|
+
When disabled or GitHub is not connected to boxes.dev, `gh` uses the user's
|
|
69
|
+
ordinary machine-local configuration and native login behavior. Aliases and
|
|
71
70
|
extensions run as ordinary same-user code with the effective managed or local
|
|
72
71
|
identity, so install only ones the user trusts. This CLI grant is separate from
|
|
73
72
|
the project's Git remote and automatic pull/push access.
|
|
@@ -186,6 +185,13 @@ This saves the Template box state used by future Devboxes. Do not snapshot a
|
|
|
186
185
|
partially working setup as though it were complete. If setup cannot be
|
|
187
186
|
completed, report the blocker and the exact remaining requirements instead.
|
|
188
187
|
|
|
188
|
+
Apps that run independently of agent and terminal sessions, such as Docker
|
|
189
|
+
containers and system services, keep running on new devboxes created from the
|
|
190
|
+
snapshot. Processes started from an agent command or a terminal do not
|
|
191
|
+
continue there. If every new devbox needs a service, run it independently of a
|
|
192
|
+
session, for example as a Docker container with a restart policy, or start it
|
|
193
|
+
from the project's startup script.
|
|
194
|
+
|
|
189
195
|
Codex and Claude plugins whose scope is **Template box** are part of that
|
|
190
196
|
machine state. A change is available on the live Template box immediately, but
|
|
191
197
|
future devboxes receive it only after a new snapshot; existing devboxes remain
|
|
@@ -300,10 +300,25 @@ connection without replacing its sign-in; other personal connections remain.
|
|
|
300
300
|
An account-wide source stays available in other projects. See
|
|
301
301
|
`team-template.md` for matching and template-update behavior.
|
|
302
302
|
|
|
303
|
-
A connected service can ask Claude
|
|
304
|
-
|
|
305
|
-
|
|
306
|
-
|
|
303
|
+
A connected service can ask Claude or Codex for information in the thread.
|
|
304
|
+
Review the server name and request, fill in the form, and choose **Submit**.
|
|
305
|
+
Forms support text, numbers, Yes/No answers, and single or multiple choices.
|
|
306
|
+
Choose **Clear** to leave an optional field out. A **No** answer is a value
|
|
307
|
+
you can submit; choose **Decline** to refuse the request or **Cancel** to
|
|
308
|
+
dismiss it. Simple confirmations may still use **Allow** and **Deny**.
|
|
309
|
+
|
|
310
|
+
Your unfinished answers will remain available when you leave and return to
|
|
311
|
+
the thread in the same running app. Restarting the app may restore only the
|
|
312
|
+
request and its defaults. If sending fails, your edits will remain available
|
|
313
|
+
for **Retry**.
|
|
314
|
+
|
|
315
|
+
Codex can also ask you to complete a service request in your browser. Review
|
|
316
|
+
the destination, choose **Open in browser**, and finish the service's flow
|
|
317
|
+
there. Opening the page will send your consent; the agent will continue
|
|
318
|
+
after the service reports completion. Enter passwords and credentials only
|
|
319
|
+
in the service's browser flow. If you cannot finish, stop the agent and ask
|
|
320
|
+
it to try again. Claude browser requests and unsupported forms
|
|
321
|
+
are currently canceled or declined so the agent can continue.
|
|
307
322
|
|
|
308
323
|
## Plugins
|
|
309
324
|
|
|
@@ -551,10 +566,11 @@ answer. Choose an option to advance to the next question or send the answers
|
|
|
551
566
|
on the last question. For a custom answer, type it and select **Continue** or
|
|
552
567
|
**Send**. Your answer will reach the running turn, and any text or attachments
|
|
553
568
|
already in the reply box will stay there. Use **Skip** to
|
|
554
|
-
leave a question unanswered
|
|
555
|
-
|
|
556
|
-
|
|
557
|
-
reopen when you return to the thread
|
|
569
|
+
leave a question unanswered. Once you send or skip the last question, the panel
|
|
570
|
+
closes for the rest of the turn. **Dismiss** minimizes the panel instead;
|
|
571
|
+
select **Answer questions** to reopen it. Historical questions do not
|
|
572
|
+
automatically reopen when you return to the thread; any you have not sent or
|
|
573
|
+
skipped stay under **Answer questions**. An untouched panel minimizes after 30
|
|
558
574
|
seconds without sending anything. If
|
|
559
575
|
the turn ends, edited answers that you have not sent will move to the reply box.
|
|
560
576
|
Answers reach the running turn even if ordinary replies are set to Queue.
|
|
@@ -589,9 +605,15 @@ action.
|
|
|
589
605
|
The Codex rate-limit indicator shows remaining session, weekly, and available
|
|
590
606
|
model-specific quotas with countdowns to their resets. Limits for the selected
|
|
591
607
|
model use warning colors; quotas for other models remain visible in muted
|
|
592
|
-
colors. When the connected ChatGPT account has
|
|
593
|
-
|
|
594
|
-
|
|
608
|
+
colors. When the connected ChatGPT account has credits, the indicator also
|
|
609
|
+
shows the credit balance. Codex keeps working on credits after the ordinary
|
|
610
|
+
session or weekly limit runs out, so that limit shows an amber warning instead
|
|
611
|
+
of the red alert, and the balance is marked in use. When the account has banked
|
|
612
|
+
usage limit resets, the same indicator shows how many are available and when
|
|
613
|
+
the next three expire; that row is omitted when reset inventory is unavailable.
|
|
614
|
+
The indicator's details name the account the limits belong to. When Codex is
|
|
615
|
+
using an API key, the indicator shows a key icon instead, with today's token
|
|
616
|
+
usage for that key when available.
|
|
595
617
|
|
|
596
618
|
Codex transcript activity keeps tool work readable after it finishes. A model
|
|
597
619
|
that reads or searches files and runs several foreground commands can settle
|
|
@@ -757,7 +779,9 @@ session and weekly quota with reset times. That quota is shared across
|
|
|
757
779
|
Template boxes and devboxes using the same Anthropic organization and account.
|
|
758
780
|
If a thread is still connected with credentials from before a re-authentication,
|
|
759
781
|
it continues to show the quota for the account scope that thread is actually
|
|
760
|
-
using.
|
|
782
|
+
using. The quota details name that account. When Claude Code is using an API
|
|
783
|
+
key, the composer shows a key icon instead, with today's token usage for that
|
|
784
|
+
key when available.
|
|
761
785
|
|
|
762
786
|
Claude Code transcripts can be shown in two transcript styles, chosen from the
|
|
763
787
|
thread action menu's Transcript style submenu: CLI style (a terminal-style
|
|
@@ -340,27 +340,27 @@ First confirm that the selected Template box or devbox is awake and ready.
|
|
|
340
340
|
First-run desktop setup may already have connected GitHub while leaving its
|
|
341
341
|
separate CLI checkbox cleared in **Finalize Bundle → GitHub access**. Open
|
|
342
342
|
**Integrations → GitHub**, connect or reconnect the account if needed, and turn
|
|
343
|
-
on **GitHub CLI
|
|
343
|
+
on **GitHub CLI access** when `gh` should use that connected identity. If
|
|
344
344
|
the switch is unavailable, finish the shown GitHub reconnect step first. An
|
|
345
345
|
older machine may need to finish its boxes.dev update before managed `gh`
|
|
346
346
|
commands become available.
|
|
347
347
|
|
|
348
|
-
When the setting is on
|
|
349
|
-
|
|
350
|
-
|
|
351
|
-
the setting is off
|
|
352
|
-
|
|
353
|
-
`gh` uses its ordinary local configuration and environment instead. In the
|
|
354
|
-
missing-access case, it is safe to run `gh auth login` on that machine.
|
|
348
|
+
When the setting is on, run `gh auth login` to connect optional personal access
|
|
349
|
+
through GitHub's approval code. Approve with the account connected to boxes.dev;
|
|
350
|
+
managed `gh` will prefer that personal access. Manage disconnects in
|
|
351
|
+
**Integrations → GitHub**. When the setting is off or GitHub is not connected,
|
|
352
|
+
`gh` uses its ordinary local configuration and native login behavior.
|
|
355
353
|
Disabling GitHub CLI does not disable automatic Git fetch, pull, or push for a
|
|
356
354
|
project that uses that separate access method.
|
|
357
355
|
|
|
358
356
|
If a repository or API request is still rejected while `gh` is enabled, use
|
|
359
357
|
**Manage repository access** to check App access, and reconnect GitHub if the
|
|
360
358
|
page requests it. If your organization cannot approve the App, choose **Use
|
|
361
|
-
personal access** and authorize the official GitHub CLI.
|
|
362
|
-
|
|
363
|
-
|
|
359
|
+
personal access** and authorize the official GitHub CLI. Personal access is
|
|
360
|
+
also available when App repository access works but a command needs broader
|
|
361
|
+
permissions. Without personal access, boxes.dev checks that the App can reach
|
|
362
|
+
every known project repository before issuing its credential. With personal
|
|
363
|
+
access, GitHub enforces the user's permissions on each CLI command.
|
|
364
364
|
|
|
365
365
|
## Billing Or Limit Blocks
|
|
366
366
|
|
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.1064",
|
|
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-
|
|
80
|
+
"devboxReleasedAt": "2026-10-10T22:39:43Z"
|
|
81
81
|
}
|