@boxes-dev/dvb-runtime 1.0.1076 → 1.0.1077
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 +10 -3
- package/dist/bin/dvb.mjs +587 -218
- package/dist/bin/dvbd.mjs +4 -4
- package/dist/product-docs/references/cli.md +9 -0
- package/dist/product-docs/references/desktop-workbench.md +21 -12
- package/dist/product-docs/references/files-git-and-review.md +96 -32
- package/dist/product-docs/references/fork-workflows.md +5 -2
- package/dist/product-docs/references/getting-started.md +3 -1
- package/dist/product-docs/references/index.md +1 -1
- package/dist/product-docs/references/linear.md +3 -3
- package/dist/product-docs/references/mobile.md +14 -10
- package/dist/product-docs/references/onbox-agent-tools.md +115 -10
- package/dist/product-docs/references/project-setup.md +24 -14
- package/dist/product-docs/references/security-and-data.md +1 -1
- package/dist/product-docs/references/slack.md +23 -22
- package/dist/product-docs/references/tailscale.md +2 -2
- package/dist/product-docs/references/team-template.md +33 -17
- package/dist/product-docs/references/template-box-environment.md +1 -1
- package/dist/product-docs/references/threads-and-agents.md +2 -2
- package/dist/product-docs/references/troubleshooting.md +3 -3
- package/package.json +2 -2
package/dist/bin/dvbd.mjs
CHANGED
|
@@ -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.1077";
|
|
64679
|
+
const rawGitSha = "8b1aec823d1569de8d7eba6b9f55b50c500f38de";
|
|
64680
|
+
const rawSentryRelease = "boxes-dev-dvb@1.0.1077+8b1aec823d1569de8d7eba6b9f55b50c500f38de";
|
|
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;
|
|
@@ -66894,7 +66894,7 @@ var init_packageVersion = __esm({
|
|
|
66894
66894
|
return path8.join(process.cwd(), "dvb");
|
|
66895
66895
|
};
|
|
66896
66896
|
readEmbeddedPackageVersion = () => {
|
|
66897
|
-
const raw = "1.0.
|
|
66897
|
+
const raw = "1.0.1077";
|
|
66898
66898
|
return trimVersion(raw);
|
|
66899
66899
|
};
|
|
66900
66900
|
readNearestPackageMetadata = (basePath) => {
|
|
@@ -167,6 +167,8 @@ maintenance script and its complete GitHub watch set together:
|
|
|
167
167
|
|
|
168
168
|
```bash
|
|
169
169
|
dvb projects maintenance get --project <project> --json
|
|
170
|
+
dvb projects maintenance runs --project <project> --json
|
|
171
|
+
dvb projects maintenance logs --project <project> --run <run-id> --json
|
|
170
172
|
dvb projects maintenance apply --project <project> \
|
|
171
173
|
--script-file <path> --timeout-seconds <1-480> \
|
|
172
174
|
--watches-file <path> --if-revision <revision> --json
|
|
@@ -181,6 +183,13 @@ baseline. Team Template member projects support lifecycle editing but return
|
|
|
181
183
|
`template_maintenance_unavailable` for maintenance because they have no
|
|
182
184
|
personal Template box.
|
|
183
185
|
|
|
186
|
+
For troubleshooting, `runs` returns active runs and up to twenty retained
|
|
187
|
+
completed runs, including triggers, timestamps, script status, exit codes, and
|
|
188
|
+
failure details. Pass a returned `publicRunId` to `logs` to read the recorded
|
|
189
|
+
combined stdout/stderr tail of up to 4,000 characters. These reads do not wake
|
|
190
|
+
the Template box or start maintenance. Logs can be incomplete during an active
|
|
191
|
+
run; unknown or expired IDs return `maintenance_run_not_found`.
|
|
192
|
+
|
|
184
193
|
## Open A Terminal
|
|
185
194
|
|
|
186
195
|
Use:
|
|
@@ -260,7 +260,7 @@ other new-devbox defaults, and the Claude and Codex settings kept on every box
|
|
|
260
260
|
|
|
261
261
|
To change the automatic idle-sleep timeout, open **Account
|
|
262
262
|
→ Sleep timeout** and choose 5, 15, 30, or 60 minutes, or **Team default**.
|
|
263
|
-
Team admins can set the default in **Team
|
|
263
|
+
Team admins can set the default in **Team settings → Sleep timeout**; without
|
|
264
264
|
a custom setting it is five minutes. Your choice overrides the team default
|
|
265
265
|
for your Template boxes and devboxes, including Team Template member projects.
|
|
266
266
|
Changes apply to existing and new boxes. A running box may keep its current
|
|
@@ -295,7 +295,7 @@ devbox. See `fork-workflows.md` for that workflow.
|
|
|
295
295
|
A team can have several named Team Templates: shared starting
|
|
296
296
|
environments that team admins prepare separately from any member's projects.
|
|
297
297
|
Team admins can open **Team Templates** from the desktop project selector or
|
|
298
|
-
Team
|
|
298
|
+
Team settings, then select the exact template they want to inspect or edit. To
|
|
299
299
|
create a project, start the ordinary **New project...** flow and choose **Start
|
|
300
300
|
from a Team Template**; project creation does not start from the template
|
|
301
301
|
detail page.
|
|
@@ -329,14 +329,16 @@ agent. On first use, choose **Start dictation** and allow microphone access.
|
|
|
329
329
|
Your audio is sent to OpenAI to turn it into text. While dictation listens, the
|
|
330
330
|
microphone turns solid blue and the composer has a blue outline. Words appear
|
|
331
331
|
live at your cursor if you were typing in the composer, otherwise at the end of
|
|
332
|
-
your draft. A blue caret with a small microphone marks where the next
|
|
333
|
-
will land, and the words from the current recording stay highlighted
|
|
334
|
-
|
|
335
|
-
|
|
336
|
-
|
|
337
|
-
|
|
338
|
-
|
|
339
|
-
|
|
332
|
+
your draft. A blue caret with a small microphone above it marks where the next
|
|
333
|
+
words will land, and the words from the current recording stay highlighted
|
|
334
|
+
while you speak. Click the microphone again to stop listening; it turns off
|
|
335
|
+
right away, and any last words appear in your draft a moment later. Then
|
|
336
|
+
review, edit, and send. Clicking Send or pressing Enter while dictating adds
|
|
337
|
+
the last words, then sends the message; dictation never sends on its own. You
|
|
338
|
+
can keep typing and adding attachments while speaking. The microphone shows a
|
|
339
|
+
spinner while connecting. Switching threads or hiding the window stops capture
|
|
340
|
+
and keeps the text already in your draft. An agent's Stop button remains
|
|
341
|
+
separate.
|
|
340
342
|
|
|
341
343
|
Each recording stops after three minutes. Frequent use is limited to 120 starts
|
|
342
344
|
per account in an hour. If the connection fails, any words already received are
|
|
@@ -380,7 +382,7 @@ finished agents leave it after your next message. The inspector is read-only.
|
|
|
380
382
|
Older conversations may not have a subagent list.
|
|
381
383
|
|
|
382
384
|
To distinguish Claude and Codex threads at a glance, turn on **Show agent
|
|
383
|
-
logos** in **Desktop app settings > General > Thread
|
|
385
|
+
logos** in **Desktop app settings > General > Thread list**. The logos appear
|
|
384
386
|
at the right edge of thread rows and are off by default.
|
|
385
387
|
|
|
386
388
|
Thread rows can show unread or attention state. When a thread completes, fails,
|
|
@@ -595,7 +597,7 @@ own role is read-only there, so another team admin must change it. Invitations
|
|
|
595
597
|
remain for new accounts; if an email is already on the team, manage that person
|
|
596
598
|
in the **Members** section instead.
|
|
597
599
|
|
|
598
|
-
Team
|
|
600
|
+
Team settings also shows **Static egress IP**. This optional feature gives the
|
|
599
601
|
team a stable public IPv4 to allowlist at an external database or service. It
|
|
600
602
|
is visible but off by default; use **Talk to us** to request enablement. Once
|
|
601
603
|
enabled, all team members can copy the current static IP and read the configured
|
|
@@ -638,6 +640,13 @@ If a downloaded update fails to install, the app does not download that same
|
|
|
638
640
|
version again in the background. Choose **Check for Updates…** in the app menu
|
|
639
641
|
to try it again; newer versions still download automatically.
|
|
640
642
|
|
|
643
|
+
On Linux, the AppImage updates itself the same way. The .deb and .rpm packages
|
|
644
|
+
add the boxes.dev package repository when installed, so system updates keep
|
|
645
|
+
the app current. When the app needs a newer version before it can continue,
|
|
646
|
+
an app installed from a .deb or .rpm package shows the command to run, such as
|
|
647
|
+
`sudo apt update && sudo apt install --only-upgrade boxes-dev`, and a
|
|
648
|
+
**Restart App** button for after the update.
|
|
649
|
+
|
|
641
650
|
Use the Help button next to your account identity at the bottom of the left pane
|
|
642
651
|
for quick troubleshooting tips and to send product feedback, when the button is
|
|
643
652
|
shown.
|
|
@@ -281,7 +281,7 @@ direct children with token-free GitHub HTTPS remotes, configures automatic
|
|
|
281
281
|
pull/push access, and adds them to the project index. A name collision uses a
|
|
282
282
|
stable owner-qualified folder name instead. On success, boxes.dev automatically
|
|
283
283
|
saves one new Template snapshot so future devboxes inherit the added checkouts.
|
|
284
|
-
Existing devboxes remain unchanged. **Review
|
|
284
|
+
Existing devboxes remain unchanged. **Review startup script** opens the existing
|
|
285
285
|
setting in **Devbox lifecycle → New devbox defaults**; boxes.dev does not edit
|
|
286
286
|
the script for you.
|
|
287
287
|
|
|
@@ -509,6 +509,10 @@ terminal or external commits, pull-request bodies, or pull-request metadata.
|
|
|
509
509
|
Following a trailer opens the read-only thread only when the viewer's current
|
|
510
510
|
team access allows it.
|
|
511
511
|
|
|
512
|
+
The Git settings also include **Automate follow-ups on new pull requests**,
|
|
513
|
+
which is off by default; see
|
|
514
|
+
[Automatic Pull Request Follow-ups](#automatic-pull-request-follow-ups).
|
|
515
|
+
|
|
512
516
|
When the default branch has local commits, Git/Review can move that committed
|
|
513
517
|
work to a new branch, restore only the local default branch to its upstream,
|
|
514
518
|
publish the new branch, and create a pull request. The Create pull request
|
|
@@ -561,8 +565,10 @@ flows remain separate, do not pull, and preserve their existing remote-default
|
|
|
561
565
|
safety rules.
|
|
562
566
|
|
|
563
567
|
On an existing pull request, Git/Review names the next action explicitly, such
|
|
564
|
-
as Fix checks, Mark ready, Address feedback, Push to update
|
|
565
|
-
|
|
568
|
+
as Resolve conflicts, Fix checks, Mark ready, Address feedback, Push to update
|
|
569
|
+
PR, or Merge. Resolve conflicts prepares a prompt asking the agent to bring the
|
|
570
|
+
base branch in the way the repository does; review it, then choose **Send**.
|
|
571
|
+
Push to update PR uses the same Pull-first Push dialog. When **View PR #N** appears,
|
|
566
572
|
it opens that pull request in your browser.
|
|
567
573
|
|
|
568
574
|
Hover over or click the PR indicator in the conversation header to see the
|
|
@@ -572,7 +578,8 @@ multiple pull requests, the panel lists each one with its own links.
|
|
|
572
578
|
|
|
573
579
|
Choose **Fix CI & apply
|
|
574
580
|
feedback** to prepare the available CI fixes and review feedback together.
|
|
575
|
-
Choose **Fix CI** or **Apply review feedback** to handle just one
|
|
581
|
+
Choose **Fix CI** or **Apply review feedback** to handle just one, or
|
|
582
|
+
**Resolve conflicts** when the branch conflicts with its base branch; an option
|
|
576
583
|
is unavailable when there is no work of that kind. Review the prepared prompt
|
|
577
584
|
and **Code review** attachment, then choose **Send** to start the agent.
|
|
578
585
|
Choose **Open PR in Git/Review** in the same panel to inspect the pull request.
|
|
@@ -583,20 +590,72 @@ checks for that PR; it doesn't mean the checks passed.
|
|
|
583
590
|
|
|
584
591
|
## Automatic Pull Request Follow-ups
|
|
585
592
|
|
|
586
|
-
|
|
587
|
-
|
|
588
|
-
|
|
589
|
-
|
|
590
|
-
|
|
591
|
-
|
|
592
|
-
|
|
593
|
-
|
|
594
|
-
|
|
595
|
-
|
|
596
|
-
|
|
597
|
-
|
|
598
|
-
|
|
599
|
-
or
|
|
593
|
+
Automatic follow-ups let an agent thread keep working on its pull request
|
|
594
|
+
without you starting each step. When a selected event happens, boxes.dev wakes
|
|
595
|
+
that thread's machine and asks the agent to follow up. The events are:
|
|
596
|
+
|
|
597
|
+
- **Failed checks**: a check on the pull request fails.
|
|
598
|
+
- **Review feedback from people**: a review or comment from someone GitHub
|
|
599
|
+
lists as the repository's owner, an organization member, or a collaborator.
|
|
600
|
+
- **Bot review feedback**: a review or comment that GitHub identifies as
|
|
601
|
+
bot-authored.
|
|
602
|
+
- **Merge conflicts**: the pull request branch conflicts with its base branch.
|
|
603
|
+
|
|
604
|
+
To turn follow-ups on for one pull request, open its actions menu in
|
|
605
|
+
Git/Review, choose **Automate follow-ups**, and select the events. The selected
|
|
606
|
+
devbox or Template box needs **GitHub CLI access**, and the boxes.dev GitHub
|
|
607
|
+
App needs access to the repository so GitHub can send the events; personal
|
|
608
|
+
GitHub CLI access alone cannot provide them. Follow-ups work only for pull
|
|
609
|
+
requests into the repository's default branch. An agent can also turn them on
|
|
610
|
+
itself with `dvb-onbox pr followups enable`; see
|
|
611
|
+
[Pull Request Follow-ups](onbox-agent-tools.md#pull-request-follow-ups).
|
|
612
|
+
|
|
613
|
+
To turn them on for new pull requests automatically, open **Project settings**,
|
|
614
|
+
expand **Git**, and turn on **Automate follow-ups on new pull requests**. It is
|
|
615
|
+
off by default. While it is on, boxes.dev turns on all four events when one of
|
|
616
|
+
the project's threads opens a pull request, either with **Create PR** in
|
|
617
|
+
Git/Review or by an agent running `gh pr create` on one of the project's
|
|
618
|
+
devboxes. The thread that opened the pull request handles its follow-ups, and
|
|
619
|
+
an agent's `gh pr create` output ends with a line saying they are on. The
|
|
620
|
+
setting does not cover pull requests opened any other way, such as on
|
|
621
|
+
github.com or with `gh pr create` in your own terminal, or a branch that
|
|
622
|
+
already had an open pull request. It acts only when the pull request is
|
|
623
|
+
created, so turning a pull request's follow-ups off later stays in effect.
|
|
624
|
+
|
|
625
|
+
Before acting, the agent fetches the pull request's current state with `gh`. It
|
|
626
|
+
may edit the worktree, run tests, commit, and push to the pull request branch.
|
|
627
|
+
If a safe fix is not clear, it stops and explains why. When a failing check is
|
|
628
|
+
something it can't fix, it also turns follow-ups off. When feedback needs no
|
|
629
|
+
changes, such as an approval, it says so in the thread and leaves follow-ups
|
|
630
|
+
on. An automatic follow-up never merges the pull request,
|
|
631
|
+
deletes its branch, or reruns workflows. It force-pushes only after rebasing to
|
|
632
|
+
resolve merge conflicts, and then only with `--force-with-lease
|
|
633
|
+
--force-if-includes`.
|
|
634
|
+
|
|
635
|
+
Review feedback from people includes reviews that request changes or have a
|
|
636
|
+
summary comment, inline review comments, and comments in the pull request's
|
|
637
|
+
conversation. Approvals without a comment, edits, and deletions do not start a
|
|
638
|
+
follow-up. Your own reviews and comments never start one, because agents act on
|
|
639
|
+
GitHub as you; message the agent in its thread instead. The owner, member, and
|
|
640
|
+
collaborator filter uses the relationship GitHub reports for each author; it
|
|
641
|
+
does not check whether the author can write to the repository. boxes.dev waits
|
|
642
|
+
until two minutes pass without a new comment, or ten minutes after the first
|
|
643
|
+
one, then sends the comments together. If another selected event is ready in
|
|
644
|
+
the meantime, its follow-up starts right away and includes the waiting
|
|
645
|
+
comments. The agent replies to or resolves review conversations only
|
|
646
|
+
when your instructions or the project's agent guidance tell it to.
|
|
647
|
+
|
|
648
|
+
GitHub does not announce new merge conflicts, so boxes.dev checks the pull
|
|
649
|
+
request about ten minutes after its base branch changes, or an hour after the
|
|
650
|
+
last conflict follow-up if that is later. When GitHub reports a
|
|
651
|
+
conflict, the agent brings the base branch into the pull request branch the way
|
|
652
|
+
the repository does: it rebases when the project's agent instructions or the
|
|
653
|
+
repository's `pull.rebase` Git setting say to, and merges otherwise. Updating
|
|
654
|
+
the branch can dismiss existing approvals in some repositories. Conflicts alone
|
|
655
|
+
wake the agent at most once an hour and once for each pull request commit, so
|
|
656
|
+
if the agent can't resolve a conflict, boxes.dev won't ask again until the
|
|
657
|
+
branch changes. A follow-up for another event can also include a current
|
|
658
|
+
conflict.
|
|
600
659
|
|
|
601
660
|
When the pull request merges, boxes.dev will also send that agent a final
|
|
602
661
|
notice so it can account for the merge in future work. This may wake the
|
|
@@ -607,19 +666,24 @@ deleted threads will not receive it. Turning follow-ups off will also turn off
|
|
|
607
666
|
the merge notice. Closing a pull request without merging will end follow-ups
|
|
608
667
|
silently.
|
|
609
668
|
|
|
610
|
-
|
|
611
|
-
|
|
612
|
-
|
|
613
|
-
|
|
614
|
-
|
|
615
|
-
|
|
616
|
-
|
|
617
|
-
|
|
618
|
-
|
|
619
|
-
|
|
620
|
-
|
|
621
|
-
|
|
622
|
-
|
|
669
|
+
Only one agent thread per boxes.dev account can handle follow-ups for a pull
|
|
670
|
+
request at a time. Turning them on from another thread will show the current
|
|
671
|
+
thread and ask you to move the job. While that thread is still available,
|
|
672
|
+
agents move follow-ups to their own thread only when you ask.
|
|
673
|
+
|
|
674
|
+
Use **Edit follow-ups** to change the selected events, resume paused
|
|
675
|
+
follow-ups, or turn them off. The dialog notes when the project setting or an
|
|
676
|
+
agent turned them on. Follow-ups pause when the selected repository or branch
|
|
677
|
+
changes, including when the pull request is retargeted to another base branch,
|
|
678
|
+
when GitHub CLI access is no longer available, or when boxes.dev cannot queue
|
|
679
|
+
a follow-up after several attempts. They also pause when the agent's thread is
|
|
680
|
+
archived or its devbox is destroyed, including when an automation's cleanup
|
|
681
|
+
destroys a run's devbox. Another thread can then take them over, and a
|
|
682
|
+
restored thread can resume them. Deleting the thread turns its follow-ups off.
|
|
683
|
+
When you destroy a devbox in the desktop app, the confirmation lists the pull
|
|
684
|
+
requests whose follow-ups will stop. Follow-ups end when the pull request
|
|
685
|
+
closes or merges. The manual **Fix checks**, **Address feedback**, and
|
|
686
|
+
**Resolve conflicts** actions remain available.
|
|
623
687
|
|
|
624
688
|
After the selected repository, remote, or branch changes, Git/Review may
|
|
625
689
|
briefly show that GitHub repository state is updating. Pull-request actions
|
|
@@ -640,7 +704,7 @@ Common actions:
|
|
|
640
704
|
or line range when that operation is available.
|
|
641
705
|
- Open the selected diff file in Files by clicking its path in the diff header.
|
|
642
706
|
- Enter a commit message and choose Commit, or press Cmd/Ctrl+Enter.
|
|
643
|
-
- Enable Amend
|
|
707
|
+
- Enable **Amend last commit** when the selected repo supports amending.
|
|
644
708
|
|
|
645
709
|
Commit is disabled until there is at least one staged file, a non-empty commit
|
|
646
710
|
message, no unresolved conflicts, and no other Git action in progress.
|
|
@@ -39,7 +39,7 @@ If an ordinary project's Template box has changed in a way future devboxes shoul
|
|
|
39
39
|
new snapshot before starting the devbox.
|
|
40
40
|
|
|
41
41
|
To configure startup behavior, open **Project settings** in the desktop app and
|
|
42
|
-
edit **Startup
|
|
42
|
+
edit **Startup script** under **Devbox lifecycle** > **New devbox defaults**.
|
|
43
43
|
The field saves shell commands directly as a project setting; boxes.dev does
|
|
44
44
|
not create a script file for it. The startup timeout defaults to 60 seconds and
|
|
45
45
|
can be set from 1 to 120 seconds.
|
|
@@ -345,7 +345,10 @@ Destroy and archive permanently deletes the devbox filesystem and preserves its
|
|
|
345
345
|
eligible threads as archived cold-storage transcripts, including secondary
|
|
346
346
|
threads that were already archived inside the devbox. The confirmation dialog
|
|
347
347
|
warns about uncommitted changes, changed files, and local-only commits when that
|
|
348
|
-
information is available.
|
|
348
|
+
information is available. It also names the pull requests whose automatic
|
|
349
|
+
follow-ups the devbox's threads handle. Destroying the devbox stops those
|
|
350
|
+
follow-ups, and the pull request shows them as paused until a restored or
|
|
351
|
+
other thread turns them on again. The devbox's threads move into the archived section
|
|
349
352
|
of the thread list as soon as the destroy starts, on every device, while the
|
|
350
353
|
cold-storage archive finishes in the background; if archiving fails, the
|
|
351
354
|
threads return to the active list untouched. Preserving the transcripts does
|
|
@@ -66,7 +66,9 @@ The recommended boxes.dev workflow is:
|
|
|
66
66
|
|
|
67
67
|
## Desktop App Orientation
|
|
68
68
|
|
|
69
|
-
The desktop app is the main workbench.
|
|
69
|
+
The desktop app is the main workbench. It is available for macOS
|
|
70
|
+
(`https://boxes.dev/mac`) and Linux (`https://boxes.dev/linux`, with .deb,
|
|
71
|
+
.rpm, and AppImage packages).
|
|
70
72
|
|
|
71
73
|
The left side is the thread list. It groups work on devboxes, automations, and,
|
|
72
74
|
when the project has one, the Template box. New-thread controls let you choose
|
|
@@ -85,7 +85,7 @@ Use this terminology consistently:
|
|
|
85
85
|
- `onbox-agent-tools.md`: the separate, narrow `dvb-onbox` surface available
|
|
86
86
|
only to coding agents inside a Template box or devbox, including setup,
|
|
87
87
|
snapshots, user-authorized delegated thread starts, project devbox
|
|
88
|
-
folders,
|
|
88
|
+
folders, managing the project's automations, and pull request follow-ups.
|
|
89
89
|
- `automations.md`: Thread Automations, scheduled/API-triggered runs, Slack and
|
|
90
90
|
Linear-triggered runs, run history, capacity, spawned devbox threads, and
|
|
91
91
|
automations created by agents.
|
|
@@ -28,7 +28,7 @@ assignment receiver from Integrations.
|
|
|
28
28
|
## Connect Linear
|
|
29
29
|
|
|
30
30
|
Open the desktop workbench's **Integrations** section and choose **Connect**
|
|
31
|
-
for Linear. Team admins can also connect Linear from **Team
|
|
31
|
+
for Linear. Team admins can also connect Linear from **Team settings**. Linear
|
|
32
32
|
opens an authorization screen; review the permissions and approve the app for
|
|
33
33
|
the workspace.
|
|
34
34
|
|
|
@@ -40,11 +40,11 @@ administrative activity, and technical details. Expand **Linear team access**
|
|
|
40
40
|
and choose **Manage in Linear** to open the connected workspace's application
|
|
41
41
|
settings. A Linear workspace admin can grant or revoke team access there. After
|
|
42
42
|
the change, a boxes.dev team admin can run **Check** to refresh the list.
|
|
43
|
-
The same team-level information remains available in Team
|
|
43
|
+
The same team-level information remains available in Team settings.
|
|
44
44
|
|
|
45
45
|
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
|
-
reconnect Linear and run **Recheck** from Team
|
|
47
|
+
reconnect Linear and run **Recheck** from Team settings.
|
|
48
48
|
|
|
49
49
|
## Link Your Linear Identity
|
|
50
50
|
|
|
@@ -86,7 +86,7 @@ to that exact devbox rather than another project machine.
|
|
|
86
86
|
|
|
87
87
|
Tap the new-thread button to open a new-devbox draft directly. Long-press it
|
|
88
88
|
to open the menu with **New devbox + thread** and, in an ordinary project,
|
|
89
|
-
**New thread on
|
|
89
|
+
**New thread on Template box**. A Team Template member project has no template
|
|
90
90
|
choice. If the project does not support devboxes, tapping opens a Template-box
|
|
91
91
|
draft instead. The draft uses the project's last Codex or Claude choice from
|
|
92
92
|
mobile, desktop, or
|
|
@@ -154,13 +154,17 @@ text size as the composer. The composer can also show:
|
|
|
154
154
|
|
|
155
155
|
Tap **Dictate** (the microphone beside Send or the agent's Stop button) to
|
|
156
156
|
speak a message to Codex or Claude. On first use, tap **Start dictation** and
|
|
157
|
-
allow microphone access. Audio is sent to OpenAI to turn it into text.
|
|
158
|
-
|
|
159
|
-
|
|
160
|
-
|
|
161
|
-
|
|
162
|
-
|
|
163
|
-
|
|
157
|
+
allow microphone access. Audio is sent to OpenAI to turn it into text. While
|
|
158
|
+
dictation listens, the microphone turns solid blue and the composer has a blue
|
|
159
|
+
outline. Words appear live at the end of your editable draft and stay
|
|
160
|
+
highlighted while you speak, with a blue caret and a small microphone above it
|
|
161
|
+
marking where the next words will land. Tap the microphone again to stop
|
|
162
|
+
listening; it turns off right away, and any last words appear a moment later.
|
|
163
|
+
Then review, edit, and Send. Tapping Send while dictating adds the last words,
|
|
164
|
+
then sends the message; dictation never sends on its own and preserves
|
|
165
|
+
attachments. The microphone shows a spinner while connecting. Leaving the
|
|
166
|
+
thread or putting the app in the background stops capture and keeps the
|
|
167
|
+
draft's text. The agent's Stop button still controls its work.
|
|
164
168
|
|
|
165
169
|
A recording stops after three minutes; frequent use is limited to 120 starts
|
|
166
170
|
per account in an hour. If the connection fails, words already received are
|
|
@@ -398,8 +402,8 @@ choose **Use this account**, **Re-authenticate** or **Edit API key**, **Check
|
|
|
398
402
|
now**, or **Remove**. An older Claude account labeled **Setup token** offers
|
|
399
403
|
**Switch to claude.ai login** instead of **Re-authenticate**. Once a claude.ai
|
|
400
404
|
login is saved, the **Allow claude.ai connectors** switch below the Claude
|
|
401
|
-
accounts controls whether
|
|
402
|
-
|
|
405
|
+
accounts controls whether Claude can use the connectors added on claude.ai. A
|
|
406
|
+
change takes effect the next time Claude starts.
|
|
403
407
|
|
|
404
408
|
To sign in to Codex, tap **Log in with ChatGPT**. The app shows a one-time
|
|
405
409
|
code, and **Open ChatGPT** copies it and opens the ChatGPT device sign-in page.
|
|
@@ -605,6 +605,8 @@ Template maintenance uses one script and one complete GitHub watch set:
|
|
|
605
605
|
|
|
606
606
|
```bash
|
|
607
607
|
dvb-onbox project maintenance get --json
|
|
608
|
+
dvb-onbox project maintenance runs --json
|
|
609
|
+
dvb-onbox project maintenance logs --run <run-id> --json
|
|
608
610
|
dvb-onbox project maintenance apply \
|
|
609
611
|
--script-file /home/boxes/<file> \
|
|
610
612
|
--timeout-seconds <1-480> \
|
|
@@ -628,6 +630,16 @@ grandfathered read-only watches remain unchanged. Maintenance reads and writes
|
|
|
628
630
|
on an ordinary Template box require **Edit template maintenance**, a separate
|
|
629
631
|
permission that covers the script and GitHub watches together.
|
|
630
632
|
|
|
633
|
+
To investigate maintenance, list runs and choose a `publicRunId` for `logs`.
|
|
634
|
+
History includes active runs and up to twenty retained completed runs, with
|
|
635
|
+
trigger sources, timestamps, script status, exit code, and failure details.
|
|
636
|
+
Logs return the recorded combined stdout/stderr tail of up to 4,000 characters;
|
|
637
|
+
output may be incomplete while a run is active. These commands only read saved
|
|
638
|
+
records and do not start maintenance or wake a machine. Unknown, expired, and
|
|
639
|
+
unavailable run IDs return `maintenance_run_not_found`. The existing maintenance
|
|
640
|
+
permission and Template box or Team Template editing-session requirements also
|
|
641
|
+
apply to history and logs.
|
|
642
|
+
|
|
631
643
|
The same maintenance commands work in a Team Template's current editing
|
|
632
644
|
session. They update that Team Template's shared maintenance script and watches
|
|
633
645
|
and require the editing session's owner to remain a team admin. Use repository
|
|
@@ -795,6 +807,66 @@ When a user-required title change returns `title_editing_disabled`, request
|
|
|
795
807
|
only `update-thread-titles` through the Agent permissions command above. Do not
|
|
796
808
|
request it merely to perform an optional rename after unrelated work.
|
|
797
809
|
|
|
810
|
+
## Pull Request Follow-ups
|
|
811
|
+
|
|
812
|
+
boxes.dev can send a managed Codex or Claude thread a message when its pull
|
|
813
|
+
request needs attention: checks fail, people or bots leave review feedback, or
|
|
814
|
+
the branch has merge conflicts with its base branch. Follow-ups need an open
|
|
815
|
+
pull request in a repository the boxes.dev GitHub App can access, and GitHub
|
|
816
|
+
CLI access on the devbox so the agent can act on them. They cover only pull
|
|
817
|
+
requests into the repository's default branch. One thread per boxes.dev
|
|
818
|
+
account handles a pull request's follow-ups at a time.
|
|
819
|
+
|
|
820
|
+
When the project's **Automate follow-ups on new pull requests** Git setting is
|
|
821
|
+
on, `gh pr create` turns on all four triggers for the new pull request in the
|
|
822
|
+
thread that ran it, and its output ends with a line saying so. A line saying
|
|
823
|
+
follow-ups only work for pull requests into the default branch means none were
|
|
824
|
+
turned on, and a line saying boxes.dev couldn't turn them on gives the reason.
|
|
825
|
+
When gh prints nothing about follow-ups and you need to know whether they are
|
|
826
|
+
on, run `status`.
|
|
827
|
+
|
|
828
|
+
Check, turn on, or turn off follow-ups for the pull request of the branch
|
|
829
|
+
checked out in the current repository:
|
|
830
|
+
|
|
831
|
+
```bash
|
|
832
|
+
dvb-onbox pr followups status [--repo <path>] [--json]
|
|
833
|
+
dvb-onbox pr followups enable [--repo <path>] [--triggers <list>] [--take-over] [--json]
|
|
834
|
+
dvb-onbox pr followups disable [--repo <path>] [--json]
|
|
835
|
+
```
|
|
836
|
+
|
|
837
|
+
The commands use the repository that contains the working directory. Pass
|
|
838
|
+
`--repo <path>` when the working directory is outside the project's
|
|
839
|
+
repositories and the project has more than one. They always act for the thread
|
|
840
|
+
that runs them.
|
|
841
|
+
|
|
842
|
+
`--triggers` takes a comma-separated list of `failed-checks`, `bot-reviews`,
|
|
843
|
+
`human-reviews`, and `conflicts`. Without it, `enable` turns on all four for a
|
|
844
|
+
pull request that has no follow-ups and keeps the current triggers otherwise.
|
|
845
|
+
`enable` also resumes paused follow-ups that this thread handles.
|
|
846
|
+
|
|
847
|
+
When another thread handles the pull request's follow-ups, `enable` returns
|
|
848
|
+
`held_by_other_thread` with that thread's title and changes nothing. Add
|
|
849
|
+
`--take-over` only when the user asks to move follow-ups to this thread. When
|
|
850
|
+
the other thread is no longer available because it was archived or moved to
|
|
851
|
+
another devbox, `enable` moves follow-ups to this thread without
|
|
852
|
+
`--take-over` and names the previous thread. Messages already queued for the
|
|
853
|
+
previous thread still run there.
|
|
854
|
+
|
|
855
|
+
`disable` turns off follow-ups that this thread handles. It can't turn off
|
|
856
|
+
another thread's follow-ups.
|
|
857
|
+
|
|
858
|
+
Turn follow-ups on after opening a pull request meant for review, or when you
|
|
859
|
+
want to hear about its CI results, unless `gh pr create` reported that they are
|
|
860
|
+
already on. Leave them off for throwaway or draft-only experiments unless the
|
|
861
|
+
user asks. If you keep getting follow-ups you can't resolve or that aren't
|
|
862
|
+
worth acting on, turn them off and tell the user why.
|
|
863
|
+
|
|
864
|
+
Errors use these codes: `repo_required`, `no_pull_request`, `pr_closed`,
|
|
865
|
+
`github_app_required`, `github_cli_unavailable`, `held_by_other_thread`,
|
|
866
|
+
`thread_context_unavailable`, and `daemon_update_required`. `holder_changed`,
|
|
867
|
+
`repo_changed`, and `service_unavailable` are retryable; run `status` before
|
|
868
|
+
trying again.
|
|
869
|
+
|
|
798
870
|
## Inline Visuals
|
|
799
871
|
|
|
800
872
|
A managed Codex or Claude agent can publish a self-contained interactive HTML
|
|
@@ -1346,10 +1418,30 @@ enforce idle admission. Sleeping recipients may wake before checking. This
|
|
|
1346
1418
|
mode requires an updated recipient service; `unsupported_capability` means
|
|
1347
1419
|
the recipient cannot enforce it and the message was not delivered.
|
|
1348
1420
|
|
|
1421
|
+
Attach local files when the recipient needs material beyond a short message:
|
|
1422
|
+
|
|
1423
|
+
```bash
|
|
1424
|
+
dvb-onbox threads message --to <thread-id> \
|
|
1425
|
+
--message "Read the attached handoff before continuing." \
|
|
1426
|
+
--attach /tmp/handoff.json --idempotency-key handoff-1 --json
|
|
1427
|
+
```
|
|
1428
|
+
|
|
1429
|
+
File attachments work with your own agent threads in this project. Repeat
|
|
1430
|
+
`--attach` for additional files. In a batch item, use
|
|
1431
|
+
`"attachments": ["/tmp/handoff.json"]`. Attach up to ten regular files totaling
|
|
1432
|
+
100 MiB per message, including empty or binary files. Paths may be relative
|
|
1433
|
+
to the sender's working directory or absolute. The recipient will receive
|
|
1434
|
+
separate copies in its thread's attachment directory and local file references
|
|
1435
|
+
in the message, even when it runs on another devbox. Images will be attached
|
|
1436
|
+
as files. File contents will not be encoded into message text or publicly
|
|
1437
|
+
shared. If any file cannot be transferred, the message will not be delivered.
|
|
1438
|
+
Attachments cannot be sent to a teammate's thread; send a link they can open
|
|
1439
|
+
instead.
|
|
1440
|
+
|
|
1349
1441
|
Keys reuse the same receipt on the same source machine, including across CLI
|
|
1350
1442
|
invocations. Retrying with the same key and message recovers that outcome
|
|
1351
|
-
without another delivery. Changing the recipient, message, or
|
|
1352
|
-
under that key fails with `idempotency_key_reused`. Use a new key for each new
|
|
1443
|
+
without another delivery. Changing the recipient, message, attachments, or
|
|
1444
|
+
idle-only policy under that key fails with `idempotency_key_reused`. Use a new key for each new
|
|
1353
1445
|
logical nudge or cadence pass, including when reconsidering a busy skip.
|
|
1354
1446
|
|
|
1355
1447
|
`--to` takes a boxes.dev thread ID, such as one named in a received message,
|
|
@@ -1359,8 +1451,8 @@ from thread list or search results are accepted in `--to` and batch `to`.
|
|
|
1359
1451
|
Use this command rather than a
|
|
1360
1452
|
built-in agent messaging tool such as Claude's SendMessage, which cannot
|
|
1361
1453
|
address boxes.dev thread IDs or reach Codex and other devboxes, and may hold a
|
|
1362
|
-
message until the recipient's user approves it.
|
|
1363
|
-
|
|
1454
|
+
message until the recipient's user approves it. Message text is limited to 4 KiB;
|
|
1455
|
+
attach files or point to threads for longer material. Only a managed agent thread can send,
|
|
1364
1456
|
so the recipient can reply. Sending will start an idle agent and wake the
|
|
1365
1457
|
recipient's devbox if it's asleep, which uses compute and model usage. An
|
|
1366
1458
|
active agent reads the message at its next opportunity in its current work.
|
|
@@ -1368,10 +1460,13 @@ active agent reads the message at its next opportunity in its current work.
|
|
|
1368
1460
|
The recipient's Codex or Claude receives the message from another agent, not
|
|
1369
1461
|
as user input. The message names the sender's thread and the command for
|
|
1370
1462
|
replying. It cannot answer a pending permission prompt or question for the
|
|
1371
|
-
user.
|
|
1372
|
-
|
|
1373
|
-
|
|
1374
|
-
|
|
1463
|
+
user. In the recipient's thread, each message starts collapsed with a message
|
|
1464
|
+
icon, a source label such as **Message from Codex**, and a short excerpt.
|
|
1465
|
+
Select the row to read the full message and use **View thread** to open the
|
|
1466
|
+
sender's thread. Select the header again to collapse it. After work finishes,
|
|
1467
|
+
peer messages also collapse with tool activity under **Worked for…**. Expand
|
|
1468
|
+
that activity, then select a message to read it; messages from the user and
|
|
1469
|
+
the agent's final answer stay visible.
|
|
1375
1470
|
|
|
1376
1471
|
A successful result means the recipient accepted the message; it does not mean
|
|
1377
1472
|
the agent has read, acted on, or answered it. Replies arrive later as messages
|
|
@@ -1468,7 +1563,10 @@ agents on this box created, see
|
|
|
1468
1563
|
[Destroy And Archive Created Devboxes](#destroy-and-archive-created-devboxes).
|
|
1469
1564
|
|
|
1470
1565
|
Destruction permanently deletes the devbox's files and retains its thread
|
|
1471
|
-
history.
|
|
1566
|
+
history. It also stops automatic pull request follow-ups that the devbox's
|
|
1567
|
+
threads handle (see [Pull Request Follow-ups](#pull-request-follow-ups)), so
|
|
1568
|
+
mention them to the user when their pull request is still open. Run this only
|
|
1569
|
+
when the user's task calls for destroying the devbox.
|
|
1472
1570
|
When the user asks for teardown, generally proceed, ignoring files, branches
|
|
1473
1571
|
and stashes inherited unchanged from the Template box. If significant work
|
|
1474
1572
|
created on this devbox is worth keeping and has not been committed and pushed
|
|
@@ -1525,7 +1623,8 @@ created by restoring an archived thread, and Template boxes return
|
|
|
1525
1623
|
Run this only when the user's task calls for it, such as after the devbox's
|
|
1526
1624
|
work has merged or has otherwise been preserved outside the machine.
|
|
1527
1625
|
Destruction permanently deletes the devbox's files and retains its thread
|
|
1528
|
-
history.
|
|
1626
|
+
history. It also stops automatic pull request follow-ups that the devbox's
|
|
1627
|
+
threads handle until another thread turns them on.
|
|
1529
1628
|
|
|
1530
1629
|
The request waits for every agent and queued message on that devbox to finish,
|
|
1531
1630
|
and boxes.dev wakes a sleeping devbox to archive it. New work submitted to the
|
|
@@ -1846,6 +1945,12 @@ a new Team Template based on that project. This path uses clean GitHub clones;
|
|
|
1846
1945
|
it never snapshots the source box or copies its home directory, credentials,
|
|
1847
1946
|
environment values, uncommitted files, or unrelated machine state.
|
|
1848
1947
|
|
|
1948
|
+
Admins can also start this workflow in the desktop app from **New Team
|
|
1949
|
+
Template** → **Create from an existing project**. That opens a draft on the
|
|
1950
|
+
source Template box with the prompt `Create a Team Template from this project`
|
|
1951
|
+
for the user to send, and turns on `create-team-templates` for that box, so
|
|
1952
|
+
`inspect` will report the permission as granted. Still review the spec with the user before creation.
|
|
1953
|
+
|
|
1849
1954
|
Every source repository must have a GitHub remote. Before creation, the admin's
|
|
1850
1955
|
boxes.dev GitHub connection and GitHub App installation must cover each chosen
|
|
1851
1956
|
repository with write access. Start by reading the complete source and access
|