@boxes-dev/dvb-runtime 1.0.1115 → 1.0.1117

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.
@@ -113,10 +113,11 @@ If a team member is not a team admin, billing controls usually show status and
113
113
  tell the member to contact a team admin.
114
114
 
115
115
  New teams that sign up at boxes.dev/conductor will receive one month of Pro
116
- free, and new teams that sign up at boxes.dev/alien will receive three months.
117
- The account that creates the team will get the first Pro seat, including 300
118
- box-hours each month. Extra usage will require prepaid credits. No card is
119
- required for the offer. Pro will end when the offer does unless a team admin
116
+ free, and new teams that sign up at boxes.dev/alien or boxes.dev/launch-yc
117
+ will receive three months. The account that creates the team will get the
118
+ first Pro seat, including 300 box-hours each month. Extra usage will require
119
+ prepaid credits. Only boxes.dev/launch-yc asks for a card, which is charged
120
+ only if the team keeps Pro. Pro will end when the offer does unless a team admin
120
121
  chooses **Keep plan** in Billing; continuing will use the normal Pro price.
121
122
  The offer does not replace an existing account's or team's billing.
122
123
 
@@ -10,13 +10,13 @@ box.
10
10
  The workbench has a few persistent areas:
11
11
 
12
12
  - The top bar is split at the left pane's edge. The left pane's own top area
13
- shows the project selector, paired Back and Forward buttons, and a crosshair
13
+ shows the sidebar toggle, paired Back and Forward buttons, and a crosshair
14
14
  button. Back and Forward retrace workbench
15
15
  selections, so an integration or automation detour can return to the thread
16
16
  you were viewing at the reply you were reading. If you were following the
17
17
  latest output, you return to the bottom. Each arrow is disabled when there
18
18
  is nowhere to go in that direction. Both arrows are hidden when the left
19
- pane is too narrow to fit them beside a readable project name, which can
19
+ pane's titlebar is too narrow to fit the controls, which can
20
20
  happen at narrow widths once the app is zoomed out; **Cmd+[** and **Cmd+]**
21
21
  still work. The crosshair button scrolls the thread
22
22
  list to the selected thread, first expanding Devboxes or Project and the
@@ -31,12 +31,13 @@ The workbench has a few persistent areas:
31
31
  If the app loses its connection, an Offline or Reconnecting badge appears
32
32
  beside the pane control and clears on its own once boxes.dev is reachable
33
33
  again.
34
- - The left pane starts with Devboxes, with thread search immediately left of
35
- its **New thread** header button,
36
- followed by Automations and Project. Expand Project for Integrations,
34
+ - The left pane starts with the project selector, Project settings,
35
+ and thread search. Below them, **New thread**, **New automation**,
36
+ **Integrations**, and **Coordinator** when available open their respective
37
+ surfaces. Devboxes, Automations, and Project follow. Expand Project for
37
38
  Project URLs, Public links when active, sharing, and the Template box when
38
- the project has one. The gear on the Project header opens Project settings,
39
- including while the section is collapsed. Tool rows open list pages in the
39
+ the project has one. Project settings stays beside the project selector,
40
+ including while the Project section is collapsed. Tool rows open list pages in the
40
41
  detail pane; choose an integration or Project URL to open its settings.
41
42
  Shared with me lists saved teammate conversations from every project as
42
43
  selectable nested rows. Its chevron collapses the threads; its heading
@@ -44,7 +45,12 @@ The workbench has a few persistent areas:
44
45
  Shared by me expands this project's shares and access requests. Sharing
45
46
  rows appear when they have items. Collapsed Project and Template box controls
46
47
  retain cues for activity, unread updates, or attention in their contents.
47
- Your account identity, usage icon, and Help button stay pinned at the bottom.
48
+ The sidebar scrolls, with the project selector and New thread staying
49
+ visible at the top. Your avatar, first name and team name, usage icon, and Help button
50
+ stay fixed at the bottom.
51
+ The team name appears beside your first name in a lighter color. If your
52
+ profile has no name, your account label appears instead. Click the
53
+ avatar or label to open account settings and account switching.
48
54
  Hover over or click the usage icon just left of Help for billing usage details.
49
55
  Once you've sent messages in three threads (not counting project setup
50
56
  threads), a **Code on the go!** banner appears above your account if you
@@ -166,7 +172,7 @@ Threads:
166
172
  Panes:
167
173
 
168
174
  - Show or hide the left sidebar: **Cmd+B** (Ctrl+Shift+B). Press it again
169
- to reopen the sidebar, or use the sidebar button beside the project selector.
175
+ to reopen the sidebar, or use the sidebar button beside Back and Forward.
170
176
  The open conversation stays in place, and the project remembers the sidebar's
171
177
  visibility and width on this computer.
172
178
  - Toggle the Terminal / Files / Git-Review pane: **Cmd+L** / **Cmd+K** /
@@ -242,8 +248,9 @@ row to return it to the default.
242
248
 
243
249
  ## Project Selector
244
250
 
245
- Use the project selector in the titlebar to switch between projects on the same
246
- desktop app account. Threads and devboxes are shown for the selected project.
251
+ Use the project selector at the top of the sidebar to switch between projects
252
+ on the same desktop app account. Reopen the sidebar if it is hidden; the picker
253
+ does not appear in the collapsed header. Threads and devboxes are shown for the selected project.
247
254
  Most projects have one Template box. A project created through a Team
248
255
  Template's **managed projects** mode has no personal Template box and omits that
249
256
  row without changing its normal thread and devbox workflow.
@@ -312,7 +319,7 @@ box has no live metrics.
312
319
 
313
320
  ## Project Settings
314
321
 
315
- Choose the gear on the sidebar's **Project** header for
322
+ Choose **Project settings** beside the project selector for
316
323
  settings that belong to the project rather than to a particular box. This
317
324
  page contains **Project storage**, **Browser**, **Git**, **Agent
318
325
  permissions for this project**, **Devbox lifecycle**, and **Agent settings**,
@@ -490,6 +497,14 @@ The list updates as Claude works, and
490
497
  finished agents leave it after your next message. The inspector is read-only.
491
498
  Older conversations may not have a subagent list.
492
499
 
500
+ When Claude finishes replying while background subagents are still running,
501
+ the thread no longer shows Working. A message you send then reaches Claude
502
+ right away, and the subagents keep running. Stop reads **Stop background
503
+ agents** and will end them; Escape won't. While Claude is still replying, Stop
504
+ will end both the reply and any background subagents. Claude learns which
505
+ subagents Stop ended when you send your next message. The thread list keeps
506
+ showing the thread as working until its subagents finish.
507
+
493
508
  To distinguish Claude and Codex threads at a glance, turn on **Show agent
494
509
  logos** in **Settings > General**. The logos appear
495
510
  at the right edge of thread rows and are off by default.
@@ -562,7 +577,7 @@ terminal bell can request attention without adding an unread thread.
562
577
  ## Search Your Threads
563
578
 
564
579
  Press **Cmd+F** (Ctrl+F), or choose the search button (a magnifying glass)
565
- to the left of **New thread** in the **Devboxes** heading, to open thread search.
580
+ beside the project selector at the top of the sidebar, to open thread search.
566
581
  It searches the titles and
567
582
  text of your own Codex and Claude threads across all of your projects, including archived
568
583
  threads, threads on sleeping machines,
@@ -739,6 +754,16 @@ the user to complete the passkey flow themselves; the resulting Browser profile
739
754
  session remains shared with the agent afterwards. If the user disabled passkey
740
755
  forwarding, they can re-enable it under **Settings > Browser**.
741
756
 
757
+ When an agent needs the user to act in the Browser, such as signing in or
758
+ completing a passkey prompt, it can run `dvb-onbox browser request` from its
759
+ thread (see `onbox-agent-tools.md`). The titlebar's Browser button then shows a
760
+ small blue dot, the same dot the thread list uses for unread threads, while a
761
+ thread on that box is selected. The dot pops in with two rings when it appears
762
+ during use and stays still after that. It disappears when the user opens the
763
+ Browser on that box, when they send their next message in the requesting
764
+ thread, or when the agent withdraws the request. The button's label and icon
765
+ don't change, and the mobile app doesn't show the dot.
766
+
742
767
  Users can also review specific page elements from the Browser. Select the
743
768
  review control to enter a focused **Reviewing** mode, hover to preview a target,
744
769
  and click an element to open a compact comment editor beside it. The cancel
@@ -32,8 +32,8 @@ right preview. For images, click the preview to open a
32
32
  full-screen, zoomable view (scroll or use the toolbar to zoom, drag to pan); the
33
33
  full-screen Files window zooms the image in place instead. Clicking an image
34
34
  file link in a thread opens Files and also opens that full-screen image view.
35
- Files that cannot be previewed inline can still be downloaded when the box
36
- can provide a download URL.
35
+ Files that cannot be previewed inline, including images, videos, and PDFs over
36
+ 100 MB, open in a download-only view.
37
37
 
38
38
  Supported text files can also be edited directly in Files. Changes auto-save
39
39
  after you stop typing and before file switches, pane close, or pop-out changes.
@@ -65,6 +65,11 @@ to reveal the saved file (Open in folder on Windows and Linux). When the selecte
65
65
  file has Git changes, use Git/Review from the file header to open the matching
66
66
  diff in Git/Review.
67
67
 
68
+ The desktop app downloads files up to 5 GiB each, and active downloads count
69
+ toward the same 10 GiB per-user limit as uploads. A box or desktop app awaiting
70
+ an update may still have the previous 100 MB download limit; retry after it
71
+ updates. The mobile app downloads files up to 100 MB.
72
+
68
73
  ### Creating And Managing Files And Folders
69
74
 
70
75
  Use New file or New folder above the tree. The destination starts at the
@@ -140,7 +145,7 @@ Uploads can run in parallel. The file tree shows a slim row for each active
140
145
  upload with progress; successful rows clear after completion, and failed rows
141
146
  can be retried or dismissed. After successful uploads, the target directory
142
147
  reloads. Desktop uploads support files up to 5 GiB each, with up to 10 GiB of
143
- active uploads per user at a time. Before uploading, boxes.dev checks the
148
+ active uploads and downloads per user at a time. Before uploading, boxes.dev checks the
144
149
  box's free disk space and warns if the files will not fit. It checks again
145
150
  before copying each file onto the box. Free up space or choose fewer files
146
151
  if an upload is blocked. A box awaiting an update may still have the previous
@@ -408,9 +413,9 @@ connection to finish.
408
413
 
409
414
  Personal sign-in is optional even when App repository access works. Choose
410
415
  **Connect personal access** under **GitHub CLI access** in Integrations →
411
- GitHub, or **Connect** under **Personal GitHub CLI access (optional)** in
412
- Account or the optional follow-up in onboarding or project setup, or run
413
- `gh auth login` on a Template box or devbox. The description under **GitHub
416
+ GitHub, or under **Personal GitHub CLI access (optional)** in Account or the
417
+ optional follow-up in onboarding or project setup, or run `gh auth login` on
418
+ a Template box or devbox. The description under **GitHub
414
419
  CLI access** names the access `gh` uses. The App covers pull, push, pull requests, and CLI commands
415
420
  within its permissions; personal authorization enables broader CLI use,
416
421
  within the approved scopes and the user's permissions. The App also supports
@@ -458,6 +463,12 @@ runs. For those commands, choose **Disconnect personal access** to use App
458
463
  access after approving its required permissions. Do not assume personal access
459
464
  includes every App capability.
460
465
 
466
+ `gh`'s `--attach` flag uploads images and videos into pull requests, issues,
467
+ and comments (`gh pr create`, `gh pr edit`, `gh pr comment`, and the matching
468
+ `gh issue` commands). It needs personal access. GitHub rejects these uploads
469
+ from the App, and `gh` will report that attaching files requires write access
470
+ to the repository.
471
+
461
472
  Managed `gh` will show a direct installation permission-review link when a
462
473
  supported command needs a newly requested App grant. This covers Actions
463
474
  commands, issue and pull-request changes, and recognized `gh api` writes to
@@ -164,6 +164,11 @@ existing devboxes, running agent sessions, or Template box threads. Clearing
164
164
  the setting removes an older boxes.dev-managed project-guidance block from
165
165
  subsequently created devboxes while preserving other user and managed content.
166
166
 
167
+ In a project that a Team Template manages, each new devbox also gets the
168
+ template's current agent guidance, placed before the project's own guidance.
169
+ A team admin's change to the template's guidance therefore reaches these
170
+ projects' new devboxes without editing each project.
171
+
167
172
  Creation uses the guidance current when the devbox is prepared, including for
168
173
  environment-only creation and paused or draft-prepared devboxes. If guidance
169
174
  cannot be fully applied, devbox creation still succeeds and boxes.dev shows a
@@ -297,6 +302,10 @@ ready; the earlier conversation will load then. You can leave the chat and
297
302
  return while it starts. If the fork fails, your messages remain available to
298
303
  recover, and you can return to the original chat to try the fork again.
299
304
 
305
+ To hand a conversation to a teammate so they continue it with their own
306
+ accounts, transfer the thread to them instead; see **Transferring A Thread To
307
+ A Teammate** in `threads-and-agents.md`.
308
+
300
309
  ## Working Inside The Devbox
301
310
 
302
311
  While a devbox is selected:
@@ -294,8 +294,13 @@ start from the Template box's saved checkout.
294
294
  Inspect `origin` to identify the source Team Template and saved version, the
295
295
  captured `projectConfigurationInput`, and its `configurationSource` when
296
296
  recorded. These show what was copied when the project was created. Compare
297
- those inputs with `team-template settings get` to explain inherited guidance;
298
- changing template defaults will not replace an existing project's copy.
297
+ those inputs with `team-template settings get` to explain inherited settings;
298
+ changing template defaults will not replace an existing project's copy. Agent
299
+ Guidance is the exception for a project the Team Template manages
300
+ (`kind: team_template_managed`): its new devboxes get the template's current
301
+ guidance, a blank line, and then the project's own `lifecycle.agentGuidance`.
302
+ A project created before this behavior may still hold a copy of the template's
303
+ guidance in its own field, so its devboxes would get that text twice.
299
304
  Older projects without recorded creation inputs report a null origin.
300
305
 
301
306
  Team Template output includes its identity, description, source/repositories,
@@ -326,6 +331,29 @@ including from an independent project created from it. Request only the minimum
326
331
  permission returned by a denied write. Agent permission defaults remain
327
332
  user-only even with an editing grant.
328
333
 
334
+ #### Teammates' project settings
335
+
336
+ A team admin's agent can open any project owned by a current member of the
337
+ team, including a teammate's project or another of the admin's own projects,
338
+ by adding `--project` with a `projectId` from `team settings get`:
339
+
340
+ ```bash
341
+ dvb-onbox project settings get --project <project-id> --json
342
+ dvb-onbox project settings set --settings-file /home/boxes/settings-edit.json --project <project-id> --json
343
+ ```
344
+
345
+ Reads need only team admin and return that project's settings without its
346
+ environment metadata. Saves also need the thread's `edit-team-template` grant.
347
+ They support `lifecycle`, `git`, `ports_enabled`, `ports`, `default_branches`,
348
+ `storage`, `browser`, `agent_settings`, `maintenance`, `maintenance_delete`,
349
+ `maintenance_watches`, and the Project URL sections. Other sections fail with
350
+ `member_project_section_unsupported`, because they act on the calling box or
351
+ thread, the owner's account, the owner's connected integrations, or the
352
+ owner's own environment values and member files. `admin_required` means the
353
+ user isn't a team admin; `project_not_found` means no current member of the
354
+ team owns that project. Saved changes apply to the owner's future devboxes,
355
+ and the owner isn't notified.
356
+
329
357
  ### Integration status and setup
330
358
 
331
359
  The project read includes `integrations.isTeamAdmin` and
@@ -573,8 +601,12 @@ dvb-onbox team settings set --settings-file /home/boxes/team-edit.json --json
573
601
 
574
602
  Reads list the team's name, members and roles, invites, allowed domains,
575
603
  teammate thread access policy, idle sleep default, and static egress
576
- destinations. Changes need the thread's `edit-team-template` grant; only team
577
- admins can read or change these settings.
604
+ destinations. `memberProjects` lists every project owned by a current member,
605
+ including the admin's own, with its `projectId`, `alias`, `kind`,
606
+ `teamTemplateId`, `archived`, and `owner`; pass a `projectId` to
607
+ [`project settings --project`](#teammates-project-settings). Changes need the
608
+ thread's `edit-team-template` grant; only team admins can read or change these
609
+ settings.
578
610
 
579
611
  | Section | Fields |
580
612
  | --- | --- |
@@ -1042,9 +1074,10 @@ own environment and member-file values, to share the current thread, and to
1042
1074
  change the user's [account preferences](#account-preferences). It cannot change
1043
1075
  agent permission defaults. Request
1044
1076
  `edit-team-template` from any box in one of the user's projects to edit
1045
- [team settings](#team-settings) and, in a project created from a Team
1046
- Template, that Team Template's settings, including environment and member-file
1047
- definitions; only a team admin can receive it. Request `edit-personal-environment` from a devbox in a Team
1077
+ [team settings](#team-settings), the settings of any project on the team
1078
+ ([`--project`](#teammates-project-settings)), and, in a project created from a
1079
+ Team Template, that Team Template's settings, including environment and
1080
+ member-file definitions; only a team admin can receive it. Request `edit-personal-environment` from a devbox in a Team
1048
1081
  Template project to edit the user's own environment variables for that
1049
1082
  project; any member can receive it, and a thread that already has
1050
1083
  `edit-team-template` or `edit-project-settings` does not need it. A thread holds one of these grants at a
@@ -1113,7 +1146,7 @@ dvb-onbox threads get-title --json
1113
1146
 
1114
1147
  The result includes the title source (`manual`, `generated`, `first_message`,
1115
1148
  or `placeholder`) and whether title editing is enabled on the current box. The
1116
- command accepts no thread ID and works even when editing is disabled.
1149
+ command works even when editing is disabled.
1117
1150
 
1118
1151
  Users can independently enable **Update thread titles** from the **Agent
1119
1152
  permissions** control in an owned Codex or Claude thread header. That header
@@ -1134,8 +1167,14 @@ dvb-onbox threads set-title --title "New central topic" --json
1134
1167
  The title must be non-empty and at most 120 Unicode characters. Managed-agent
1135
1168
  guidance limits edits to meaningful central-topic changes and requires the
1136
1169
  agent to ask before replacing a manual title. The command does not rename a
1137
- provider-native Codex or Claude session and cannot clear or target another
1138
- thread title.
1170
+ provider-native Codex or Claude session and cannot clear a title.
1171
+
1172
+ Only the project coordinator can name another thread, with
1173
+ `--thread <thread-id>` on `get-title` or `set-title`. It can name any of the
1174
+ user's unarchived threads in its project, including Template box threads,
1175
+ except its own chat; other targets return `thread_not_found`. Its own **Update
1176
+ thread titles** permission decides whether it can rename them. Other agents
1177
+ that pass `--thread` get `invalid_request`.
1139
1178
 
1140
1179
  When a user-required title change returns `title_editing_disabled`, request
1141
1180
  only `update-thread-titles` through the Agent permissions command above. Do not
@@ -1247,6 +1286,39 @@ codes:
1247
1286
  | `unauthorized` | boxes.dev rejected this box's credentials. | `false` |
1248
1287
  | `service_unavailable` | Presence is temporarily unavailable. Wait a minute and try again. | `true` |
1249
1288
 
1289
+ ## Browser Requests
1290
+
1291
+ When the user has to do something in the box's Browser themselves, such as
1292
+ signing in, completing a passkey prompt, or solving a captcha, an agent can
1293
+ point them to it:
1294
+
1295
+ ```bash
1296
+ dvb-onbox browser request
1297
+ dvb-onbox browser clear-request
1298
+ ```
1299
+
1300
+ `request` puts a small blue dot on the Browser button in the owner's desktop
1301
+ app while a thread on this box is selected. The dot stays until one of these
1302
+ happens:
1303
+
1304
+ - The owner opens the Browser on this box, which clears every request on the
1305
+ box.
1306
+ - The owner sends their next message in the requesting thread. Scheduled
1307
+ checks, automation runs, automatic pull request follow-ups, and messages
1308
+ from other agents don't count.
1309
+ - The agent runs `clear-request`.
1310
+
1311
+ Requests from archived or deleted threads stop showing. A request carries no
1312
+ text, so the agent should still say in its reply what the user needs to do.
1313
+ Both commands act on the managed thread that runs them, take no thread ID, and
1314
+ need no permission. With `--json`, they print
1315
+ `{"schemaVersion": 1, "ok": true, "operation": "request"}` or
1316
+ `"operation": "clear"`. `thread_context_unavailable` means boxes.dev couldn't
1317
+ match the command to a managed Codex or Claude thread running on this box: it
1318
+ ran outside a managed thread, its thread identity didn't resolve to a thread on
1319
+ this box, or the box isn't running. `daemon_update_required` means the box's
1320
+ boxes.dev service predates the command. The mobile app doesn't show the dot.
1321
+
1250
1322
  ## Pull Request Follow-ups
1251
1323
 
1252
1324
  boxes.dev can send a managed Codex or Claude thread a message when its pull
@@ -2323,6 +2395,12 @@ it. Template boxes, teammates' devboxes, and devboxes in other projects return
2323
2395
  `invalid_request`; see
2324
2396
  [Destroy And Archive The Current Devbox](#destroy-and-archive-the-current-devbox).
2325
2397
 
2398
+ The project coordinator has its own **Destroy and archive devboxes** setting
2399
+ with the levels **Started by the coordinator** and **In this project**. It
2400
+ never follows the project setting, so its requests can be allowed only for the
2401
+ coordinator. It can't destroy its own box. Its instructions limit destruction
2402
+ to a direct request from the user in its chat.
2403
+
2326
2404
  Run this only when the user's task calls for it, such as after the devbox's
2327
2405
  work has merged or has otherwise been preserved outside the machine. If it's
2328
2406
  unclear which devboxes the user means, ask before requesting destruction.
@@ -2386,6 +2464,32 @@ other boxes return `thread_not_found`. Threads that haven't started return
2386
2464
  `archive_disabled` error, request `destroy-created-devboxes`. Permission to
2387
2465
  destroy this devbox does not grant permission to archive individual threads.
2388
2466
 
2467
+ ## Work Package Requests
2468
+
2469
+ When a user transfers a thread to a teammate, boxes.dev sends a work package
2470
+ request into that thread. The thread's Git work (local commits, staged and
2471
+ unstaged edits, and new untracked files that Git doesn't ignore) is packaged
2472
+ automatically. The request asks for anything else the work needs; answer it
2473
+ once from the same thread:
2474
+
2475
+ ```bash
2476
+ dvb-onbox threads package create --package <id> --include <path> --env-key <file>:<KEY>
2477
+ dvb-onbox threads package create --package <id> --json
2478
+ ```
2479
+
2480
+ `--include` adds files Git doesn't cover, from the repository, the home
2481
+ directory, or anywhere else on the devbox such as `/tmp`; they land at the
2482
+ same place on the teammate's devbox. `--env-key` is for the rare new
2483
+ environment variable the work added: it sends one variable's definition from
2484
+ an env file, such as `.env.local:API_URL`, and the teammate gets it only if
2485
+ their file doesn't define it. Don't include env files or credentials
2486
+ themselves, and don't edit files, environment variables, or project settings
2487
+ to answer the request. Relative paths resolve from the current folder, and
2488
+ a folder includes its contents. Run it with no options when nothing else is
2489
+ needed. Packages are limited to 512 MB. `package_not_waiting` means the
2490
+ package already exists or the transfer no longer needs it. The
2491
+ `boxes-work-packages` skill covers what to include.
2492
+
2389
2493
  ## Devbox Folders
2390
2494
 
2391
2495
  Project folders group whole ordinary devboxes in the desktop thread list. They
@@ -2452,6 +2556,13 @@ The Template box cannot move itself. Sibling, manually created, indirect, stale,
2452
2556
  cross-project, and cross-owner devboxes fail without revealing whether another
2453
2557
  target exists.
2454
2558
 
2559
+ The project coordinator can move any of the user's devboxes in its project
2560
+ except its own box. For the coordinator, `folders list` also returns each
2561
+ folder's `devboxes`, with `devboxId`, `title`, and `folderRevision`, including
2562
+ pinned devboxes; the field is null for other boxes. Unfiled devboxes aren't
2563
+ listed: find them with `threads list --scope project` and read each one's
2564
+ revision with `folders get`.
2565
+
2455
2566
  `folder_revision_conflict` means another person or agent changed the membership.
2456
2567
  Run `get` again and reconsider the operation; moves never overwrite a newer
2457
2568
  revision. Keep one idempotency key per logical create or move, and retry an
@@ -44,7 +44,9 @@ When a new connection finishes either way, the app DMs the Slack user who
44
44
  approved it with getting-started steps and links to the Slack help article and
45
45
  support. A reinstall while the workspace is still connected, for example to add
46
46
  permissions, sends no DM; a reinstall after an uninstall, a disconnect, or a
47
- connection that needed a reinstall does.
47
+ connection that needed a reinstall does. Anyone else who opens the app's
48
+ **Messages** tab before the app has messaged them gets a short welcome with how
49
+ to link their Slack account (`connect`) and see what they can do (`help`).
48
50
 
49
51
  After Slack redirects back, the Slack integration home continues through the
50
52
  remaining setup steps: link your identity, create your automation, and activate
@@ -75,12 +77,13 @@ to request deletion.
75
77
 
76
78
  Slack-triggered automations need to know which boxes.dev user a Slack user
77
79
  represents. The Slack integration home shows **Link your account** when this
78
- step is still needed.
80
+ step is still needed. When a team admin connects the workspace, boxes.dev also
81
+ links the admin's own Slack account if it uses their verified boxes.dev email.
79
82
 
80
83
  You can link by:
81
84
 
82
- - choosing **Connect Slack** on the **Account** step of first-run desktop setup
83
- or on the website's getting-started page, when your team already has a
85
+ - choosing **Link your account** on the **Account** step of first-run desktop
86
+ setup or on the website's getting-started page, when your team already has a
84
87
  connected Slack workspace;
85
88
  - using **Find my Slack account** in the automation editor, or under **Slack
86
89
  identity** on the **Account** page when boxes.dev hasn't seen your Slack
@@ -93,10 +96,10 @@ you, including `help`, with a DM containing a connect link, the next setup
93
96
  steps, and links to the Slack help article and support. The connect link works
94
97
  whatever email your Slack profile uses.
95
98
 
96
- **Link your account**, **Connect Slack**, and **Find my Slack account** look
97
- for a Slack account with your verified boxes.dev email and link it. When none
98
- matches, Slack opens and asks you to sign in to the team's workspace, and
99
- boxes.dev links the account you sign in with. The sign-in can't link a bot, a
99
+ **Link your account** and **Find my Slack account** look for a Slack account
100
+ with your verified boxes.dev email and link it. When none matches, Slack opens
101
+ and asks you to sign in to the team's workspace, and boxes.dev links the
102
+ account you sign in with. The sign-in can't link a bot, a
100
103
  guest, a member of another workspace, or an account that is already linked to
101
104
  another boxes.dev user. Verify your boxes.dev email before linking.
102
105
 
@@ -267,6 +267,11 @@ devboxes and does not rerun startup on the current one.
267
267
  Team teardown failures remain available on the template page. Saving a script
268
268
  records it; it does not run it or publish a new saved version.
269
269
 
270
+ A member can transfer a thread to a teammate whose project starts from the
271
+ same Team Template. The thread moves to a new devbox from the current saved
272
+ version in the teammate's project; see **Transferring A Thread To A Teammate**
273
+ in `threads-and-agents.md`.
274
+
270
275
  ## Environment And Member Files
271
276
 
272
277
  The **Environment and member files** card holds the template's environment
@@ -375,7 +380,10 @@ creation. Saving a setting does not save a new filesystem version and does not
375
380
  wait for the current editing session to close. Unsaved changes remain only in
376
381
  that focused editor; there is no configuration draft, filesystem save,
377
382
  history, or rollback. Existing projects keep these copied settings; managed
378
- MCP definitions follow the separate live rules above. An
383
+ MCP definitions follow the separate live rules above. Agent guidance is not
384
+ copied into managed projects: each new devbox in a managed project gets the
385
+ template's current guidance, followed by the guidance the member saved in their
386
+ own project settings. Independent projects receive a copy. An
379
387
  independent project with its own Template box receives every applicable
380
388
  setting; managed projects receive the same settings except setup instructions
381
389
  and maintenance.