@boxes-dev/dvb-runtime 1.0.1075 → 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.
@@ -565,6 +565,17 @@ that run used, or `null` for older runs that didn't record them. A run's
565
565
  open the thread link to see the result. Schedule times include the local time
566
566
  and UTC offset.
567
567
 
568
+ The listing includes saved archived runs automatically. Manual devbox archival
569
+ preserves the run ID and recorded settings. In JSON, `coverage.scope` is
570
+ `retained_runs`, `oldestRetainedRunNumber` identifies the oldest saved run,
571
+ and `lastIssuedRunNumber` identifies the last assigned run number. The oldest
572
+ number is null when no runs are saved or the oldest run predates numbering.
573
+ The last issued number is zero when none have been assigned and null when a
574
+ legacy counter is unavailable. `nextCursor: null` means there are no more
575
+ retained records, not that every historical run is still saved. Explicit
576
+ deletion can leave gaps, and these range endpoints do not prove that
577
+ intermediate runs are present.
578
+
568
579
  After `create` times out or fails without a clear result, run `list` before
569
580
  trying again so you don't create a duplicate.
570
581
 
@@ -594,6 +605,8 @@ Template maintenance uses one script and one complete GitHub watch set:
594
605
 
595
606
  ```bash
596
607
  dvb-onbox project maintenance get --json
608
+ dvb-onbox project maintenance runs --json
609
+ dvb-onbox project maintenance logs --run <run-id> --json
597
610
  dvb-onbox project maintenance apply \
598
611
  --script-file /home/boxes/<file> \
599
612
  --timeout-seconds <1-480> \
@@ -617,6 +630,16 @@ grandfathered read-only watches remain unchanged. Maintenance reads and writes
617
630
  on an ordinary Template box require **Edit template maintenance**, a separate
618
631
  permission that covers the script and GitHub watches together.
619
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
+
620
643
  The same maintenance commands work in a Team Template's current editing
621
644
  session. They update that Team Template's shared maintenance script and watches
622
645
  and require the editing session's owner to remain a team admin. Use repository
@@ -784,6 +807,66 @@ When a user-required title change returns `title_editing_disabled`, request
784
807
  only `update-thread-titles` through the Agent permissions command above. Do not
785
808
  request it merely to perform an optional rename after unrelated work.
786
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
+
787
870
  ## Inline Visuals
788
871
 
789
872
  A managed Codex or Claude agent can publish a self-contained interactive HTML
@@ -1229,6 +1312,37 @@ They may lag active work and shorten long messages. They do not wake boxes,
1229
1312
  mark threads read, claim links, or expose full tool logs. Without `--scope`,
1230
1313
  the existing `list` and `read` commands still select delegated children only.
1231
1314
 
1315
+ For original visible message text, add `--full --json`:
1316
+
1317
+ ```bash
1318
+ dvb-onbox threads read --scope user --thread <thread-id> --full --json
1319
+ ```
1320
+
1321
+ Full mode preserves text whitespace, retrieves stored large-message bodies,
1322
+ and includes human attachment prompts and slash commands under the same read
1323
+ permissions. It exports attachment descriptors, with binary bodies excluded.
1324
+ Start without a preview or search cursor; full mode has its own cursors.
1325
+ Pass its `transcript.pagination.nextCursor` as `--cursor` with the same full
1326
+ flags until it is null, including after an empty page. Each page examines one
1327
+ source message; `--turns` bounds the turn window examined.
1328
+
1329
+ Messages include `source.fileIdentityKey`, `source.lineId`, `source.seq`,
1330
+ `source.textOffset`, and `source.textLength`. A long message continues across
1331
+ pages: group parts by file identity and line ID, sort by text offset, and join
1332
+ contiguous parts until their combined length equals text length. Offsets and
1333
+ lengths count JavaScript string positions. `textComplete` means the returned
1334
+ text contains the whole message; `reason: continued` identifies a partial
1335
+ message. Other non-null reasons report unavailable or unsupported content.
1336
+
1337
+ Check `transcript.completeness` on every page. Preview mode reports omitted,
1338
+ shortened, and unavailable message counts, independently of older-page
1339
+ pagination. `hasMoreBefore: false` does not by itself prove content completeness.
1340
+ Full mode also reports `syncedThroughSeq`, `projectionThroughSeq`, and
1341
+ `missingTurnCount`, with `binaryAttachmentsIncluded: false`. A nonzero missing
1342
+ turn count identifies a gap in stored projected history; stored history can still lag a running
1343
+ agent. Older local services will report an update requirement when full mode
1344
+ is requested.
1345
+
1232
1346
  To find your own threads by title or by what was said in them, search
1233
1347
  instead of listing:
1234
1348
 
@@ -1304,19 +1418,41 @@ enforce idle admission. Sleeping recipients may wake before checking. This
1304
1418
  mode requires an updated recipient service; `unsupported_capability` means
1305
1419
  the recipient cannot enforce it and the message was not delivered.
1306
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
+
1307
1441
  Keys reuse the same receipt on the same source machine, including across CLI
1308
1442
  invocations. Retrying with the same key and message recovers that outcome
1309
- without another delivery. Changing the recipient, message, or idle-only policy
1310
- 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
1311
1445
  logical nudge or cadence pass, including when reconsidering a busy skip.
1312
1446
 
1313
1447
  `--to` takes a boxes.dev thread ID, such as one named in a received message,
1314
1448
  one returned by `dvb-onbox threads start`, or one from
1315
- `dvb-onbox threads list --scope project`. Use this command rather than a
1449
+ `dvb-onbox threads list --scope project`. Both `id` and `publicId` (`thr_…`)
1450
+ from thread list or search results are accepted in `--to` and batch `to`.
1451
+ Use this command rather than a
1316
1452
  built-in agent messaging tool such as Claude's SendMessage, which cannot
1317
1453
  address boxes.dev thread IDs or reach Codex and other devboxes, and may hold a
1318
- message until the recipient's user approves it. Messages are limited to 4 KiB;
1319
- point to files or threads for longer material. Only a managed agent thread can send,
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,
1320
1456
  so the recipient can reply. Sending will start an idle agent and wake the
1321
1457
  recipient's devbox if it's asleep, which uses compute and model usage. An
1322
1458
  active agent reads the message at its next opportunity in its current work.
@@ -1324,10 +1460,13 @@ active agent reads the message at its next opportunity in its current work.
1324
1460
  The recipient's Codex or Claude receives the message from another agent, not
1325
1461
  as user input. The message names the sender's thread and the command for
1326
1462
  replying. It cannot answer a pending permission prompt or question for the
1327
- user. The user sees it in the recipient's thread as a message from the sending
1328
- agent, linked to the sender's thread. After work finishes, peer messages
1329
- collapse with tool activity under **Worked for…**. Expand it to read those
1330
- messages; messages from the user and the agent's final answer stay visible.
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.
1331
1470
 
1332
1471
  A successful result means the recipient accepted the message; it does not mean
1333
1472
  the agent has read, acted on, or answered it. Replies arrive later as messages
@@ -1424,7 +1563,10 @@ agents on this box created, see
1424
1563
  [Destroy And Archive Created Devboxes](#destroy-and-archive-created-devboxes).
1425
1564
 
1426
1565
  Destruction permanently deletes the devbox's files and retains its thread
1427
- history. Run this only when the user's task calls for destroying the devbox.
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.
1428
1570
  When the user asks for teardown, generally proceed, ignoring files, branches
1429
1571
  and stashes inherited unchanged from the Template box. If significant work
1430
1572
  created on this devbox is worth keeping and has not been committed and pushed
@@ -1481,7 +1623,8 @@ created by restoring an archived thread, and Template boxes return
1481
1623
  Run this only when the user's task calls for it, such as after the devbox's
1482
1624
  work has merged or has otherwise been preserved outside the machine.
1483
1625
  Destruction permanently deletes the devbox's files and retains its thread
1484
- history.
1626
+ history. It also stops automatic pull request follow-ups that the devbox's
1627
+ threads handle until another thread turns them on.
1485
1628
 
1486
1629
  The request waits for every agent and queued message on that devbox to finish,
1487
1630
  and boxes.dev wakes a sleeping devbox to archive it. New work submitted to the
@@ -1802,6 +1945,12 @@ a new Team Template based on that project. This path uses clean GitHub clones;
1802
1945
  it never snapshots the source box or copies its home directory, credentials,
1803
1946
  environment values, uncommitted files, or unrelated machine state.
1804
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
+
1805
1954
  Every source repository must have a GitHub remote. Before creation, the admin's
1806
1955
  boxes.dev GitHub connection and GitHub App installation must cover each chosen
1807
1956
  repository with write access. Start by reading the complete source and access
@@ -47,10 +47,11 @@ which has three steps:
47
47
  once and expires within 30 minutes. The textbox automatically regenerates
48
48
  the code after use and before it expires, so the user can copy a fresh
49
49
  prompt if an earlier attempt fails.
50
- 3. **Get the desktop app**: the agent gives the user the Mac app link once
51
- setup starts, and **Download for Mac now** is available right away. On
52
- Windows and Linux browsers that boxes.dev can confidently identify, this
53
- step says the desktop app is Mac-only and links to the mobile app instead.
50
+ 3. **Get the desktop app**: the agent gives the user the desktop app link
51
+ once setup starts, and **Download for Mac now** is available right away.
52
+ Linux browsers see **Download for Linux now** instead. On Windows browsers
53
+ that boxes.dev can confidently identify, this step says the desktop app is
54
+ only available for Mac and Linux and links to the mobile app instead.
54
55
 
55
56
  On a phone, the second step becomes **Continue on your computer**, with
56
57
  actions to email, copy, or share a link to the page, and the desktop step is
@@ -380,12 +381,13 @@ keeps waiting; it can stop the command and check setup status.
380
381
  one connected coding agent.
381
382
 
382
383
  Once the setup thread starts on the Template box, `dvb agent-init run` tells
383
- the agent where the user can follow it. On a Mac with the desktop app
384
- installed, the agent offers to open it with `dvb agent-init open-desktop`,
385
- which opens the Template box on the setup thread. On a Mac without the app,
386
- the agent gives the download link, and on other computers or over SSH, it
387
- points to the mobile app. When setup finishes on a Mac with the desktop app
388
- installed, `dvb agent-init` opens the app on the setup thread, where the user
384
+ the agent where the user can follow it. On a Mac or Linux computer with the
385
+ desktop app installed, the agent offers to open it with
386
+ `dvb agent-init open-desktop`, which opens the Template box on the setup
387
+ thread. Without the app, the agent gives the download link for that computer
388
+ (`https://boxes.dev/mac` or `https://boxes.dev/linux`), and on other
389
+ computers or over SSH, it points to the mobile app. When setup finishes on a
390
+ Mac or Linux computer with the desktop app installed, `dvb agent-init` opens the app on the setup thread, where the user
389
391
  can read the setup agent's summary. Otherwise, the agent lists the same
390
392
  choices. Either way, the agent also mentions `dvb agents <project>`, which
391
393
  opens the Template box's agent threads in the terminal (`--workspace` keeps
@@ -432,9 +434,10 @@ desktop app, or switch from the mobile app. Claude API keys are unchanged.
432
434
 
433
435
  Once a claude.ai login is saved, Configure agents and mobile Agent accounts
434
436
  show **Allow claude.ai connectors**, which is on by default. Turning it off
435
- keeps claude.ai connectors out of new Claude sessions, including automation
436
- and Slack runs that use the account; synced skills and plugins still load.
437
- Sessions that are already running keep their connectors until they restart.
437
+ keeps claude.ai connectors out of Claude the next time it starts, including in
438
+ automation and Slack runs that use the account; synced skills and plugins
439
+ still load. A Claude process that is already running keeps its connectors
440
+ until it restarts.
438
441
 
439
442
  Each saved subscription row in desktop Configure agents shows a small bar for
440
443
  the weekly limit's remaining usage. A 5-hour bar appears below it only when
@@ -892,7 +895,14 @@ for those repos. Setup verifies signed commits locally on the Template box, but
892
895
  Git host "Verified" badges still require the public signing key to be registered
893
896
  with the Git host.
894
897
 
895
- In agent-driven setup, `run` prints the public signing key and the host's
898
+ In agent-driven setup, an explicit `gitSigning.mode: create` can also set up
899
+ signing when no selected repository signs locally. It uses local Git
900
+ `user.name` and `user.email`, with OpenPGP by default or SSH when `gpg.format`
901
+ is `ssh`; it does not require an existing signing key or change local signing
902
+ settings. OpenPGP creation requires GnuPG on the user's computer. Projects that
903
+ mix signed and unsigned repositories keep their existing signing scope.
904
+
905
+ `run` prints the public signing key and the host's
896
906
  registration instructions. Retrieve them again with `dvb agent-init status`,
897
907
  including after setup finishes. Private keys are never printed. Signing
898
908
  identifies the signer of a commit; it does not grant pull or push access.
@@ -114,7 +114,7 @@ receive only Claude's current short-lived access, written where Claude Code
114
114
  reads its own login. A claude.ai login also lets Claude use the connectors the
115
115
  user added on claude.ai, such as Gmail, so an agent on a box can reach those
116
116
  services; **Allow claude.ai connectors** in Configure agents or Agent accounts
117
- turns that off for new sessions.
117
+ turns that off. The change takes effect the next time Claude starts.
118
118
 
119
119
  Agent credentials should be treated like other development credentials. If a
120
120
  user no longer wants an agent credential available in boxes.dev, they should
@@ -26,7 +26,7 @@ channels where the app is available and in 1:1 app DMs.
26
26
  ## Connect Slack
27
27
 
28
28
  Open the desktop workbench's **Integrations** section and choose **Connect**
29
- for Slack. Team admins can also connect Slack from **Team Settings**, or from
29
+ for Slack. Team admins can also connect Slack from **Team settings**, or from
30
30
  the **Account** step of first-run desktop setup when their team has no Slack
31
31
  workspace yet. Slack opens an authorization screen; choose the workspace and
32
32
  allow the app.
@@ -57,7 +57,7 @@ You can link by:
57
57
  identity** on the **Account** page when boxes.dev hasn't seen your Slack
58
58
  account yet;
59
59
  - opening the boxes.dev app DM in Slack and sending `connect`;
60
- - following a connect link sent by a team admin from Team Settings.
60
+ - following a connect link sent by a team admin from Team settings.
61
61
 
62
62
  If boxes.dev cannot match your Slack user, verify your boxes.dev email and try
63
63
  again from Slack.
@@ -330,27 +330,28 @@ output, needs-input, and failed-run events.
330
330
  ## Shared Thread Previews
331
331
 
332
332
  When someone posts a boxes.dev share link (`/t/...`) in Slack, boxes.dev adds
333
- a preview card to the message. The card shows the boxes.dev logo, the thread's
334
- title, its creator, and an **Open in boxes.dev** button that opens the share
335
- link. A thread without a manual or generated title shows **boxes.dev thread**;
336
- the first message never appears on the card, because everyone in the
337
- conversation can see it. boxes.dev updates posted cards when the thread is
338
- renamed; turns don't change the card. Several share links in one message get
339
- compact cards, and Slack previews at most five links per message.
340
-
341
- Selecting the card's title opens its details in Slack. A viewer who has linked
342
- their Slack identity and can open the share sees the card's fields and button
343
- plus the first message, last activity, coding agent, project, devbox, and
344
- shared date. The details show a status only when the thread is **Working**,
345
- **Waiting for input**, **Failed**, **Cold stored**, or **History only**, read
346
- when the panel opens. An unlinked member of the connected workspace is asked to
347
- connect their boxes.dev account. External users, bots, and members linked to
348
- another boxes.dev team see Slack's restricted state. An open details panel
349
- keeps what it loaded until the viewer chooses **Sync data**.
333
+ a preview to the message. The preview shows the thread's title, one message,
334
+ a line with the boxes.dev logo, "boxes.dev", the project, the status, and the
335
+ time of the last message, and an **Open in boxes.dev** button. The title and
336
+ the button open the link as posted. The message is a plain-text excerpt of
337
+ the agent's latest finished reply, or the first message until the agent has
338
+ replied; Slack folds an excerpt longer than four lines behind **Show more**. A
339
+ thread without a manual or generated title shows
340
+ **boxes.dev thread**. The status is **Working**, **Waiting for input**,
341
+ **Failed**, **Cold stored**, or **History only** while one applies, **Done**
342
+ for an idle thread that has a reply, and absent otherwise. Slack shows the
343
+ time relative to now, such as "5 minutes ago".
344
+
345
+ Everyone who can see the Slack message sees the same preview, including
346
+ workspace guests; there is no separate details view. boxes.dev updates posted
347
+ previews when a prompt is sent, a turn starts, finishes, fails, or is
348
+ interrupted, the agent asks for input, or the thread is renamed. Each share
349
+ link in a message gets its own preview, and Slack previews at most five links
350
+ per message.
350
351
 
351
352
  A revoked or private share, a deleted thread, an owner whose account was
352
353
  deleted or who left the team keeping the project, and another team's share all
353
- show **This shared thread isn't available**, and posted cards switch to it
354
+ show **This shared thread isn't available**, and posted previews switch to it
354
355
  within seconds. Previews also appear in DMs, group DMs, and private channels
355
356
  without the app. boxes.dev adds no preview in conversations Slack reports as
356
357
  shared with another organization.
@@ -361,7 +362,7 @@ them. The Slack integration home shows **Update available** and "Reinstall the
361
362
  Slack app to turn on previews for shared thread links." Members instead see
362
363
  that a team admin needs to reinstall it. A team admin needs to choose
363
364
  **Reinstall** there, or **Reinstall Slack** from the Slack actions menu in
364
- **Team Settings**, and approve the request in Slack.
365
+ **Team settings**, and approve the request in Slack.
365
366
 
366
367
  ## Current Limits
367
368
 
@@ -389,7 +390,7 @@ If Slack says your user is not linked, use **Find my Slack account** or send
389
390
 
390
391
  If a channel is not available, add `@boxes.dev` to the channel and run
391
392
  **Check** from **Team connection** on the Slack integration home (or
392
- **Recheck** in Team Settings).
393
+ **Recheck** in Team settings).
393
394
 
394
395
  If a share link gets no preview, confirm the conversation isn't shared with
395
396
  another organization and the Slack connection lists no missing permissions. See [Shared Thread Previews](#shared-thread-previews).
@@ -45,7 +45,7 @@ The setup sequence is:
45
45
 
46
46
  The Tailscale admin returns the Tailnet ID, `tag:boxes-dev`, OAuth client ID,
47
47
  and one-time-displayed OAuth client secret. The boxes.dev team admin enters all
48
- four values from the project's Tailscale integration page or Team Settings.
48
+ four values from the project's Tailscale integration page or Team settings.
49
49
  Both surfaces keep a separate connection form visible beneath four selectable
50
50
  setup tabs, so an admin can move among the detailed Tag, Access, OAuth, and
51
51
  Tailnet ID instructions without losing entered values. boxes.dev validates the
@@ -59,7 +59,7 @@ OAuth credential stays central.
59
59
 
60
60
  The required read scopes let boxes.dev read the tailnet's full device and user
61
61
  directories, access policy, and device posture attributes. Device mutations
62
- and auth-key creation are restricted to the configured tag. Team Settings
62
+ and auth-key creation are restricted to the configured tag. Team settings
63
63
  discloses this access before the connection is saved.
64
64
 
65
65
  ## Who Can Enable It
@@ -51,7 +51,7 @@ a saved version or a project created from it.
51
51
 
52
52
  ### Removing A Team Member
53
53
 
54
- An admin can remove another member from **Team Settings → Members** using the
54
+ An admin can remove another member from **Team settings → Members** using the
55
55
  member's menu. Select a remaining member as the work recipient, then choose
56
56
  **Transfer**, **Delete**, or **Keep** for every project. Transfer preserves the
57
57
  project's work under the recipient and records its original account. Delete
@@ -72,7 +72,7 @@ account can continue using its personal team and will not automatically rejoin
72
72
  the former team through its email domain. Remove its paid seat in Billing and
73
73
  finish pending project operations first. Team Template editing sessions must
74
74
  be saved or discarded before removal. Admins cannot remove themselves.
75
- An interrupted removal remains in Team Settings with progress and a retry
75
+ An interrupted removal remains in Team settings with progress and a retry
76
76
  action; closing its dialog does not cancel it.
77
77
  The dialog counts the remaining records before each start or retry, then
78
78
  shows how many records have moved out of that total. A retry counts only the
@@ -99,13 +99,14 @@ here.
99
99
  The collection and each template's detail page also work in a web browser, so
100
100
  an admin can keep a template open beside the desktop workbench. In the desktop
101
101
  app, **Open in browser** opens the current Team Templates page in the default
102
- browser. On the website, **Team** in the header opens Team Settings, where
102
+ browser. On the website, **Team** in the header opens Team settings, where
103
103
  **Manage Team Templates** opens the collection. A browser can change everything
104
104
  on the detail page except the editing session itself: creating a template,
105
105
  GitHub setup, **Take control**, continuing an editing session, and **Resolve**
106
- all need the desktop app on a Mac. In their place, a browser on a Mac shows
107
- **Open in desktop app**, which opens the same template in the desktop app;
108
- phones, tablets, Windows, and Linux show a note instead.
106
+ all need the desktop app on a Mac or Linux computer. In their place, a
107
+ browser on a Mac or Linux computer shows **Open in desktop app**, which opens
108
+ the same template in the desktop app; phones, tablets, and Windows show a note
109
+ instead.
109
110
 
110
111
  **Project settings** for a project made from a Team Template names that
111
112
  template. A managed project shows the template it uses, and an independent
@@ -116,14 +117,28 @@ detail page.
116
117
  Team members do not see the management submenu. To create a project from a
117
118
  saved template, choose **New project...**, then **Start from a Team Template**.
118
119
 
119
- Admins create a Team Template from this collection. The default flow starts
120
- from GitHub: choose one or several existing repositories, or create a new
121
- repository on GitHub, then review their direct-child paths under
122
- `/home/boxes`. **Start empty** keeps the clean-machine flow available. GitHub
123
- setup uses temporary boxes.dev GitHub App access limited to the selected
124
- repositories while cloning them. It does not require SSH-key registration or a
125
- desktop private-key transfer. An interrupted setup can be continued from the
126
- template's card or detail page.
120
+ Admins create a Team Template from this collection with **New Team
121
+ Template**, which offers two starting points.
122
+
123
+ **Create from an existing project** is the recommended path. It lists the
124
+ admin's unarchived projects whose Template box has finished setup, including
125
+ projects that still need GitHub access; managed projects have no Template box
126
+ and are not listed. Selecting a project opens an ordinary new-thread draft on
127
+ that project's Template box with `Create a Team Template from this project` in
128
+ the composer, using the project's default agent and settings. The admin can
129
+ change the agent, model, and reasoning effort before sending it, and the agent
130
+ doesn't start until it's sent. Opening the draft also turns on the box-wide **Create Team Templates** agent permission
131
+ (`create-team-templates`) for that Template box. The thread then follows **Create a Team Template from
132
+ this project** in [On-box agent tools](onbox-agent-tools.md), so the template
133
+ starts from clean GitHub clones and the admin reviews the spec before creation.
134
+
135
+ **Create from scratch** starts from GitHub: choose one or several existing
136
+ repositories, or create a new repository on GitHub, then review their
137
+ direct-child paths under `/home/boxes`. **Start empty** keeps the
138
+ clean-machine flow available. GitHub setup uses temporary boxes.dev GitHub App
139
+ access limited to the selected repositories while cloning them. It does not
140
+ require SSH-key registration or a desktop private-key transfer. An interrupted
141
+ setup can be continued from the template's card or detail page.
127
142
 
128
143
  If you discard a GitHub-backed editing session before the first save, reopening
129
144
  the template will recreate the originally selected repositories as clean
@@ -131,8 +146,9 @@ clones. Other unsaved files from the discarded session cannot be recovered.
131
146
 
132
147
  The template's name and description can change later, but its machine size is
133
148
  fixed after creation and is inherited by projects made from it. Creating and
134
- preparing the entry does not create a usable saved version: an admin must
135
- inspect the machine and save it first.
149
+ preparing the entry does not create a usable saved version: the machine must be
150
+ inspected and saved first, either by an admin in the editor or by the creating
151
+ agent after the admin asks it to save.
136
152
 
137
153
  Open a template's detail page to inspect and administer it; members start
138
154
  projects from the normal new-project flow instead. The admin page groups
@@ -320,7 +336,7 @@ personal or project connection is ready. Marking one **Recommended** lets the
320
336
  owner choose **Finish without recommendations**. The saved requirement contains
321
337
  no provider credentials, identities, automation settings, or machine state.
322
338
 
323
- Machine size is fixed for the Team Template lineage and is not a Project
339
+ Box size is fixed for the Team Template lineage and is not a Project
324
340
  default. Project creation offers no per-default overrides; members can change
325
341
  the resulting ordinary project afterward.
326
342
 
@@ -86,7 +86,7 @@ settings card.
86
86
  Successful additions and reviews on the Template box automatically create one
87
87
  new Template snapshot. Future devboxes inherit that saved filesystem and repo
88
88
  index; existing devboxes do not change. The completion dialog links to
89
- **Devbox lifecycle → New devbox defaults → Startup Script** in case the new
89
+ **Devbox lifecycle → New devbox defaults → Startup script** in case the new
90
90
  repositories need install or startup commands, but it never changes the script
91
91
  automatically.
92
92
 
@@ -576,7 +576,7 @@ steer at its next available opportunity; a message sent during a final response
576
576
  may get a separate response afterward. Both actions support Claude's existing
577
577
  attachments.
578
578
 
579
- Desktop Settings has a separate **Claude Replies** default. Enter will use
579
+ Desktop Settings has a separate **Claude replies** default. Enter will use
580
580
  that action while Claude is working, and Cmd/Ctrl+Enter will use the alternate
581
581
  action. On mobile, use the **Queue**/**Steer** control beside the composer.
582
582
  An idle thread starts normally with either preference. Once Claude accepts a
@@ -974,7 +974,7 @@ The desktop thread list groups work by devboxes, automations, and, when the
974
974
  project has one, Template-box threads.
975
975
 
976
976
  Thread sections include pinned, recent, and archived chats. Template box pinned
977
- threads can be reordered. Archived chats can be shown or hidden. Template box
977
+ threads can be reordered. Archived threads can be shown or hidden. Template box
978
978
  threads may also support moving older archived transcripts to cold storage.
979
979
 
980
980
  Rows show status indicators for draft, starting, active, unread, idle, archived,
@@ -469,7 +469,7 @@ the same block again.
469
469
 
470
470
  ## Slack Problems
471
471
 
472
- For Slack-triggered automations, check Team Settings > Slack.
472
+ For Slack-triggered automations, check Team settings > Slack.
473
473
 
474
474
  Common fixes:
475
475
 
@@ -478,7 +478,7 @@ Common fixes:
478
478
  reinstall Slack.
479
479
  - If known users or channels are stale, use the check/verification action.
480
480
  - If a user cannot start or receive Slack-linked work, link that user's Slack
481
- identity from Account settings or send a connect link from Team Settings.
481
+ identity from Account settings or send a connect link from Team settings.
482
482
  - If attachments are missing, confirm the bot can access the channel and the
483
483
  file is still available in Slack.
484
484
  - If several Slack mentions start at once and some fail to launch, check awake
@@ -489,7 +489,7 @@ authorization, so a team admin should do it intentionally.
489
489
 
490
490
  ## Linear Problems
491
491
 
492
- For Linear assignment-triggered automations, check Team Settings > Linear.
492
+ For Linear assignment-triggered automations, check Team settings > Linear.
493
493
 
494
494
  Common fixes:
495
495
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@boxes-dev/dvb-runtime",
3
- "version": "1.0.1075",
3
+ "version": "1.0.1077",
4
4
  "description": "Runtime for the boxes.dev CLI. Install @boxes-dev/dvb to use the CLI.",
5
5
  "homepage": "https://boxes.dev",
6
6
  "type": "module",
@@ -77,5 +77,5 @@
77
77
  "e2b": "^2.18.0",
78
78
  "ink-testing-library": "^4.0.0"
79
79
  },
80
- "devboxReleasedAt": "2026-10-15T02:35:58Z"
80
+ "devboxReleasedAt": "2026-10-15T19:24:00Z"
81
81
  }