@boxes-dev/dvb-runtime 1.0.1098 → 1.0.1099

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.
Files changed (31) hide show
  1. package/dist/agent-init-guides/git-ssh.md +2 -2
  2. package/dist/bin/dvb.mjs +14 -14
  3. package/dist/bin/dvbd.mjs +4 -4
  4. package/dist/product-docs/references/agent-tools.md +6 -7
  5. package/dist/product-docs/references/automations.md +4 -4
  6. package/dist/product-docs/references/aws.md +17 -11
  7. package/dist/product-docs/references/billing-and-limits.md +23 -11
  8. package/dist/product-docs/references/cli.md +14 -15
  9. package/dist/product-docs/references/core-concepts.md +35 -30
  10. package/dist/product-docs/references/desktop-workbench.md +24 -24
  11. package/dist/product-docs/references/files-git-and-review.md +14 -15
  12. package/dist/product-docs/references/fork-workflows.md +20 -19
  13. package/dist/product-docs/references/getting-started.md +7 -8
  14. package/dist/product-docs/references/glossary.md +46 -22
  15. package/dist/product-docs/references/google-cloud.md +13 -8
  16. package/dist/product-docs/references/index.md +18 -16
  17. package/dist/product-docs/references/linear.md +2 -2
  18. package/dist/product-docs/references/managed-environment-files.md +1 -1
  19. package/dist/product-docs/references/member-managed-files.md +4 -4
  20. package/dist/product-docs/references/mobile.md +18 -16
  21. package/dist/product-docs/references/onbox-agent-tools.md +25 -26
  22. package/dist/product-docs/references/ports-terminal-and-runtime.md +27 -28
  23. package/dist/product-docs/references/project-setup.md +9 -9
  24. package/dist/product-docs/references/security-and-data.md +10 -10
  25. package/dist/product-docs/references/slack.md +3 -3
  26. package/dist/product-docs/references/tailscale.md +2 -2
  27. package/dist/product-docs/references/team-template.md +22 -22
  28. package/dist/product-docs/references/template-box-environment.md +7 -3
  29. package/dist/product-docs/references/threads-and-agents.md +41 -22
  30. package/dist/product-docs/references/troubleshooting.md +24 -25
  31. package/package.json +2 -2
@@ -6,10 +6,10 @@ why a setup step is waiting, how to resume setup, or how to add another project.
6
6
  ## What Setup Creates
7
7
 
8
8
  The local-folder, agent-driven, and direct GitHub setup paths described here
9
- create one ordinary project with one Template box. The Template box is the
9
+ create one independent project with one Template box. The Template box is the
10
10
  persistent base machine for that project. After setup, future devboxes start
11
11
  from snapshots of this Template box. A Team Template can separately enable
12
- **Member projects**, which have no personal Template box; see
12
+ **managed projects**, which have no personal Template box; see
13
13
  `team-template.md` for that flow.
14
14
 
15
15
  The desktop app's Project step recommends agent-driven setup first: the user's
@@ -169,7 +169,7 @@ If the desktop window reloads, the app rediscovers the matching local setup and
169
169
  continues the secure bundle handoff. The setup progress banner also provides
170
170
  **Resume setup** while the desktop still needs to finish the handoff, then
171
171
  **Open setup thread** once the setup agent is running. Once bundle extraction
172
- is complete, ordinary project actions become available while the setup thread
172
+ is complete, independent project actions become available while the setup thread
173
173
  continues.
174
174
 
175
175
  ## Agent-Driven Setup From The Terminal
@@ -543,8 +543,8 @@ Company AWS access is managed separately from project setup under
543
543
  sign-in and chooses one assigned account and role for the project, or enters an
544
544
  IAM user's access key. boxes.dev then applies the managed `boxes-dev` profile to
545
545
  the Template box and devboxes without changing the repository or requiring a
546
- new snapshot. Open a new terminal or agent session after connecting or changing
547
- the role. See `aws.md` for profile precedence, central refresh, removal, and
546
+ new snapshot. Open terminals pick up the change at their next prompt, and
547
+ agent sessions before their next turn. See `aws.md` for profile precedence, central refresh, removal, and
548
548
  container limits.
549
549
 
550
550
  Project setup Codex scans may use the user's local Codex sign-in on this
@@ -629,7 +629,7 @@ Canceling setup or deleting the boxes.dev project does not delete a repository
629
629
  created on GitHub.
630
630
 
631
631
  A project created through this direct GitHub path can contain up to 20 selected
632
- repositories, but it still creates exactly one ordinary project and one
632
+ repositories, but it still creates exactly one independent project and one
633
633
  Template box. Setup starts in
634
634
  single-repository mode; switching it to multiple repositories is an explicit
635
635
  choice to combine several repositories into one project. With one repository,
@@ -1107,10 +1107,10 @@ To upload another local project, use **New project...** in the titlebar project
1107
1107
  selector or **File > New Project...** in the desktop app. On the website,
1108
1108
  **New project** offers the coding-agent prompt and **Create from GitHub**. For
1109
1109
  a repository that is not on the user's computer, **Create from GitHub** clones
1110
- another GitHub-backed ordinary project instead, with the same manual
1111
- environment setup afterwards. Each ordinary project made through
1110
+ another GitHub-backed independent project instead, with the same manual
1111
+ environment setup afterwards. Each independent project made through
1112
1112
  these paths gets its own setup flow and Template box. A Team Template's
1113
- **Member projects** path is the exception: it creates an independent project
1113
+ managed-project path is the exception: it creates a managed project
1114
1114
  without a personal Template box and uses the Team Template's current saved
1115
1115
  version for future devboxes. Existing agent auth can be reused by local-folder
1116
1116
  setup, but each local project still needs its own folder selection, scans,
@@ -144,14 +144,14 @@ disconnecting the main GitHub connection.
144
144
 
145
145
  When automatic Git access uses the GitHub App, the connected user's App
146
146
  credential remains encrypted at rest in boxes.dev. When Git needs access, the
147
- machine requests that credential through a local helper. For ordinary projects,
147
+ machine requests that credential through a local helper. For independent projects,
148
148
  boxes.dev first checks the machine's ownership and that the connected user can
149
149
  read the requested repository. GitHub enforces write permissions when pushing.
150
150
  The token can exist in the boxes.dev service, local
151
151
  service, Git process, and snapshot process memory, but is not written to the
152
152
  remote URL or a managed credential file.
153
153
 
154
- Ordinary project checkout selection does not restrict Git access. Code running
154
+ Independent project checkout selection does not restrict Git access. Code running
155
155
  on the box can request and inspect the App credential,
156
156
  whose access is the intersection of the connected user's repositories and the
157
157
  repositories and permissions granted to the boxes.dev GitHub App. Current App
@@ -166,7 +166,7 @@ removing App access stops future App helper issuance after its bounded cache
166
166
  lease, but does not itself revoke an App token already returned to a process.
167
167
  GitHub attributes the Git operation to the connected user.
168
168
 
169
- Team Template member projects retain their separate release-bound repository
169
+ Managed projects retain their separate release-bound repository
170
170
  checks. Team Template editing uses repository-restricted App installation
171
171
  credentials rather than an administrator's broad user credential.
172
172
 
@@ -265,7 +265,7 @@ Template boxes and devboxes are full cloud Linux development machines. Agents
265
265
  and users can run commands, edit files, install dependencies, open ports, and
266
266
  interact with local services inside either machine.
267
267
 
268
- A Team Template member project has no personal Template box. Team admins author
268
+ A managed project has no personal Template box. Team admins author
269
269
  its shared saved files in separate Team Template editing machines, and members
270
270
  cannot access those machines through their projects. Prepared devboxes belong
271
271
  to one member and project. The team-authored startup script runs immediately
@@ -273,19 +273,19 @@ before the member's startup script, with the same prepared member credentials
273
273
  and files available to both. Team admins are trusted authors of that code.
274
274
  Once assigned to a draft, the devbox never returns to a prepared pool.
275
275
 
276
- Anything available inside the selected machine can usually be read or changed by
276
+ Anything available inside the selected box can usually be read or changed by
277
277
  the agent running there. This includes checked-out code, local env files, local
278
278
  databases, generated files, and credentials copied into the environment.
279
279
 
280
280
  Devboxes are isolated from their source after they are created. A devbox has
281
281
  its own filesystem, processes, ports, local database state, and agent threads.
282
- Work done on a devbox does not automatically change an ordinary project's
282
+ Work done on a devbox does not automatically change an independent project's
283
283
  Template box or a Team Template saved version. Move changes intentionally with
284
284
  Git or another explicit workflow.
285
285
 
286
286
  ## Files, Transcripts, And Metadata
287
287
 
288
- Most repository files and terminal/session history live on the selected machine
288
+ Most repository files and terminal/session history live on the selected box
289
289
  filesystem. Product surfaces can stream or display those files and histories so
290
290
  users can review work from desktop, mobile, web, or CLI.
291
291
 
@@ -295,9 +295,9 @@ status, detected ports, notification tokens, short session title summaries, and
295
295
  limited snippets that support the UI.
296
296
 
297
297
  boxes.dev stores thread transcript history so users can review conversation
298
- history without waking the selected machine.
298
+ history without waking the selected box.
299
299
 
300
- Forwarded ports expose local development services from the selected runtime.
300
+ Forwarded ports expose local development services from the selected box.
301
301
  Users should treat forwarded apps as development surfaces and avoid exposing
302
302
  production-admin tools or sensitive local dashboards unless that is intentional.
303
303
 
@@ -348,7 +348,7 @@ the legal privacy policy at `https://boxes.dev/privacy`.
348
348
 
349
349
  Deleting a project permanently deletes its personal Template box when it has
350
350
  one, its devboxes, snapshots, threads, and attached project data. Deleting a
351
- Team Template member project does not delete the shared Team Template or affect
351
+ managed project does not delete the shared Team Template or affect
352
352
  another member's project. The product asks the user to type the project name
353
353
  before deletion. Treat project deletion as irreversible.
354
354
 
@@ -160,8 +160,8 @@ would trust with that access, including on named commands that allow
160
160
  teammates.
161
161
 
162
162
  boxes.dev starts each automation run on a fresh devbox from the latest
163
- Template box snapshot for an ordinary project, or the current saved Team
164
- Template version for a member project. The agent sees the automation prompt
163
+ Template box snapshot for an independent project, or the current saved Team
164
+ Template version for a managed project. The agent sees the automation prompt
165
165
  plus Slack context, including the triggering message and available Slack
166
166
  thread messages. If Slack context is incomplete, boxes.dev can start with
167
167
  partial context instead of waiting forever.
@@ -274,7 +274,7 @@ Use Slack controls in the linked thread:
274
274
  - `@boxes.dev !cancel` cancels queued Slack follow-ups when possible.
275
275
 
276
276
  If the linked devbox is sleeping, boxes.dev may queue the follow-up while the
277
- runtime wakes. If capacity is full, Slack replies with guidance when follow-up
277
+ box wakes. If capacity is full, Slack replies with guidance when follow-up
278
278
  confirmations are enabled.
279
279
 
280
280
  ## Slack Files
@@ -1,8 +1,8 @@
1
1
  # Tailscale Integration
2
2
 
3
3
  The Tailscale integration connects a project's machines to a team's tailnet as
4
- tagged, ephemeral Tailscale devices. For an ordinary project, that includes its
5
- Template box and devboxes. A Team Template member project has no personal
4
+ tagged, ephemeral Tailscale devices. For an independent project, that includes its
5
+ Template box and devboxes. A managed project has no personal
6
6
  Template box, so only its assigned devboxes connect. A team admin connects the
7
7
  tailnet once, and each project owner verifies their own access before enabling
8
8
  the integration for that project. No one signs in to Tailscale separately on
@@ -7,11 +7,11 @@ Template.
7
7
  ## What The Team Template Is
8
8
 
9
9
  A Team Template is one named, team-wide starting environment for new projects.
10
- It is separate from each ordinary project's Template box. A team can keep
10
+ It is separate from each independent project's Template box. A team can keep
11
11
  several Team Templates for different project shapes—for example, a website
12
12
  playground, a full-stack application, and backend services. Each Team Template
13
13
  has one latest saved version. The ordinary creation path gives a new project
14
- an independent Template box copied from that version. The optional **Member
14
+ an independent Template box copied from that version. The optional **managed
15
15
  projects** mode instead gives the member no Template box and uses the Team
16
16
  Template's current saved version for each future devbox.
17
17
 
@@ -24,8 +24,8 @@ environment.
24
24
  Team Templates are available to every team without an enablement step.
25
25
 
26
26
  Any current team member can inspect the team's available Team Templates. A
27
- member can create an ordinary project from a template only when it has a saved
28
- version. Member-project creation also requires an admin to enable it on that
27
+ member can create an independent project from a template only when it has a saved
28
+ version. Managed-project creation also requires an admin to enable it on that
29
29
  Team Template. Only team admins can create, rename, archive, or restore
30
30
  templates; edit them; save new versions; use an older
31
31
  version; or remove an older version.
@@ -37,7 +37,7 @@ assigned to its admin if the desktop app closes or the machine sleeps.
37
37
 
38
38
  The saved environment is separate from every admin editing session. After a
39
39
  successful save, boxes.dev keeps the cleaned environment asleep as the shared
40
- source for later editing sessions and member-project devboxes. It is not a
40
+ source for later editing sessions and managed-project devboxes. It is not a
41
41
  Template box that admins or members can open. Discarding an editing session
42
42
  therefore removes only that unsaved session and never changes the shared saved
43
43
  environment.
@@ -59,7 +59,7 @@ uses permanent project deletion and requires confirmation for each project.
59
59
  Keep moves the project to the departing account's fresh personal team and
60
60
  removes managed files, managed secrets, team access, and existing thread
61
61
  sharing. Ordinary files and unmanaged environment-file content remain.
62
- A kept Member project receives an independent Template box.
62
+ A kept managed project receives an independent Template box.
63
63
 
64
64
  Sleeping boxes remain asleep during Transfer and Keep. Ownership and team
65
65
  access change during removal; managed files and credentials are cleaned up on
@@ -158,7 +158,7 @@ settings in the order they are usually needed:
158
158
  machine size, the editing status and **Take control** action, plus rows for
159
159
  **Maintenance**, the **Cleanup before saving** script, and **Previous
160
160
  versions**.
161
- - **Member projects**: whether this template creates independent or managed
161
+ - **Projects from this template**: whether this template creates independent or managed
162
162
  projects, and the **Pause new projects** / **Resume new projects** control
163
163
  for managed templates.
164
164
  - **When a new devbox is created**: the startup and teardown sequence with the
@@ -180,7 +180,7 @@ settings**, save it, then restore the archived template.
180
180
  An archived template's name and description remain editable. Restore it before
181
181
  changing other settings or running maintenance.
182
182
 
183
- The **Member projects** card explains which kind of project the template
183
+ The **Projects from this template** card explains which kind of project the template
184
184
  creates. A template creates independent projects until an admin chooses **Set
185
185
  up managed projects…**; the confirmation states that members will get no
186
186
  Template box of their own, that new devboxes will start from the latest saved
@@ -319,20 +319,20 @@ permissions.
319
319
 
320
320
  For managed projects, the admin chooses one of two modes:
321
321
 
322
- - **Editable defaults:** each Member project follows the template's values
322
+ - **Editable defaults:** each managed project follows the template's values
323
323
  until the member changes a permission in Project settings. A permission the
324
324
  member changed stays as they set it when the template changes. **Use Team
325
325
  Template permissions** in Project settings returns every permission to the
326
326
  template's values.
327
- - **Locked:** every Member project uses the template's values, and members
327
+ - **Locked:** every managed project uses the template's values, and members
328
328
  can't change them in Project settings. Locking replaces any permissions
329
329
  members chose themselves. Unlocking keeps everyone on the template's values
330
330
  until a member changes one.
331
331
 
332
332
  The first time an admin saves editable defaults for a template that already
333
- has Member projects, boxes.dev asks whether those projects should move to the
333
+ has managed projects, boxes.dev asks whether those projects should move to the
334
334
  template's values or keep their current permissions as the members' own
335
- choices. Either way, new Member projects will follow the template.
335
+ choices. Either way, new managed projects will follow the template.
336
336
 
337
337
  In both modes, members can still change permissions on an individual box from
338
338
  its thread header, and agents can still request permission for their own box.
@@ -386,7 +386,7 @@ no provider credentials, identities, automation settings, or machine state.
386
386
 
387
387
  Box size is fixed for the Team Template lineage and is not a Project
388
388
  default. Project creation offers no per-default overrides; members can change
389
- the resulting ordinary project afterward.
389
+ the resulting independent project afterward.
390
390
 
391
391
  ## Team Template Maintenance
392
392
 
@@ -408,7 +408,7 @@ to establish its shared saved environment. A failure preserves the prior saved
408
408
  version, discards any machine that may have been partly changed, and never
409
409
  modifies an admin's editing session.
410
410
 
411
- boxes.dev prepares a few devboxes for each member project ahead of time. For a
411
+ boxes.dev prepares a few devboxes for each managed project ahead of time. For a
412
412
  minute or two after a maintenance run makes a new saved version current, while
413
413
  those are replaced, a new devbox can start from one prepared from the previous
414
414
  saved version if the startup and teardown scripts and the box size have not
@@ -425,11 +425,11 @@ repositories, then choose **Refresh repository access** on the
425
425
  maintenance failure before running it again. Repair refreshes only repositories
426
426
  the Team Template already tracks; it does not add or replace a repository.
427
427
 
428
- Ordinary projects created with a personal Template box receive an independent
428
+ Independent projects created with a personal Template box receive an independent
429
429
  maintenance policy and watches containing only the saved behavior. Their
430
430
  schedules start at the next future occurrence, and enabled watches establish a
431
431
  fresh repository baseline without an initial run. Authorization, repository
432
- baselines, run history, errors, and other live state are never copied. Member
432
+ baselines, run history, errors, and other live state are never copied. Managed
433
433
  projects do not copy or run Team Template maintenance; their future devboxes
434
434
  use the Team Template's current saved files instead.
435
435
 
@@ -489,7 +489,7 @@ environment in the background and keeps the current version active until the
489
489
  older one is ready; the page shows preparation progress or a retryable failure.
490
490
  The next save still receives the next version number. Removing an inactive
491
491
  version requires a reason, prevents new work from starting from it, and cancels
492
- project creation still in progress from it. Ordinary projects that already
492
+ project creation still in progress from it. Independent projects that already
493
493
  received their independent Template box continue to work. Saving, changing the
494
494
  current version, removal, and cleanup on one Team Template do not change
495
495
  another.
@@ -546,7 +546,7 @@ permanently. A later provider disconnection may show the ordinary integration
546
546
  warning, but it does not reopen setup or block project use. Later Team Template
547
547
  requirement changes apply only to new projects.
548
548
 
549
- In a Member project, an untouched new-devbox draft uses the ordinary composer
549
+ In a managed project, an untouched new-devbox draft uses the ordinary composer
550
550
  and notes that sending creates a devbox from the team's Template. A new thread
551
551
  on an existing devbox shows neither that note nor new-devbox blockers. For a
552
552
  new-devbox draft, a missing agent connection, missing GitHub repository access,
@@ -572,7 +572,7 @@ The new project is independent of later Team Template versions and save cleanup.
572
572
  When removing a member, an admin chooses whether to transfer, delete, or let
573
573
  that member keep each project under the removal rules above.
574
574
  Creating it uses a normal project slot and its
575
- runtime uses the member's normal billing entitlement.
575
+ box uses the member's normal billing entitlement.
576
576
 
577
577
  Setup instructions are current Project defaults, not part of the filesystem
578
578
  save cadence. If instructions are present and the selected agent is authenticated,
@@ -629,11 +629,11 @@ a GitHub connection unless another configured feature requires it.
629
629
  ## Files And Credentials Included In A Saved Version
630
630
 
631
631
  Team admins are trusted authors of the shared environment. Saving removes
632
- boxes.dev-managed runtime identity and session state before capture, but it
632
+ boxes.dev-managed box identity and session state before capture, but it
633
633
  does not guess which team-authored files are secrets. Files deliberately left
634
634
  in the environment—including `.env` files, databases, shell history, or
635
- custom SSH and cloud credentials—are copied into ordinary projects and into
636
- member-project devboxes that use the saved version.
635
+ custom SSH and cloud credentials—are copied into independent projects and into
636
+ managed-project devboxes that use the saved version.
637
637
 
638
638
  The short-lived GitHub App token used during setup is removed after cloning.
639
639
  The separate short-lived token used during editing is removed on pause and
@@ -128,7 +128,11 @@ in managed environment files, not in the script. The runner starts from a
128
128
  login shell, then runs the script with noninteractive bash and
129
129
  `set -e -o pipefail`, with `HOME=/home/boxes` and `/opt/devbox-tools/bin` first
130
130
  on PATH. Interactive `~/.bashrc` setup, such as nvm's shell hook, does not
131
- load. Agent setup tests a proposed script twice in this environment before
131
+ load. When the project is connected to AWS or Google Cloud, the script
132
+ receives the same defaults as a new terminal, so `aws` and `gcloud` act as the
133
+ project owner. A tool that writes an access token to a file during
134
+ maintenance, such as a package registry login, leaves it in the snapshot that
135
+ new devboxes copy, so the script should delete that file before it exits. Agent setup tests a proposed script twice in this environment before
132
136
  saving it.
133
137
  Automatic scheduling is optional; the supported cadences are every 6 hours,
134
138
  every 12 hours, nightly, and weekly.
@@ -183,7 +187,7 @@ indicator. Provider-side detection failures stay visible on the affected watch
183
187
  without raising that red indicator; retry them and contact support if they
184
188
  persist.
185
189
 
186
- The desktop workbench also shows the owner of an ordinary project a maintenance
190
+ The desktop workbench also shows the owner of an independent project a maintenance
187
191
  attention banner. **Maintenance settings** opens the relevant card. A failed
188
192
  or timed-out script offers **Ask an agent to fix it**, which creates a fresh,
189
193
  unsent Template box draft with the full saved script, the failed run's script
@@ -199,7 +203,7 @@ inaccessible repositories and other branches, and names the most-behind
199
203
  repository when there are several. Any saved policy suppresses this reminder.
200
204
  After dismissal it returns only after seven days and at least 100 additional
201
205
  missing commits. Both dismissals are per viewer, Template and device. These
202
- banners apply to ordinary projects; Team Template administration has its own
206
+ banners apply to independent projects; Team Template administration has its own
203
207
  maintenance workflow.
204
208
 
205
209
  Maintenance and snapshot creation never overlap, but maintenance may interrupt
@@ -5,7 +5,7 @@ threads in boxes.dev.
5
5
 
6
6
  ## Thread Types
7
7
 
8
- A thread is a conversation with a coding agent connected to a runtime. A thread
8
+ A thread is a conversation with a coding agent connected to a box. A thread
9
9
  can run on:
10
10
 
11
11
  - the Template box, for setup, maintenance, and shared baseline work in a
@@ -23,10 +23,10 @@ than separate agent choices.
23
23
  Start threads from the desktop thread list.
24
24
 
25
25
  Use **New thread** for most work. A devbox thread gives the task its
26
- own isolated machine. In an ordinary project, this uses the latest Template-box
27
- snapshot when one is available. In a Team Template member project, it uses the
26
+ own isolated machine. In an independent project, this uses the latest Template-box
27
+ snapshot when one is available. In a managed project, it uses the
28
28
  Team Template's current saved version and the project's prepared devbox pool.
29
- If an ordinary project has no snapshot yet, the devbox start control may first
29
+ If an independent project has no snapshot yet, the devbox start control may first
30
30
  take one and then create the devbox.
31
31
 
32
32
  Use **New thread** on the Template box only when the work belongs in the shared
@@ -40,7 +40,7 @@ new snapshot from the Template box first.
40
40
  Threads can also be browsed and started from a terminal with
41
41
  `dvb agents [project]`. The project-wide switchboard groups threads by devbox
42
42
  and by Template box when available, shows live working/input/unread state, and
43
- starts Codex or Claude threads on the selected machine or a new devbox. Enter opens the
43
+ starts Codex or Claude threads on the selected box or a new devbox. Enter opens the
44
44
  thread's terminal interface; leaving that interface returns to the switchboard
45
45
  without creating another thread.
46
46
 
@@ -93,9 +93,8 @@ event renders.
93
93
 
94
94
  The switchboard can pin or unpin eligible Template-box threads and devbox
95
95
  anchors with `p`, rename with `r`, and archive or restore with `x`. Restoring a
96
- cold thread in an ordinary project opens a choice between a new devbox from the
97
- latest project snapshot and the existing Template-box path. A Team Template
98
- member project restores only to a new devbox from the saved version pinned when
96
+ cold thread in an independent project opens a choice between a new devbox from the
97
+ latest project snapshot and the existing Template-box path. A managed project restores only to a new devbox from the saved version pinned when
99
98
  restore begins. Codex
100
99
  archive updates its saved native session first. Claude archive updates the
101
100
  shared thread list without waking the machine. Changes appear on desktop and
@@ -333,7 +332,7 @@ counts. Use **Reauthorize** or **Remove from Codex** / **Remove from Claude**
333
332
  from an agent chip's menu, and the row's own **⋯** menu to edit the definition
334
333
  and headers or to remove the connection entirely.
335
334
 
336
- In a Team Template member project, the centrally managed MCP list remains
335
+ In a managed project, the centrally managed MCP list remains
337
336
  available but the **Template-managed MCPs** inventory is omitted because the
338
337
  member has no Template box. Rows marked **Team Template** follow live team
339
338
  definitions and cannot be edited or removed by members. **Connection details**
@@ -461,7 +460,7 @@ an eligible public GitHub plugin managed for this project; an unsupported source
461
460
  stays installed only on the current box. The install is never blocked merely
462
461
  because boxes.dev cannot manage that plugin type for a project.
463
462
 
464
- Team Template member projects omit this project-wide Plugin page in the MVP
463
+ Managed projects omit this project-wide Plugin page in the MVP
465
464
  because its native inventory and marketplace actions require a personal
466
465
  Template box. A user or agent can still use the agent's native Plugin tooling
467
466
  on an exact devbox; that installation is local to that devbox.
@@ -516,13 +515,13 @@ saved somewhere else after the editor loaded it, the card says **These
516
515
  settings were changed elsewhere** and offers **Load latest**; make the change
517
516
  again on the loaded text.
518
517
 
519
- In a Team Template member project, the card also shows the template's settings
518
+ In a managed project, the card also shows the template's settings
520
519
  under **Team settings from <template name>**, which members can read but not
521
520
  edit. Every devbox in the project combines the team settings with the member's
522
521
  own. Where both set the same option, the member's value is used; Claude lists
523
522
  include the items from both, and a member's Codex list replaces the team's.
524
523
  Team admins edit the team settings on the Team Template page, and changes reach
525
- existing devboxes within a minute. An ordinary project created from a Team
524
+ existing devboxes within a minute. An independent project created from a Team
526
525
  Template receives a copy of the template's settings when it is created; later
527
526
  team changes don't reach it, and its owner edits that copy like any other
528
527
  project's settings. See `team-template.md`.
@@ -538,11 +537,11 @@ startup, the UI may show progress such as preparing the devbox, binding the
538
537
  thread, or sending the first message.
539
538
 
540
539
  Before a new-devbox draft is assigned its exact devbox, it belongs to the
541
- project rather than to the Template box. The desktop app keeps runtime status,
540
+ project rather than to the Template box. The desktop app keeps box status,
542
541
  Terminal, Files, Git/Review, Browser, Ports, and machine controls hidden during
543
542
  that period. Background preparation can still use the project's chosen
544
543
  reusable source; that preparation does not make a Template box or the preparing
545
- devbox the selected runtime. After placement, those controls follow the exact
544
+ devbox the selected box. After placement, those controls follow the exact
546
545
  new devbox. A draft explicitly created on an available Template box continues
547
546
  to select it normally.
548
547
 
@@ -586,7 +585,7 @@ managed in **Integrations → MCPs**, choose **Reauthorize** for Codex there onc
586
585
  boxes.dev applies the new sign-in to every devbox and the notice clears on its
587
586
  own. For an MCP installed directly on the Template box, reauthorize it under
588
587
  **Template-managed MCPs**, then take a snapshot so new devboxes will have it;
589
- existing devboxes keep running without that MCP. In a Team Template member
588
+ existing devboxes keep running without that MCP. In a managed
590
589
  project, a Template admin repairs a machine-local MCP inherited in the saved
591
590
  environment. Centrally managed Team Template definitions
592
591
  still use the member's own per-agent sign-in and **Reauthorize** action.
@@ -618,7 +617,7 @@ When an agent intends a local file or directory in its final response to be
618
617
  navigable, it presents that exact target as a clickable link that opens in the
619
618
  boxes.dev file viewer.
620
619
 
621
- Desktop file attachments are staged into the selected runtime and can be up to
620
+ Desktop file attachments are staged into the selected box and can be up to
622
621
  5 GiB each, with up to 10 GiB of active uploads per user at a time. Image
623
622
  attachments still follow the selected agent's image input limits.
624
623
 
@@ -697,7 +696,7 @@ Dismissing won't resend the message, cancel agent work, or
697
696
  delete saved conversation history. It will persist after reopening the
698
697
  thread, and later successful sends won't dismiss earlier warnings.
699
698
 
700
- If a thread is blocked because the selected runtime is sleeping, not ready, or
699
+ If a thread is blocked because the selected box is sleeping, not ready, or
701
700
  missing auth, the composer shows the reason and any available repair action.
702
701
 
703
702
  ## Codex Controls
@@ -997,10 +996,10 @@ or the CLI. These are two views of the same conversation, not separate thread
997
996
  types. Every new-thread entry point first opens a draft on the location that
998
997
  entry point already chose. The prominent selector changes the agent; the quiet
999
998
  **Start in the CLI** or **Back to the GUI composer** action changes the draft
1000
- view without asking for the runtime target again.
999
+ view without asking for the target box again.
1001
1000
 
1002
1001
  A GUI draft has the normal composer. A CLI draft has no composer and uses
1003
- **Open CLI** to commit the draft to the selected runtime; the first prompt
1002
+ **Open CLI** to commit the draft to the selected box; the first prompt
1004
1003
  is then typed directly into the agent's interactive terminal. Merely selecting
1005
1004
  the CLI view keeps any GUI draft text and attachments intact in case the user
1006
1005
  returns to GUI. **Open CLI** warns before discarding GUI-only text,
@@ -1108,6 +1107,26 @@ Mobile shows each existing devbox's archive inside its
1108
1107
  group and every other archived chat in one **Archived threads** list at the
1109
1108
  end of the project. `dvb agents` keeps a single archived section.
1110
1109
 
1110
+ Threads are sorted by the user's last message by default. **Sort threads**, in
1111
+ **Account → Threads** on desktop and **Settings → Threads** on mobile, sets the
1112
+ order for the whole account, so every computer and phone follows it:
1113
+
1114
+ - **Your last message** sorts by the last message the user sent, or by when
1115
+ the thread was created.
1116
+ - **Last activity** also moves a thread up when its agent finishes, fails, or
1117
+ stops a turn, or asks the user a question. Output streaming in while the
1118
+ agent works does not move it.
1119
+ - **Working first** puts threads with an agent working at the top and sorts
1120
+ the rest by last activity. The desktop Devboxes list and the mobile list show
1121
+ them under a **Working** heading; inside a folder or the Template box section
1122
+ they come first without a heading. A devbox with any working thread moves up
1123
+ with its whole group. A thread waiting for the user's answer shows its
1124
+ needs-input state and stays in place by activity.
1125
+
1126
+ The order applies to recent threads, folders, devbox groups, the Template box
1127
+ section, and archived threads. Pinned threads keep their own order. In the
1128
+ activity orders, each row's time and date group show its last activity.
1129
+
1111
1130
  Rows show status indicators for draft, starting, active, unread, idle, archived,
1112
1131
  and cold-storage states. Devbox rows also show devbox context and devbox runtime
1113
1132
  status where relevant.
@@ -1241,8 +1260,8 @@ The thread action menu can include:
1241
1260
  - Rename thread.
1242
1261
  - Mute notifications or Unmute notifications.
1243
1262
  - Archive thread or Unarchive thread.
1244
- - Restore thread for an archived cold-storage thread. Ordinary projects offer
1245
- To new devbox and To Template box; Team Template member projects offer only
1263
+ - Restore thread for an archived cold-storage thread. Independent projects offer
1264
+ To new devbox and To Template box; managed projects offer only
1246
1265
  To new devbox.
1247
1266
  - Copy transcript, which copies user messages and final agent replies as
1248
1267
  structured Markdown.
@@ -1270,7 +1289,7 @@ starting. The chosen name stays after startup finishes.
1270
1289
  Destroy and archive preserves eligible thread history directly in cold storage
1271
1290
  before deleting the devbox. The archived history stays readable without waking
1272
1291
  a machine. Restore an individual thread to a new devbox from the project's
1273
- current reusable source or, in an ordinary project, to the current Template
1292
+ current reusable source or, in an independent project, to the current Template
1274
1293
  box; either path returns it to the normal thread list. If boxes.dev cannot safely preserve the history
1275
1294
  because the devbox connection is unavailable, it keeps the devbox and thread
1276
1295
  and reports the failure instead of deleting the source.