@boxes-dev/dvb-runtime 1.0.1104 → 1.0.1106
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/app.md +6 -5
- package/dist/agent-init-guides/flow.md +36 -12
- package/dist/agent-init-guides/git-ssh.md +9 -4
- package/dist/agent-init-guides/untracked.md +2 -1
- package/dist/bin/dvb.mjs +1216 -1829
- package/dist/bin/dvbd.mjs +6 -6
- package/dist/product-docs/references/agent-tools.md +32 -5
- package/dist/product-docs/references/cli.md +6 -4
- package/dist/product-docs/references/core-concepts.md +1 -1
- package/dist/product-docs/references/desktop-workbench.md +22 -3
- package/dist/product-docs/references/environment-setup-validation.md +22 -0
- package/dist/product-docs/references/files-git-and-review.md +29 -16
- package/dist/product-docs/references/fork-workflows.md +3 -2
- package/dist/product-docs/references/getting-started.md +2 -1
- package/dist/product-docs/references/index.md +2 -1
- package/dist/product-docs/references/linear.md +15 -0
- package/dist/product-docs/references/mobile.md +6 -1
- package/dist/product-docs/references/onbox-agent-tools.md +221 -61
- package/dist/product-docs/references/ports-terminal-and-runtime.md +5 -3
- package/dist/product-docs/references/project-setup.md +33 -17
- package/dist/product-docs/references/security-and-data.md +3 -2
- package/dist/product-docs/references/threads-and-agents.md +17 -4
- package/dist/product-docs/references/troubleshooting.md +7 -5
- package/dist/prompts/local-services-scan.md +3 -4
- package/package.json +2 -2
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]="
|
|
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]="e0a9c17c-a865-5681-a514-632ec7b02f34")}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";
|
|
@@ -64675,9 +64675,9 @@ var init_sentry = __esm({
|
|
|
64675
64675
|
uncaughtExceptionMonitorInstalled = false;
|
|
64676
64676
|
currentDevboxSentryUser = null;
|
|
64677
64677
|
readBuildMetadata = () => {
|
|
64678
|
-
const rawPackageVersion = "1.0.
|
|
64679
|
-
const rawGitSha = "
|
|
64680
|
-
const rawSentryRelease = "boxes-dev-dvb@1.0.
|
|
64678
|
+
const rawPackageVersion = "1.0.1106";
|
|
64679
|
+
const rawGitSha = "d61081369787f2b8d0e2f0c06f53bbf1aba2bb8b";
|
|
64680
|
+
const rawSentryRelease = "boxes-dev-dvb@1.0.1106+d61081369787f2b8d0e2f0c06f53bbf1aba2bb8b";
|
|
64681
64681
|
const packageVersion = typeof rawPackageVersion === "string" ? rawPackageVersion : void 0;
|
|
64682
64682
|
const gitSha = typeof rawGitSha === "string" ? rawGitSha : void 0;
|
|
64683
64683
|
const sentryRelease = typeof rawSentryRelease === "string" ? rawSentryRelease : void 0;
|
|
@@ -67199,7 +67199,7 @@ var init_packageVersion = __esm({
|
|
|
67199
67199
|
return path8.join(process.cwd(), "dvb");
|
|
67200
67200
|
};
|
|
67201
67201
|
readEmbeddedPackageVersion = () => {
|
|
67202
|
-
const raw = "1.0.
|
|
67202
|
+
const raw = "1.0.1106";
|
|
67203
67203
|
return trimVersion(raw);
|
|
67204
67204
|
};
|
|
67205
67205
|
readNearestPackageMetadata = (basePath) => {
|
|
@@ -80404,4 +80404,4 @@ smol-toml/dist/index.js:
|
|
|
80404
80404
|
*)
|
|
80405
80405
|
*/
|
|
80406
80406
|
|
|
80407
|
-
//# debugId=
|
|
80407
|
+
//# debugId=e0a9c17c-a865-5681-a514-632ec7b02f34
|
|
@@ -349,9 +349,12 @@ archive changes shared metadata without waking it.
|
|
|
349
349
|
|
|
350
350
|
On a shared devbox, keep its anchor thread and archive the secondary task
|
|
351
351
|
threads. The first thread started on a previously threadless devbox becomes
|
|
352
|
-
its anchor and cannot be archived separately.
|
|
353
|
-
|
|
354
|
-
|
|
352
|
+
its anchor and cannot be archived separately. When the devbox is no longer
|
|
353
|
+
needed, archive all of its threads and destroy it together, as described in
|
|
354
|
+
[Lifecycle Mutations And Cleanup](#lifecycle-mutations-and-cleanup). These
|
|
355
|
+
commands also support threads on the Template box. Restore cold threads in the
|
|
356
|
+
desktop or mobile app before unarchiving them; history-only threads cannot be
|
|
357
|
+
restored.
|
|
355
358
|
|
|
356
359
|
For a script that cleans up successful tasks, retain each task's result and
|
|
357
360
|
check `threads wait`'s `data.status` for `completed` before archiving. A
|
|
@@ -369,8 +372,32 @@ dvb devboxes wake --project <project-fingerprint> --target <instance-id> --json
|
|
|
369
372
|
dvb devboxes destroy --project <project-fingerprint> --target <instance-id> --yes --json
|
|
370
373
|
```
|
|
371
374
|
|
|
372
|
-
|
|
373
|
-
|
|
375
|
+
This destroy works only on a devbox without threads. To destroy a devbox that
|
|
376
|
+
has threads, add `--archive-threads`:
|
|
377
|
+
|
|
378
|
+
```bash
|
|
379
|
+
dvb devboxes destroy --project <project-fingerprint> --target <instance-id> --archive-threads --wait --yes --json
|
|
380
|
+
```
|
|
381
|
+
|
|
382
|
+
This is the same Destroy and archive as the desktop app. It saves each thread's
|
|
383
|
+
history, archives the threads, and then permanently deletes the devbox. Agents
|
|
384
|
+
still running on that devbox will be stopped. Like `devboxes create`, the
|
|
385
|
+
result has `data.operation` and `data.target`, and `--wait` waits up to 10
|
|
386
|
+
minutes for a terminal operation. A failed operation exits 1 and keeps
|
|
387
|
+
`ok: true`; check `data.operation.status` for `succeeded` or `failed` and read
|
|
388
|
+
`data.operation.failure` for the reason.
|
|
389
|
+
|
|
390
|
+
Omit `--wait` to return immediately. Poll the returned operation, or check on
|
|
391
|
+
an interrupted or timed-out wait, with:
|
|
392
|
+
|
|
393
|
+
```bash
|
|
394
|
+
dvb devboxes status --operation <operation-id> --json
|
|
395
|
+
```
|
|
396
|
+
|
|
397
|
+
`--wait` prints that command to stderr before it starts waiting. While a
|
|
398
|
+
request is in progress, check it with `devboxes status` instead of destroying
|
|
399
|
+
the devbox again. If the command reports `unsupported_capability`, that devbox
|
|
400
|
+
can't be destroyed and archived; keep it to preserve its threads' history.
|
|
374
401
|
|
|
375
402
|
Sleep, wake, and destroy are mutations. Confirm they match the user's intent
|
|
376
403
|
before running them. Destroy is permanent, requires `--yes`, and should happen
|
|
@@ -215,7 +215,9 @@ dvb permissions set pause-and-resume-agents project --box <box>
|
|
|
215
215
|
switches, `none`, `move`, or `create` for `folder-access`, and `none`,
|
|
216
216
|
`project`, `user`, `shared`, or `team` for `read-threads`. For
|
|
217
217
|
`pause-and-resume-agents`, choose `none`, `created` (the default), `project`,
|
|
218
|
-
or `user`; wider scopes cover your own threads.
|
|
218
|
+
or `user`; wider scopes cover your own threads. For **Destroy and archive
|
|
219
|
+
devboxes**, `destroy-created-devboxes` takes `none` (the default), `created`,
|
|
220
|
+
or `project`. A box change applies
|
|
219
221
|
only to that box, while a project change applies to existing and future
|
|
220
222
|
devboxes except those configured separately. Template-box-only permissions such as
|
|
221
223
|
`create-team-templates` are rejected for a devbox or a project. Lifecycle and
|
|
@@ -622,7 +624,7 @@ the URL in commands and in the app; it is not part of the public address.
|
|
|
622
624
|
Changing the target port, delivery settings, disablement, or public URL clears
|
|
623
625
|
all claims and subscriptions; renaming does not.
|
|
624
626
|
|
|
625
|
-
Routed traffic goes to one
|
|
627
|
+
Routed traffic goes to one box at a time, and that box has to claim the
|
|
626
628
|
URL after its HTTP listener is running. There are three ways to claim:
|
|
627
629
|
|
|
628
630
|
- In the desktop app, open the Ports menu on the devbox that should receive
|
|
@@ -713,8 +715,8 @@ later; destroy removes it.
|
|
|
713
715
|
|
|
714
716
|
## Services, IDE, SSH, And Mounts
|
|
715
717
|
|
|
716
|
-
`dvb services`
|
|
717
|
-
|
|
718
|
+
`dvb services` lists services that earlier boxes.dev setups registered on the
|
|
719
|
+
selected box, and can start, stop, remove, or show logs for them.
|
|
718
720
|
|
|
719
721
|
`dvb ide` prepares and opens remote editor access. `dvb ssh proxy` supports the
|
|
720
722
|
generated SSH config used by remote editor tools.
|
|
@@ -84,7 +84,7 @@ devboxes can start from. A snapshot preserves the saved filesystem, local
|
|
|
84
84
|
development data, and memory. Apps that run independently of agents and
|
|
85
85
|
terminals, such as Docker containers and system services, keep running on new
|
|
86
86
|
devboxes. Copied agents, terminals, and processes started from them do not
|
|
87
|
-
continue
|
|
87
|
+
continue. Managed projects use the Team Template's current saved version instead; team
|
|
88
88
|
admins update it from the Team Template editor.
|
|
89
89
|
|
|
90
90
|
Take a new snapshot after updating the Template box in a way future devboxes
|
|
@@ -15,7 +15,10 @@ The workbench has a few persistent areas:
|
|
|
15
15
|
selections, so an integration or automation detour can return to the thread
|
|
16
16
|
you were viewing at the reply you were reading. If you were following the
|
|
17
17
|
latest output, you return to the bottom. Each arrow is disabled when there
|
|
18
|
-
is nowhere to go in that direction.
|
|
18
|
+
is nowhere to go in that direction. Both arrows are hidden when the left
|
|
19
|
+
pane is too narrow to fit them beside a readable project name, which can
|
|
20
|
+
happen at narrow widths once the app is zoomed out; **Cmd+[** and **Cmd+]**
|
|
21
|
+
still work. The crosshair button scrolls the thread
|
|
19
22
|
list to the selected thread, first expanding Devboxes or Project and the
|
|
20
23
|
Template box row, folder, or devbox that hides it. It is disabled when no
|
|
21
24
|
thread is selected and hidden when the left pane
|
|
@@ -176,6 +179,7 @@ Panes:
|
|
|
176
179
|
Search:
|
|
177
180
|
|
|
178
181
|
- Search threads: **Cmd+F** (Ctrl+F)
|
|
182
|
+
- Find text on a page without a conversation: **Cmd+F** (Ctrl+F)
|
|
179
183
|
- Search files by name: **Cmd+P** (Ctrl+P)
|
|
180
184
|
- Search file contents: **Cmd+Shift+F** (Ctrl+Shift+F)
|
|
181
185
|
|
|
@@ -183,6 +187,19 @@ The file shortcuts open the workspace search modal from anywhere in the
|
|
|
183
187
|
workbench (see Files, Git, And Review → Workspace Search). On Windows and
|
|
184
188
|
Linux, Ctrl+F and Ctrl+P are left to the shell while the terminal is focused.
|
|
185
189
|
|
|
190
|
+
**Cmd+F** (Ctrl+F) searches what you are looking at. In a conversation, it
|
|
191
|
+
opens Find in conversation (see Search Your Threads), and the file viewer
|
|
192
|
+
keeps its own Find. On a page without a conversation, such as a Team
|
|
193
|
+
Template's page, Project settings, an automation, or billing, it opens a find
|
|
194
|
+
bar at the top right of the window. In the workbench, click in that page
|
|
195
|
+
first; elsewhere in the workbench, the shortcut opens thread search. The find
|
|
196
|
+
bar matches text anywhere in the window, including text in fields and script
|
|
197
|
+
editors, and ignores capitalization. Use **Enter** / **Shift+Enter** or its
|
|
198
|
+
arrows to move between matches, and press **Escape** to close it. The bar
|
|
199
|
+
closes when a dialog opens or you go to another page, and it doesn't search
|
|
200
|
+
inside dialogs such as Settings. Finding text on a page needs the latest
|
|
201
|
+
desktop app.
|
|
202
|
+
|
|
186
203
|
Terminal and Browser tabs (while that pane is focused):
|
|
187
204
|
|
|
188
205
|
- New tab: **Cmd+T** (Ctrl+Shift+T)
|
|
@@ -334,8 +351,10 @@ log out; usage and Help stay beside it.
|
|
|
334
351
|
|
|
335
352
|
For a project that has one, the Template box page is for the project's exact
|
|
336
353
|
Template machine. Use it to manage snapshots, repositories, maintenance, or
|
|
337
|
-
the machine itself; open its terminal, inspect files or Git
|
|
338
|
-
|
|
354
|
+
the machine itself; open its terminal, or inspect files or Git. **New thread**
|
|
355
|
+
at the top of the page opens a new thread on the Template box. While the page
|
|
356
|
+
is open, the box status control shows whether the Template box is awake.
|
|
357
|
+
Managed projects omit the page and its thread,
|
|
339
358
|
snapshot, repository, terminal, and power controls.
|
|
340
359
|
|
|
341
360
|
Under **Project**, select the **Template box** row's title to open its page.
|
|
@@ -41,6 +41,9 @@ Check how the required services start through the documented development
|
|
|
41
41
|
command or configured startup behavior. A manually started database on the
|
|
42
42
|
Team Template editing machine does not establish readiness in a new project;
|
|
43
43
|
the Team Template save flow cleans and cold-boots that machine before capture.
|
|
44
|
+
If you keep a project process running with a systemd unit, set
|
|
45
|
+
`Slice=boxes_workload.slice` in the unit so it stays within the box's workload
|
|
46
|
+
memory limit and appears in the desktop app's process view.
|
|
44
47
|
|
|
45
48
|
A script file on disk is not a registered startup setting. Maintenance and
|
|
46
49
|
destination startup serve different purposes. Read back settings you apply,
|
|
@@ -48,6 +51,25 @@ and report any remaining configuration step. Use the applicable project mode's
|
|
|
48
51
|
lifecycle instructions; see
|
|
49
52
|
[Team Templates](team-template.md#when-a-new-devbox-is-created).
|
|
50
53
|
|
|
54
|
+
## Configure A Stable Public Address
|
|
55
|
+
|
|
56
|
+
When the app needs a stable public address, such as an OAuth callback, a
|
|
57
|
+
webhook endpoint, or a base URL in shared configuration, run
|
|
58
|
+
`dvb-onbox url list --json` on the Template box. Put a suitable Project URL's
|
|
59
|
+
`canonicalUrl` in the configuration that new devboxes will inherit. Listing
|
|
60
|
+
doesn't need the app to be running. To test the URL, start the app on its
|
|
61
|
+
port, claim the URL with `--if-free`, complete the flow or send a request, and
|
|
62
|
+
then release the claim. If a devbox already holds the URL, ask the user before
|
|
63
|
+
taking it over. See
|
|
64
|
+
[Project URL Participation](onbox-agent-tools.md#project-url-participation).
|
|
65
|
+
|
|
66
|
+
If no Project URL fits the app's port, ask the user to create one from
|
|
67
|
+
**Project URLs** in the desktop sidebar, and then use its address. Don't save a
|
|
68
|
+
public link from `dvb-onbox ports share` as the app's lasting address. It only
|
|
69
|
+
reaches the Template box, and every new devbox would inherit it. Until the flow
|
|
70
|
+
has been tested through a Project URL, report remote sign-in or webhook
|
|
71
|
+
delivery as unverified.
|
|
72
|
+
|
|
51
73
|
## Report Readiness For The Requested Work
|
|
52
74
|
|
|
53
75
|
Report what passed, failed, or remains unverified, with the commands and any
|
|
@@ -198,7 +198,9 @@ selector in Git/Review. If boxes.dev detects unindexed direct-child repos, use
|
|
|
198
198
|
**Review new repositories** to choose which ones join the project index. Older
|
|
199
199
|
machines show the previous all-repository **Rescan** action until they update.
|
|
200
200
|
|
|
201
|
-
|
|
201
|
+
While the selected box is asleep, the titlebar and Git/Review show the branch
|
|
202
|
+
and change counts it last reported. Wake the box to see history and diffs or to
|
|
203
|
+
commit.
|
|
202
204
|
|
|
203
205
|
## History View
|
|
204
206
|
|
|
@@ -249,8 +251,9 @@ write permission and branch rules when you push.
|
|
|
249
251
|
If access stops, reconnect the GitHub account used for the project, use
|
|
250
252
|
**Manage repos** to give the boxes.dev App access, or restore the connected
|
|
251
253
|
user's write permission as directed by the error. When an organization cannot
|
|
252
|
-
approve the App for that repository, **
|
|
253
|
-
access** can authorize the official GitHub
|
|
254
|
+
approve the App for that repository, **Connect personal access** under
|
|
255
|
+
**Integrations → GitHub → GitHub CLI access** can authorize the official GitHub
|
|
256
|
+
CLI instead. That personal access
|
|
254
257
|
can authenticate a token-free HTTPS Git request after boxes.dev confirms that
|
|
255
258
|
the same connected user can read the repository. It does not
|
|
256
259
|
convert an SSH remote to HTTPS or change any repository remote.
|
|
@@ -395,9 +398,11 @@ requires it. A devbox startup script that uses GitHub may still need that
|
|
|
395
398
|
connection to finish.
|
|
396
399
|
|
|
397
400
|
Personal sign-in is optional even when App repository access works. Choose
|
|
398
|
-
**
|
|
399
|
-
GitHub, or
|
|
400
|
-
|
|
401
|
+
**Connect personal access** under **GitHub CLI access** in Integrations →
|
|
402
|
+
GitHub, or **Connect** under **Personal GitHub CLI access (optional)** in
|
|
403
|
+
Account or the optional follow-up in onboarding or project setup, or run
|
|
404
|
+
`gh auth login` on a Template box or devbox. The description under **GitHub
|
|
405
|
+
CLI access** names the access `gh` uses. The App covers pull, push, pull requests, and CLI commands
|
|
401
406
|
within its permissions; personal authorization enables broader CLI use,
|
|
402
407
|
within the approved scopes and the user's permissions. The App also supports
|
|
403
408
|
starting workflows and rerunning failed CI after the installation owner approves
|
|
@@ -425,12 +430,15 @@ Contents, Issues, Pull requests, and Workflows. This supports CI retries,
|
|
|
425
430
|
publishing check results, issue changes, code pushes, pull requests, and workflow
|
|
426
431
|
file edits. Actions write also permits starting and canceling workflows and
|
|
427
432
|
managing their runs, logs, and artifacts. The App requests read-only access to
|
|
428
|
-
deployments,
|
|
429
|
-
|
|
433
|
+
deployments, the user's email addresses, commit statuses, and repository
|
|
434
|
+
metadata.
|
|
435
|
+
|
|
436
|
+
A repository admin can install the App for the repositories they administer
|
|
437
|
+
unless the organization only allows owners to install apps.
|
|
430
438
|
|
|
431
439
|
An existing installation's repository or organization owner needs to approve
|
|
432
|
-
|
|
433
|
-
|
|
440
|
+
permission increases in GitHub Settings → GitHub Apps → boxes.dev. Existing
|
|
441
|
+
access will continue while approval is pending.
|
|
434
442
|
Account email access requires each user's approval of the updated GitHub
|
|
435
443
|
authorization. Choose **Update connection** in **Account** or **Integrations →
|
|
436
444
|
GitHub** to review and approve it.
|
|
@@ -444,7 +452,7 @@ includes every App capability.
|
|
|
444
452
|
Managed `gh` will show a direct installation permission-review link when a
|
|
445
453
|
supported command needs a newly requested App grant. This covers Actions
|
|
446
454
|
commands, issue and pull-request changes, and recognized `gh api` writes to
|
|
447
|
-
Checks or Contents and reads of Deployments
|
|
455
|
+
Checks or Contents and reads of Deployments. Explicit
|
|
448
456
|
`--repo`/`-R`, `GH_REPO`, or the CLI's repository selection identifies the account;
|
|
449
457
|
REST endpoints identify their account directly. Recognized GraphQL operations
|
|
450
458
|
with opaque repository IDs don't establish an account, so advice requires all
|
|
@@ -469,13 +477,16 @@ boxes.dev GitHub App can access that project's repositories. If access is
|
|
|
469
477
|
missing, the page names the affected repository and opens the applicable
|
|
470
478
|
GitHub grant or management flow. Request or add the repository there, then
|
|
471
479
|
return to boxes.dev for an automatic recheck or choose **Check again**. An
|
|
472
|
-
organization
|
|
480
|
+
organization owner may need to approve the request. For repository access,
|
|
473
481
|
reconnect GitHub only when the page says the account connection needs it. The
|
|
474
|
-
ready **
|
|
482
|
+
ready **GitHub App access** row shows checkmarked capabilities, with push and
|
|
475
483
|
workflow-file edits shown only where the live repository and installation
|
|
476
484
|
grants allow them. Viewing Actions does not grant permission to start a run.
|
|
477
|
-
|
|
478
|
-
|
|
485
|
+
The missing-access row is a warning only for projects whose Git pull and push
|
|
486
|
+
use automatic GitHub access. For other projects, such as SSH projects, it
|
|
487
|
+
notes that pull request status updates and automatic follow-ups need App
|
|
488
|
+
access. If App approval is unavailable, choose **Connect personal access**
|
|
489
|
+
under **GitHub CLI access**, copy the one-time code, and approve the official
|
|
479
490
|
GitHub CLI on GitHub. Personal access takes priority for managed CLI commands;
|
|
480
491
|
Git and explicit pull-request credential selection still prefers App access
|
|
481
492
|
where it works. Personal access supports eligible HTTPS Git and
|
|
@@ -719,7 +730,9 @@ follow-ups, or turn them off. The dialog notes when the project setting or an
|
|
|
719
730
|
agent turned them on. Follow-ups pause when the selected repository or branch
|
|
720
731
|
changes, including when the pull request is retargeted to another base branch,
|
|
721
732
|
when GitHub CLI access is no longer available, or when boxes.dev cannot queue
|
|
722
|
-
a follow-up after several attempts.
|
|
733
|
+
a follow-up after several attempts. Renaming or transferring the repository on
|
|
734
|
+
GitHub doesn't pause them, whether or not the checkout's remote is updated to
|
|
735
|
+
the new name. They also pause when the agent's thread is
|
|
723
736
|
archived or its devbox is destroyed, including when an automation's cleanup
|
|
724
737
|
destroys a run's devbox. Another thread can then take them over, and a
|
|
725
738
|
restored thread can resume them. Deleting the thread turns its follow-ups off.
|
|
@@ -384,8 +384,9 @@ dvb devboxes wake --project <project> --target <devbox> --json
|
|
|
384
384
|
dvb devboxes destroy --project <project> --target <devbox> --yes --json
|
|
385
385
|
```
|
|
386
386
|
|
|
387
|
-
This command refuses to destroy a devbox with attached threads.
|
|
388
|
-
|
|
387
|
+
This command refuses to destroy a devbox with attached threads. To archive
|
|
388
|
+
those threads and destroy the devbox, add `--archive-threads`; see
|
|
389
|
+
[Agent tools](agent-tools.md#lifecycle-mutations-and-cleanup). Once a thread
|
|
389
390
|
starts on an environment-only devbox, that thread adopts the devbox as its
|
|
390
391
|
anchor thread and the devbox behaves like any other devbox.
|
|
391
392
|
|
|
@@ -35,7 +35,8 @@ confirming the project looks healthy:
|
|
|
35
35
|
|
|
36
36
|
- Open the terminal pane if you want to inspect the environment or run commands.
|
|
37
37
|
- Use the ports menu to open any running local app or copied forwarded URL.
|
|
38
|
-
- Check the Template box page for
|
|
38
|
+
- Check the Template box page for snapshot history, and the box status control
|
|
39
|
+
for whether the Template box is awake.
|
|
39
40
|
- Take a new snapshot when the Template box is in a good state that future
|
|
40
41
|
devboxes should start from.
|
|
41
42
|
|
|
@@ -88,7 +88,8 @@ Use this terminology consistently:
|
|
|
88
88
|
- `onbox-agent-tools.md`: the separate, narrow `dvb-onbox` surface available
|
|
89
89
|
only to coding agents inside a Template box or devbox, including setup,
|
|
90
90
|
snapshots, user-authorized delegated thread starts, project devbox
|
|
91
|
-
folders, managing the project's automations, pull request follow-ups,
|
|
91
|
+
folders, managing the project's automations, pull request follow-ups,
|
|
92
|
+
checking whether the user has the thread open on desktop or mobile, and
|
|
92
93
|
publishing inline visuals, images, and videos.
|
|
93
94
|
- `automations.md`: Thread Automations, scheduled/API-triggered runs, Slack and
|
|
94
95
|
Linear-triggered runs, run history, capacity, spawned devbox threads, and
|
|
@@ -46,6 +46,14 @@ If Linear reports missing scopes, a revoked app, or invalid token state,
|
|
|
46
46
|
use the recovery action on the Linear integration home. Team admins can also
|
|
47
47
|
reconnect Linear and run **Recheck** from Team settings.
|
|
48
48
|
|
|
49
|
+
To disconnect, a team admin chooses **Disconnect**, then **Confirm
|
|
50
|
+
disconnect**, in **Team connection** on the Linear integration home, or
|
|
51
|
+
**Disconnect Linear** from the **…** menu in Team settings. Disconnecting
|
|
52
|
+
removes the boxes.dev app from the Linear workspace, pauses the team's Linear
|
|
53
|
+
automations, and unlinks members' Linear identities. Existing boxes.dev threads
|
|
54
|
+
stay. To use Linear again, a team admin connects it again, and each member
|
|
55
|
+
relinks their identity and reactivates their automation.
|
|
56
|
+
|
|
49
57
|
## Link Your Linear Identity
|
|
50
58
|
|
|
51
59
|
Open Linear from the desktop workbench's **Integrations** section. If Linear
|
|
@@ -110,6 +118,13 @@ Reply in the Linear Agent Session to send a follow-up prompt to the linked
|
|
|
110
118
|
boxes.dev thread. If a turn is already running, boxes.dev queues the follow-up
|
|
111
119
|
message; otherwise it starts the next turn in the existing thread.
|
|
112
120
|
|
|
121
|
+
Only the Linear account currently linked to the thread owner's boxes.dev user
|
|
122
|
+
can send follow-ups or stop the thread. Replies from other Linear users don't
|
|
123
|
+
reach it. After the owner unlinks their Linear account or links a different
|
|
124
|
+
one, replies from the earlier account don't reach the thread either; boxes.dev
|
|
125
|
+
answers those in Linear with a note to link the account or reply from the
|
|
126
|
+
linked one.
|
|
127
|
+
|
|
113
128
|
Use Linear's stop control to stop active boxes.dev work. Undelegating the
|
|
114
129
|
agent, moving the issue to a terminal completed or canceled state, or deleting
|
|
115
130
|
the issue also stops or disengages the linked work when Linear sends that
|
|
@@ -79,7 +79,9 @@ Open a project to see its threads. The list can include:
|
|
|
79
79
|
collapsed and show their devbox count and a status icon when one of their
|
|
80
80
|
threads needs attention, for example because it is running, needs input, or
|
|
81
81
|
is unread. Opening a folder lists its
|
|
82
|
-
devboxes, 15 at a time with **Load more devboxes**.
|
|
82
|
+
devboxes, 15 at a time with **Load more devboxes**. In the iPhone and
|
|
83
|
+
Android apps, an open folder's row stays at the top of the list while its
|
|
84
|
+
devboxes scroll past. Folders are read-only on
|
|
83
85
|
mobile: creating, editing, and moving devboxes between them stay in the
|
|
84
86
|
desktop app, and a pinned devbox lists under pinned threads instead of its
|
|
85
87
|
folder;
|
|
@@ -523,6 +525,9 @@ include:
|
|
|
523
525
|
date, and **Folders** groups them into the user's desktop folders. It is
|
|
524
526
|
saved on the account and applies only to the mobile app; desktop always
|
|
525
527
|
shows folders;
|
|
528
|
+
- **List density**: **Comfortable** (the default), **Cozy**, or **Compact**
|
|
529
|
+
spacing for a project's thread list. It is saved on the phone and does not
|
|
530
|
+
change the desktop sidebar's density;
|
|
526
531
|
- release package details and refresh controls in installed builds;
|
|
527
532
|
- account deletion.
|
|
528
533
|
- a Help center link that opens the public guides at `https://boxes.dev/help`
|