@boxes-dev/dvb-runtime 1.0.1076 → 1.0.1078
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 +1997 -488
- package/dist/bin/dvbd.mjs +4 -4
- package/dist/product-docs/references/agent-tools.md +25 -0
- package/dist/product-docs/references/automations.md +32 -4
- package/dist/product-docs/references/cli.md +48 -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 +119 -11
- 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.1078";
|
|
64679
|
+
const rawGitSha = "8c516f16149b71ba8dc1fd9ba16fda4b614ce8bf";
|
|
64680
|
+
const rawSentryRelease = "boxes-dev-dvb@1.0.1078+8c516f16149b71ba8dc1fd9ba16fda4b614ce8bf";
|
|
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.1078";
|
|
66898
66898
|
return trimVersion(raw);
|
|
66899
66899
|
};
|
|
66900
66900
|
readNearestPackageMetadata = (basePath) => {
|
|
@@ -330,6 +330,31 @@ thread also marks it read, but a pending request for input stays visible until
|
|
|
330
330
|
it is answered. `threads list` reports each thread's `notificationsMuted`
|
|
331
331
|
value.
|
|
332
332
|
|
|
333
|
+
Archive or unarchive an owned thread with an explicit command:
|
|
334
|
+
|
|
335
|
+
```bash
|
|
336
|
+
dvb threads archive --thread <client-thread-id> --json
|
|
337
|
+
dvb threads unarchive --thread <client-thread-id> --json
|
|
338
|
+
```
|
|
339
|
+
|
|
340
|
+
Archive preserves the history and removes the thread from the active list.
|
|
341
|
+
The result contains `clientThreadId`, `archived`, and `changed`; repeating a
|
|
342
|
+
command returns `changed: false` when its requested state is already set.
|
|
343
|
+
Codex archive updates its saved session and may wake the machine. Claude
|
|
344
|
+
archive changes shared metadata without waking it.
|
|
345
|
+
|
|
346
|
+
On a shared devbox, keep its anchor thread and archive the secondary task
|
|
347
|
+
threads. The first thread started on a previously threadless devbox becomes
|
|
348
|
+
its anchor and cannot be archived separately. These commands also support
|
|
349
|
+
threads on the Template box. Restore cold threads in the desktop or mobile
|
|
350
|
+
app before unarchiving them; history-only threads cannot be restored.
|
|
351
|
+
|
|
352
|
+
For a script that cleans up successful tasks, retain each task's result and
|
|
353
|
+
check `threads wait`'s `data.status` for `completed` before archiving. A
|
|
354
|
+
successful command exit or `ok: true` can also describe needs-input, failure,
|
|
355
|
+
timeout, or idle. Starting a thread only accepts its startup; an idle
|
|
356
|
+
observation during startup does not establish completion.
|
|
357
|
+
|
|
333
358
|
## Lifecycle Mutations And Cleanup
|
|
334
359
|
|
|
335
360
|
Use exact project and target identifiers:
|
|
@@ -209,11 +209,39 @@ The creating run retains cleanup ownership; existing cleanup preserves devboxes
|
|
|
209
209
|
with additional durable threads. The sidebar groups shared-devbox threads once,
|
|
210
210
|
while run history keeps each workflow separately.
|
|
211
211
|
|
|
212
|
+
To send a follow-up to a standing conversation, use its boxes.dev thread ID
|
|
213
|
+
(the `clientThreadId` returned by the API, or the ID shown by `dvb threads list`):
|
|
214
|
+
|
|
215
|
+
```json
|
|
216
|
+
{
|
|
217
|
+
"prompt": "Add reviewing the forwarded invoice to my to-do list.",
|
|
218
|
+
"target": { "kind": "existing_thread", "threadId": "<threadId>" }
|
|
219
|
+
}
|
|
220
|
+
```
|
|
221
|
+
|
|
222
|
+
The thread must belong to you and to the automation's project; it need not have
|
|
223
|
+
been created by that automation. An idle agent will start the prompt, and a busy
|
|
224
|
+
agent will queue it after its current turn. The thread will keep its conversation,
|
|
225
|
+
title, agent settings, placement, and notification behavior. Omit `threadTitle`
|
|
226
|
+
and `execution` for this target. Omit `prompt` to send the saved automation prompt.
|
|
227
|
+
The automation's devbox cleanup and Slack output destinations do not apply to
|
|
228
|
+
these follow-ups.
|
|
229
|
+
A sleeping target's box will wake if capacity is available. An awake target
|
|
230
|
+
needs no additional awake slot.
|
|
231
|
+
|
|
232
|
+
Missing, archived, deleted, history-only, or otherwise unavailable threads return
|
|
233
|
+
`409 thread_unavailable`. A target that becomes unavailable after acceptance
|
|
234
|
+
can cause delivery to fail; inspect the run's status. This option creates a run
|
|
235
|
+
record but no thread or devbox. The response's `followUp.disposition` will become
|
|
236
|
+
`started` or `queued` when the run reaches `thread_ready`. It does not report
|
|
237
|
+
when the agent finishes. Retry an uncertain request with the same idempotency
|
|
238
|
+
key and body to avoid sending the prompt twice.
|
|
239
|
+
|
|
212
240
|
An accepted request returns `202`, the run id, a status URL, nullable `devboxId`, and the effective
|
|
213
241
|
thread title and agent controls without echoing the prompt. GET requests to the
|
|
214
242
|
status URL require the same Bearer secret and report launch progress.
|
|
215
|
-
`thread_ready` means the
|
|
216
|
-
|
|
243
|
+
`thread_ready` means the new thread exists, or the existing-thread follow-up
|
|
244
|
+
was accepted as started or queued; it does not mean the agent turn has finished. A request may be
|
|
217
245
|
rejected if the automation is still a draft, paused, errored, or cannot create a
|
|
218
246
|
devbox because the awake devbox limit is reached. Independent requests can start
|
|
219
247
|
runs in parallel; use `Idempotency-Key` to make retries reuse the original run.
|
|
@@ -233,8 +261,8 @@ Capacity settings do not override billing limits or unavailable runtime state.
|
|
|
233
261
|
They only help when the blocker is the awake devbox concurrency limit and an
|
|
234
262
|
idle devbox can be slept.
|
|
235
263
|
|
|
236
|
-
An API request targeting an awake devbox needs no additional
|
|
237
|
-
Sleeping targets wake if capacity is available. The sleep-idle option applies only
|
|
264
|
+
An `existing_devbox` API request targeting an awake devbox needs no additional
|
|
265
|
+
awake slot. Sleeping targets wake if capacity is available. The sleep-idle option applies only
|
|
238
266
|
to new-devbox requests; a wake blocked by capacity produces a failed run with
|
|
239
267
|
`startup_active_fork_limit_reached` at its status URL.
|
|
240
268
|
|
|
@@ -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,52 @@ 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
|
+
|
|
193
|
+
## Agent Permissions
|
|
194
|
+
|
|
195
|
+
The same Agent permissions shown in a desktop thread header, the mobile app,
|
|
196
|
+
and Project settings are available from the terminal. Choose one box by alias
|
|
197
|
+
or the project's shared setting:
|
|
198
|
+
|
|
199
|
+
```bash
|
|
200
|
+
dvb permissions get --box <box>
|
|
201
|
+
dvb permissions get --project <project>
|
|
202
|
+
dvb permissions set message-agents on --project <project>
|
|
203
|
+
dvb permissions set folder-access move --box <box>
|
|
204
|
+
```
|
|
205
|
+
|
|
206
|
+
`set` takes a permission name from `get` and a value: `on` or `off` for
|
|
207
|
+
switches, `none`, `move`, or `create` for `folder-access`, and `none`,
|
|
208
|
+
`project`, `user`, `shared`, or `team` for `read-threads`. A box change applies
|
|
209
|
+
only to that box, while a project change applies to existing and future
|
|
210
|
+
devboxes except those configured separately. Template-box-only permissions such as
|
|
211
|
+
`create-team-templates` are rejected for a devbox or a project. Lifecycle and
|
|
212
|
+
maintenance rows appear only while the Template box is running. Turning on a
|
|
213
|
+
permission that an agent is waiting for completes its request.
|
|
214
|
+
|
|
215
|
+
When an agent asks for a permission with `dvb-onbox permissions request`, list
|
|
216
|
+
and answer the request from the terminal:
|
|
217
|
+
|
|
218
|
+
```bash
|
|
219
|
+
dvb permissions requests
|
|
220
|
+
dvb permissions allow <request-id>
|
|
221
|
+
dvb permissions allow <request-id> --project
|
|
222
|
+
dvb permissions deny <request-id>
|
|
223
|
+
```
|
|
224
|
+
|
|
225
|
+
`requests` shows each pending request's question, the box and thread it came
|
|
226
|
+
from, and minutes until it expires. `allow` matches **Allow**, `--project`
|
|
227
|
+
matches **Always allow for project**, and `deny` matches **Deny**. Requests
|
|
228
|
+
for 3-hour thread access, such as `edit-project-settings`, can only be allowed
|
|
229
|
+
for their thread. A request that expired or was already answered elsewhere
|
|
230
|
+
reports that it is no longer pending. Add `--json` for structured output.
|
|
231
|
+
|
|
184
232
|
## Open A Terminal
|
|
185
233
|
|
|
186
234
|
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.
|