@boxes-dev/dvb-runtime 1.0.1008 → 1.0.1009

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/bin/dvbd.mjs CHANGED
@@ -1,6 +1,6 @@
1
1
  #!/usr/bin/env node
2
2
 
3
- !function(){try{var e="undefined"!=typeof window?window:"undefined"!=typeof global?global:"undefined"!=typeof globalThis?globalThis:"undefined"!=typeof self?self:{},n=(new e.Error).stack;n&&(e._sentryDebugIds=e._sentryDebugIds||{},e._sentryDebugIds[n]="49bc38b5-e23d-5554-bc6a-27478afbfa6a")}catch(e){}}();
3
+ !function(){try{var e="undefined"!=typeof window?window:"undefined"!=typeof global?global:"undefined"!=typeof globalThis?globalThis:"undefined"!=typeof self?self:{},n=(new e.Error).stack;n&&(e._sentryDebugIds=e._sentryDebugIds||{},e._sentryDebugIds[n]="f3c47817-8f4f-5cb9-ab66-7683977843e9")}catch(e){}}();
4
4
  import { createRequire as __dvbCreateRequire } from "node:module";
5
5
  import { dirname as __dvbDirname } from "node:path";
6
6
  import { fileURLToPath as __dvbFileURLToPath } from "node:url";
@@ -96328,8 +96328,8 @@ var init_otel = __esm({
96328
96328
  return trimmed && trimmed.length > 0 ? trimmed : void 0;
96329
96329
  };
96330
96330
  readBuildMetadata = () => {
96331
- const rawPackageVersion = "1.0.1008";
96332
- const rawGitSha = "34cdee1a250021dd763121c21f58cfd30585ca83";
96331
+ const rawPackageVersion = "1.0.1009";
96332
+ const rawGitSha = "5ef03694fddc51d70b468162766e2fc4646e7602";
96333
96333
  const packageVersion = typeof rawPackageVersion === "string" ? rawPackageVersion : void 0;
96334
96334
  const gitSha = typeof rawGitSha === "string" ? rawGitSha : void 0;
96335
96335
  return { packageVersion, gitSha };
@@ -128624,9 +128624,9 @@ var init_sentry = __esm({
128624
128624
  uncaughtExceptionMonitorInstalled = false;
128625
128625
  currentDevboxSentryUser = null;
128626
128626
  readBuildMetadata2 = () => {
128627
- const rawPackageVersion = "1.0.1008";
128628
- const rawGitSha = "34cdee1a250021dd763121c21f58cfd30585ca83";
128629
- const rawSentryRelease = "boxes-dev-dvb@1.0.1008+34cdee1a250021dd763121c21f58cfd30585ca83";
128627
+ const rawPackageVersion = "1.0.1009";
128628
+ const rawGitSha = "5ef03694fddc51d70b468162766e2fc4646e7602";
128629
+ const rawSentryRelease = "boxes-dev-dvb@1.0.1009+5ef03694fddc51d70b468162766e2fc4646e7602";
128630
128630
  const packageVersion = typeof rawPackageVersion === "string" ? rawPackageVersion : void 0;
128631
128631
  const gitSha = typeof rawGitSha === "string" ? rawGitSha : void 0;
128632
128632
  const sentryRelease = typeof rawSentryRelease === "string" ? rawSentryRelease : void 0;
@@ -130826,7 +130826,7 @@ var init_packageVersion = __esm({
130826
130826
  return path8.join(process.cwd(), "dvb");
130827
130827
  };
130828
130828
  readEmbeddedPackageVersion = () => {
130829
- const raw = "1.0.1008";
130829
+ const raw = "1.0.1009";
130830
130830
  return trimVersion(raw);
130831
130831
  };
130832
130832
  readNearestPackageMetadata = (basePath) => {
@@ -144021,4 +144021,4 @@ long/umd/index.js:
144021
144021
  *)
144022
144022
  */
144023
144023
 
144024
- //# debugId=49bc38b5-e23d-5554-bc6a-27478afbfa6a
144024
+ //# debugId=f3c47817-8f4f-5cb9-ab66-7683977843e9
@@ -18,6 +18,9 @@ The workbench has a few persistent areas:
18
18
  a Template box or devbox is selected, and ends with the
19
19
  Terminal/Files/Git/Review/Browser pane control as icon-only buttons that show
20
20
  their names on hover; update notices appear in the middle when available.
21
+ If the app loses its connection, an Offline or Reconnecting badge appears
22
+ beside the pane control and clears on its own once boxes.dev is reachable
23
+ again.
21
24
  - The left pane lists threads, integrations, automations, Project URLs, an
22
25
  expandable Settings section, and the Template box when that project has one.
23
26
  Your account identity and a Help button stay pinned at the bottom.
@@ -132,6 +135,12 @@ section without changing its normal thread and devbox workflow.
132
135
  Use **New project...** in the project selector to add another project. On
133
136
  macOS, **File > New Project...** does the same thing.
134
137
 
138
+ **Manage projects...** in the project selector opens a page that lists all of
139
+ your projects with when each was last used and whether its setup is still in
140
+ progress. From there, **Open** switches the workbench to that project and
141
+ **Delete** removes it after you type its name to confirm. Deleting a project
142
+ also removes its files from this computer.
143
+
135
144
  When team access is enabled, **Teammates' projects** opens another team
136
145
  member's project in the read-only Team workbench. Team admins also see **Team
137
146
  Templates**, with shortcuts to manage non-archived templates, create one, or
@@ -237,6 +246,14 @@ threads, new-devbox placeholders, and automation views all use the same detail
237
246
  area. A Codex or Claude thread can switch between GUI and the CLI from its
238
247
  header without becoming a different thread.
239
248
 
249
+ Claude's active and recently finished subagents appear above the composer.
250
+ Open an agent from that list or its launch card to read its transcript, and use
251
+ **Back** or **Escape** to return to the parent thread and focus its composer.
252
+ Both views open at the bottom; any unsent parent message stays in the composer.
253
+ The list updates as Claude works, and
254
+ finished agents leave it after your next message. The inspector is read-only.
255
+ Older conversations may not have a subagent list.
256
+
240
257
  To distinguish Claude and Codex threads at a glance, turn on **Show agent
241
258
  logos** in **Desktop app settings > General > Thread List**. The logos appear
242
259
  at the right edge of thread rows and are off by default.
@@ -17,6 +17,11 @@ targets are not supported. The admin can add instructions for finding or
17
17
  exporting the file, but cannot upload, reveal, download, or inspect any
18
18
  member's contents or plaintext-derived metadata.
19
19
 
20
+ Agents can edit these definitions through `dvb-onbox team-template member-files`
21
+ in an authorized Team Template editing session. See
22
+ [Member-file requirements](onbox-agent-tools.md#member-file-requirements) for
23
+ commands and revision handling.
24
+
20
25
  Every requirement is required. A member selects the local file while creating
21
26
  the project. The original local filename is used only in that browser view and
22
27
  is not saved by boxes.dev. Files may contain arbitrary bytes and can be up to
@@ -224,6 +224,8 @@ Mobile settings include:
224
224
 
225
225
  - account sign-in and sign-out;
226
226
  - billing usage summary;
227
+ - an invite link and QR code you can share with someone who wants to try
228
+ boxes.dev (the same link is on the Account page in the web app);
227
229
  - unread app icon badge preference;
228
230
  - theme, monospace font, and thread text size;
229
231
  - release package details and refresh controls in installed builds;
@@ -609,11 +609,12 @@ dvb-onbox devboxes folders move \
609
609
  ```
610
610
 
611
611
  Use `--clear` instead of `--folder` to return the devbox to the unfiled date
612
- sections. In addition to `current`, `--devbox` accepts the exact ID of a new
612
+ sections. `current` identifies the devbox running the agent, including a devbox
613
+ created for an automation run. `--devbox` also accepts the exact ID of a new
613
614
  devbox directly created by this source thread through `dvb-onbox threads start`.
614
- The Template box cannot move itself. Sibling, manually created, automation,
615
- indirect, stale, cross-project, and cross-owner devboxes fail without revealing
616
- whether another target exists.
615
+ The Template box cannot move itself. Sibling, manually created, indirect, stale,
616
+ cross-project, and cross-owner devboxes fail without revealing whether another
617
+ target exists.
617
618
 
618
619
  `folder_revision_conflict` means another person or agent changed the membership.
619
620
  Run `get` again and reconsider the operation; moves never overwrite a newer
@@ -720,6 +721,43 @@ the file is missing, run the ordinary OAuth flow unchanged.
720
721
 
721
722
  ## Team Template Commands
722
723
 
724
+ ### Member-file requirements
725
+
726
+ An admin can list, add, update, and remove the files members need to provide for
727
+ a Team Template. Run these commands in its current editing box. From an ordinary
728
+ Template box with an active editor association, add `--template <team-template-id>`
729
+ to select that associated Team Template. Every operation edits the Team
730
+ Template; it does not add requirements to the caller's ordinary project.
731
+
732
+ ```bash
733
+ dvb-onbox team-template member-files list --json
734
+ dvb-onbox team-template member-files add \
735
+ --root home --path .convex/config.json \
736
+ --instructions 'Sign in to Convex on your computer, then upload ~/.convex/config.json.' \
737
+ --json
738
+ dvb-onbox team-template member-files update \
739
+ --file <file-id> --if-revision <definition-revision> \
740
+ --instructions 'Upload your personal Convex configuration file.' --json
741
+ dvb-onbox team-template member-files remove \
742
+ --file <file-id> --if-revision <definition-revision> --json
743
+ ```
744
+
745
+ `add` requires `--root home|project` and a relative `--path`. Optional
746
+ `--display-order` sets a nonnegative position; new requirements otherwise go
747
+ after existing ones. `update` accepts any of `--root`, `--path`, `--instructions`,
748
+ `--clear-instructions`, and `--display-order`; omitted settings stay unchanged.
749
+ List first and use the returned file ID and definition revision for updates
750
+ and removals. After an uncertain response, list again to inspect the outcome
751
+ before retrying a change.
752
+
753
+ Definitions take effect independently of saving a filesystem version. Existing
754
+ Member projects follow these requirements, and a missing file will block their
755
+ next startup. Changing a destination will require members to approve the new
756
+ destination or upload a replacement. Changing instructions will not require
757
+ destination approval. See [Member files](member-managed-files.md) for upload
758
+ and delivery behavior. These commands return definitions only and do not
759
+ upload or read a member's file contents.
760
+
723
761
  ### Create a Team Template from this project
724
762
 
725
763
  A team admin can ask an agent on an ordinary project's Template box to create
@@ -115,6 +115,41 @@ untracked files, Git access, agent config, and so on) — and reviews it with
115
115
  the user. The manifest lives outside the repo, so setup leaves no changes in
116
116
  the project folder, and the user can read or edit it directly at any time.
117
117
 
118
+ The manifest can explicitly select environment files outside the project.
119
+ Environment, secret, configuration, and extra file entries can also name an
120
+ edited copy to upload while leaving the laptop original untouched. Bash and
121
+ Zsh startup files are optional individual choices; selected shell content is
122
+ adapted for Linux without replacing the Template box's managed shell setup.
123
+ Removing a file entry removes that explicit copy, but repository copying or
124
+ the separate untracked-file selection may still include the file.
125
+
126
+ For a folder containing several repositories, agent setup can select those
127
+ repositories separately from ordinary files and folders alongside them.
128
+ Automatic GitHub access remains the default for GitHub repositories. SSH setup
129
+ uses one key for the selected repositories that need it, including child
130
+ repositories and repositories on other hosts; the key needs access on each
131
+ host. Automatic GitHub access and SSH for another host can be used together.
132
+
133
+ `start` and `check` explain when this folder overlaps an existing boxes.dev
134
+ project and list repositories skipped during discovery, with reasons. Review
135
+ these with the coding agent before approving the launch.
136
+
137
+ Conversation discovery initially lists the selected repositories and their
138
+ Git worktrees. Use `dvb agent-init detect agent-threads --all` to find and
139
+ optionally select conversations from other projects as well. Import remains
140
+ optional and starts with no conversations selected.
141
+
142
+ `dvb agent-init github cli status` shows the existing account setting for
143
+ signing the `gh` command into your connected GitHub account on your boxes.
144
+ Use `github cli enable` or `github cli disable` to change it. This choice
145
+ applies across projects and is separate from Git pull and push access.
146
+
147
+ Agent setup can choose separately whether to copy edits to tracked files and
148
+ files that Git has not tracked. Custom file rules can keep the usual dependency
149
+ and cache exclusions while adding exceptions, and apply to every eligible
150
+ file even when a large folder's displayed listing is shortened. Git-ignored
151
+ files need a named file selection if you want to copy them.
152
+
118
153
  The desktop app's Project step offers **Set up with your coding agent** beside
119
154
  local-folder setup. It shows a prompt to copy into Codex or Claude Code in the
120
155
  local project folder. When the remote setup thread starts, the agent offers to
@@ -579,9 +614,10 @@ When setup sees that the selected repo already signs commits, the desktop app
579
614
  also offers Git commit signing setup in this Git access step. The choices are to
580
615
  skip signing setup, create a boxes.dev signing key on the user's computer and
581
616
  upload it to the Template box, or opt in to copying existing signing material.
582
- Create mode supports OpenPGP signing and SSH signing; SSH signing reuses the
583
- Template box Git SSH key only when SSH access is selected. Managed HTTPS does
584
- not create an SSH key to reuse. Copy mode can move private signing key material
617
+ Create mode supports OpenPGP signing and SSH signing. SSH signing uses a
618
+ boxes.dev SSH key; when repository access also uses SSH, the same key can serve
619
+ both purposes. Signing also works when repository access uses HTTPS or is
620
+ skipped. Copy mode can move private signing key material
585
621
  onto the Template box, so it requires an explicit confirmation.
586
622
 
587
623
  Passphrase-protected copied keys stay passphrase-protected. boxes.dev does not
@@ -591,6 +627,11 @@ for those repos. Setup verifies signed commits locally on the Template box, but
591
627
  Git host "Verified" badges still require the public signing key to be registered
592
628
  with the Git host.
593
629
 
630
+ In agent-driven setup, `run` prints the public signing key and the host's
631
+ registration instructions. Retrieve them again with `dvb agent-init status`,
632
+ including after setup finishes. Private keys are never printed. Signing
633
+ identifies the signer of a commit; it does not grant pull or push access.
634
+
594
635
  If the remote uses HTTPS, setup can switch the Template box copy of the repo to
595
636
  SSH after verification. Users can skip Git access and set it up later, but
596
637
  devbox work usually needs working `git pull` and `git push` to save or share
@@ -219,6 +219,20 @@ Manual, scheduled, and API automations can separately send selected events to
219
219
  Slack channels or linked-user DMs. Those output destinations can receive final
220
220
  output, needs-input, and failed-run events.
221
221
 
222
+ ## Shared Channel With boxes.dev
223
+
224
+ Some teams have a shared Slack Connect channel with the boxes.dev team for
225
+ quick questions. If your team has one available, open
226
+ `https://boxes.dev/app/slack-channel`, check the channel name and the email
227
+ address you use for Slack, and choose **Set up channel**. boxes.dev will
228
+ create the channel on its Slack workspace and send an invitation to that
229
+ address. Accept the invitation from Slack or from the email Slack sends, then
230
+ invite coworkers from inside the channel. If the invitation doesn't arrive,
231
+ send another one from the same page; it goes to the same channel.
232
+
233
+ This channel is separate from the Slack integration above and does not run
234
+ automations.
235
+
222
236
  ## Current Limits
223
237
 
224
238
  Slack triggers require an app mention or a 1:1 app DM. boxes.dev does not
@@ -79,51 +79,126 @@ fixed after creation and is inherited by projects made from it. Creating and
79
79
  preparing the entry does not create a usable saved version: an admin must
80
80
  inspect the machine and save it first.
81
81
 
82
- Open a template's detail page to inspect its **Latest saved version** and the
83
- compact **Previous versions** recovery section. Admins also manage its Project
84
- defaults, name, description, save cleanup script, **Member projects** settings,
85
- and archive state there. The detail page is for inspection and administration;
86
- members start projects from the normal new-project flow instead. Restore an
87
- archived Team Template before changing its Project defaults or running
82
+ Open a template's detail page to inspect and administer it; members start
83
+ projects from the normal new-project flow instead. For admins the page has six
84
+ cards, in the order an admin usually needs them:
85
+
86
+ - **Template environment**: the latest saved version, its repositories and
87
+ machine size, the editing status and **Take control** action, plus rows for
88
+ **Maintenance**, the **Cleanup before saving** script, and **Previous
89
+ versions**.
90
+ - **Member projects**: whether this template creates independent or managed
91
+ projects, and the **Pause new projects** / **Resume new projects** control
92
+ for managed templates.
93
+ - **When a new devbox is created**: the startup and teardown sequence with the
94
+ team and member scripts edited in place.
95
+ - **Environment and member files**: file definitions that managed projects
96
+ keep following and independent projects copy once.
97
+ - **Settings for new projects**: everything else copied into a project when it
98
+ is created.
99
+ - **Template settings**: name, description, and archive.
100
+
101
+ Restore an archived Team Template before changing these settings or running
88
102
  maintenance.
89
103
 
90
- The **Member projects** section controls projects whose devboxes use the Team
91
- Template's current saved files without giving each member a personal Template
92
- box. Enabling creation requires a current saved version, confirmation that no
93
- member-specific `.env` or `.env.local` files are needed, and a repository
104
+ The **Member projects** card explains which kind of project the template
105
+ creates. A template creates independent projects until an admin chooses **Set
106
+ up managed projects…**; the confirmation states that members will get no
107
+ Template box of their own, that new devboxes will start from the latest saved
108
+ version and run the team scripts, that members will no longer be able to
109
+ create independent projects from the template, and that this can't be undone.
110
+ Setting up managed projects requires a current saved version and a repository
94
111
  inventory with only remote-free, local, or standard `github.com` origins.
95
- Unsupported network origins remain valid for ordinary Team Template use while
96
- this mode is unused. Once creation is enabled or linked member projects exist,
97
- an unsupported origin blocks saving a new current version and identifies only
98
- the safe repository path and host.
99
-
100
- Disabling member creation prevents only new projects. Existing linked projects
101
- may continue to create devboxes and refill their prepared machines. The same
102
- section defines team-owned startup and teardown scripts for those devboxes.
103
- These scripts and the current saved files stay live for future machines;
104
- project behavior settings, Project URLs, MCP definitions, and integration
105
- requirements are copied once when each member project is created. Template-box
106
- setup instructions and maintenance do not apply to member projects. When
107
- integrations are included in initial setup, the project is registered first
108
- but its first warm devbox waits until the member finishes that stage. Startup
109
- can run on warm machines kept ready for members, so scripts should avoid
110
- unnecessary external side effects. Admins see aggregate linked-project and
111
- preparation health, never member credentials or detailed per-user output.
112
-
113
- ## Project Defaults
114
-
115
- The **Project defaults** card controls what future projects receive. Its
116
- editors cover setup instructions, devbox startup and teardown behavior, Team
117
- Template maintenance and GitHub watches, Git and port behavior, Project URLs,
118
- initial integration requirements, and project-scoped MCP connections.
112
+ Unsupported network origins remain valid for independent Team Template use.
113
+ Once managed projects are set up, an unsupported origin blocks saving a new
114
+ current version and identifies only the safe repository path and host.
115
+
116
+ For a managed template, **Pause new projects** stops new project creation only.
117
+ It does not change the template back to independent projects, and existing
118
+ linked projects keep working, create devboxes, and refill their prepared
119
+ machines. **Resume new projects** reverses it. When integrations are included
120
+ in initial setup, a new project is registered first but its first warm devbox
121
+ waits until the member finishes that stage. Admins see aggregate linked-project
122
+ and preparation health, never member credentials or a member's own output.
123
+
124
+ ## When A New Devbox Is Created
125
+
126
+ The **When a new devbox is created** card shows, in order, what happens when a
127
+ member's new devbox starts, with the scripts edited where they run. Every
128
+ script row states its timing, the directory it runs in, and the template's
129
+ repository paths, and each script is edited in place with **Add script** or
130
+ **Edit script**, then **Save script** or **Cancel**.
131
+
132
+ All of these scripts run in `/home/boxes`, the project root. When the saved
133
+ version contains exactly one repository in a subfolder, the agent itself starts
134
+ inside that repository, so scripts that touch the repository should name it,
135
+ for example `git -C sandbox fetch origin`.
136
+
137
+ For a managed template the startup sequence is:
138
+
139
+ 1. Start from the saved template.
140
+ 2. **Team preparation script** (optional, team-owned). It runs on a standby
141
+ machine before any member is assigned, so Git and the saved files are
142
+ available but the member's GitHub access and files are not. Saving applies
143
+ to later preparations for every managed project using the template. A
144
+ failure discards that machine; repeated failures stop automatic
145
+ preparation until a run succeeds.
146
+ 3. The prepared devbox may wait until a member needs it.
147
+ 4. boxes.dev prepares the member's configured connections and files.
148
+ 5. **Member startup script** (default for new projects). It runs once per new
149
+ devbox, before the first agent turn, with the member's configured GitHub
150
+ access and files ready. It is copied into each new project, and members
151
+ edit their own copy afterward; saving the default does not change existing
152
+ projects. A failure shows a warning and the devbox still starts.
153
+ 6. The first agent turn starts.
154
+
155
+ An independent template shows the same sequence without the team stages,
156
+ starting from the project's own Template box. Another thread on an existing
157
+ devbox, or waking one, does not run the sequence again.
158
+
159
+ **When a devbox is destroyed** expands the teardown order: the member teardown
160
+ script, removal of member credentials, the team teardown script, then destroy.
161
+ Each devbox runs the team teardown captured when it was prepared; saving that
162
+ script applies to later preparations. Unused or failed preparations may skip
163
+ the member teardown script.
164
+
165
+ If a team script fails, the page shows one attention line linking to the
166
+ failed stage, and that stage shows the failure, the script's output, and
167
+ whether standby preparation is stopped. **Edit script** and Save resume
168
+ preparation with the corrected script; **Retry saved script** runs the saved
169
+ script again and is unavailable while unsaved edits exist. Saving a script
170
+ records it; it does not run it or publish a new saved version.
171
+ When a later run of the same saved team script succeeds, its earlier failure
172
+ disappears from the page.
173
+
174
+ ## Environment And Member Files
175
+
176
+ The **Environment and member files** card holds the template's environment
177
+ file definitions and member file requirements. They have their own card
178
+ because they propagate by project type: a managed project keeps following the
179
+ template's current definitions, so changes and removals reach existing
180
+ managed projects and their next devboxes, while an independent project
181
+ receives a copy when it is created and keeps it. In both cases each member
182
+ enters the values marked as theirs. See `managed-environment-files.md` and
183
+ `member-managed-files.md` for the editors themselves.
184
+
185
+ ## Settings For New Projects
186
+
187
+ The **Settings for new projects** card controls everything else a new project
188
+ receives: initial integration requirements, agent defaults (agent guidance
189
+ and a first-prompt prefix), Git and port behavior, Project URLs,
190
+ project-scoped MCP connections, and setup instructions. Setup instructions
191
+ reach only independent projects; the row says so while the template creates
192
+ managed projects.
119
193
 
120
194
  Each editor saves independently and takes effect immediately for project
121
- creation. Saving a Project default does not save a new filesystem version and
122
- does not wait for the current editing session to close. Unsaved changes remain
123
- only in that focused editor; there is no configuration draft, filesystem save,
124
- history, or rollback. Existing projects never follow later Project-default
125
- changes. An ordinary project with its own Template box receives every
126
- applicable default; the Member-project subset is described above.
195
+ creation. Saving a setting does not save a new filesystem version and does not
196
+ wait for the current editing session to close. Unsaved changes remain only in
197
+ that focused editor; there is no configuration draft, filesystem save,
198
+ history, or rollback. Existing projects never follow later changes. An
199
+ independent project with its own Template box receives every applicable
200
+ setting; managed projects receive the same settings except setup instructions
201
+ and maintenance.
127
202
 
128
203
  Project URLs receive fresh hostnames in each new project. MCP defaults contain
129
204
  only connection details, never credentials or a Codex/Claude choice. A new
@@ -151,13 +226,13 @@ the resulting ordinary project afterward.
151
226
  While editing a Team Template, ask Codex or Claude to configure its maintenance
152
227
  script and GitHub watches with `dvb-onbox project maintenance get` and `apply`.
153
228
  These commands use the current admin's editing session, preserve repeating
154
- schedules, and save the same settings shown in **Project defaults →
229
+ schedules, and save the same settings shown in **Template environment →
155
230
  Maintenance**. Configuration does not run the script immediately. The agent
156
231
  can confirm the editing machine with `dvb-onbox box status --json`.
157
232
 
158
233
  Maintenance is real behavior for the Team Template, not only a preset for its
159
234
  children. An admin configures its script, schedule, and optional GitHub watches
160
- under **Project defaults**, or chooses **Run now**. boxes.dev wakes the clean
235
+ under **Template environment**, or chooses **Run now**. boxes.dev wakes the clean
161
236
  shared saved environment, uses short-lived repository-scoped GitHub App access,
162
237
  runs the script, removes those credentials, validates the cleaned result after
163
238
  a cold restart, saves it, and makes one new saved version current. A Team
@@ -252,9 +327,10 @@ version and does not preselect one. Before creation, the flow shows the
252
327
  exact version, machine size, and a read-only summary of the current Project
253
328
  defaults.
254
329
 
255
- If the Team Template has any GitHub maintenance watch, including a disabled
256
- watch, project creation requires the member's current boxes.dev GitHub
257
- connection and GitHub App access to every watched repository. The flow presents
330
+ For saved GitHub repositories, project creation checks the member's current
331
+ boxes.dev GitHub connection and pull/push access. Any GitHub maintenance watch,
332
+ including a disabled watch, also requires access to the watched repository.
333
+ The flow presents
258
334
  the existing connect, update-authorization, install, or grant-access action and
259
335
  does not allocate the Template box until access is satisfied.
260
336
 
@@ -286,6 +362,26 @@ the only startup status. Once the thread is running, only failed per-devbox
286
362
  setup such as Tailscale appears above the composer; setup that is still applying
287
363
  stays in the background without an extra checklist.
288
364
 
365
+ If the Team Template startup script fails, the desktop composer will explain
366
+ which template needs attention and keep your draft and attachments. Open
367
+ **View details** to inspect the script's failure and output, or use **Copy
368
+ details** to share them with a team admin. Admins can choose **Review startup
369
+ script** to open that template's startup setting directly. After the script
370
+ is fixed, send your message again.
371
+
372
+ After repeated startup failures, **Devbox creation is paused** will explain
373
+ why new devboxes cannot start. A team admin can use **Review startup script**
374
+ to open the **Team preparation script** under **When a new devbox is created**,
375
+ review it, and use **Retry saved script**.
376
+ Your draft and attachments will remain available while the team resolves it.
377
+
378
+ If boxes.dev cannot prepare the saved template or finish setup after the startup
379
+ script succeeds, the notice will explain which part failed. Open **View details**
380
+ and use **Copy details** to share the diagnostic with your team admin or boxes.dev
381
+ support. These setup errors do not necessarily mean the startup script needs to
382
+ change. If waiting for preparation times out, the notice will say that completion
383
+ could not be confirmed and your message was not sent; it will retain your draft.
384
+
289
385
  The new project is independent. Later Team Template versions, save cleanup, or
290
386
  leaving the team do not modify or remove the project's Template box,
291
387
  threads, snapshots, or devboxes. Creating it uses a normal project slot and its
@@ -325,13 +421,23 @@ are copied with the saved version. The destination project receives fresh
325
421
  boxes.dev project and repository identity instead of the saving admin's
326
422
  project identity.
327
423
 
328
- For SSH remotes, and for standard GitHub or GitLab HTTPS remotes, boxes.dev
329
- generates a fresh SSH key inside the destination Template box. The creation
330
- flow shows only its public key plus links and instructions for the detected
331
- hosts. Add that public key to each listed Git host, then choose **Verify
332
- access**. Recognized GitHub and GitLab HTTPS remotes use the verified key after
333
- this step. Generic HTTPS, local, and unusual remotes are preserved; finish any
334
- host-specific authentication from Terminal or with the setup agent.
424
+ New independent projects use your connected GitHub account for automatic HTTPS
425
+ access to the saved version's GitHub repositories. Creation checks your pull
426
+ and push access, then configures the project's Template box before saving its
427
+ initial snapshot. You do not need to register an SSH key for those repositories.
428
+ This covers a repository at the project root or repositories directly inside
429
+ it. Older saved versions without a repository inventory and custom nested
430
+ layouts retain their existing Git setup.
431
+
432
+ For other SSH remotes and standard GitLab HTTPS remotes, boxes.dev generates a
433
+ fresh SSH key inside the destination Template box. The creation flow shows its
434
+ public key plus instructions for the detected hosts. Add that public key to
435
+ each listed Git host, then choose **Verify access**. A project can use automatic
436
+ GitHub access while still needing this step for another host, including a
437
+ separate push destination or submodule. Generic HTTPS, local, and unusual
438
+ remotes are preserved; finish any host-specific authentication from Terminal
439
+ or with the setup agent. Projects with only non-GitHub repositories do not need
440
+ a GitHub connection unless another configured feature requires it.
335
441
 
336
442
  ## Files And Credentials Included In A Saved Version
337
443
 
@@ -347,11 +453,12 @@ The separate short-lived token used during editing is removed on pause and
347
453
  before saved-version capture. This does not cover SSH keys or credentials that
348
454
  an admin installs manually.
349
455
 
350
- Review the editing session and the save warning before saving. Configure a
351
- save cleanup script in the template's settings when the team intentionally
352
- wants to remove additional team-authored state. It runs after boxes.dev removes
353
- its own managed state; a nonzero exit stops the save instead of creating a
354
- partially cleaned version.
456
+ Review the editing session and the save warning before saving. Configure the
457
+ **Cleanup before saving** script under **Template environment** when the team
458
+ intentionally wants to remove additional team-authored state. It runs in
459
+ `/home/boxes` on the editing machine with network access disabled, before
460
+ boxes.dev removes its own managed state; a nonzero exit stops the save instead
461
+ of creating a partially cleaned version.
355
462
 
356
463
  ## Taking Over A Sleeping Edit
357
464
 
@@ -394,6 +394,12 @@ boxes.dev keeps the first prompt and its attachments while devbox and agent
394
394
  startup continue in the background. Reopening the thread shows its current
395
395
  startup progress or response; leaving the thread does not cancel the start.
396
396
 
397
+ On desktop, once boxes.dev has received your first message and its uploads,
398
+ startup continues even if you close or restart the app. You can send a follow-up
399
+ while the devbox is preparing; it stays after the first message. Keep the app
400
+ open while attachments are still uploading. A startup failure still shows an
401
+ error so you can decide whether to retry.
402
+
397
403
  If devbox preparation times out before Codex or Claude Code accepts the first
398
404
  prompt, boxes.dev returns the exact unsent prompt to the composer and shows a
399
405
  retryable error. The recovered prompt and error survive switching threads or
@@ -30,6 +30,10 @@ wrong, refresh the desktop app with Cmd+R or the app menu reload action. This
30
30
  often fixes minor glitches, especially around thread content and the thread
31
31
  list.
32
32
 
33
+ If the title bar shows an Offline or Reconnecting badge, the app itself cannot
34
+ reach boxes.dev. Threads and status will catch up on their own once the badge
35
+ clears, so check your network before reloading.
36
+
33
37
  If the selected Template box, devbox, or agent seems like it is in a bad state,
34
38
  use **Machine > Reset** from the menu bar. Reset kills all non-essential
35
39
  processes on the selected machine and restarts the boxes.dev daemon.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@boxes-dev/dvb-runtime",
3
- "version": "1.0.1008",
3
+ "version": "1.0.1009",
4
4
  "type": "module",
5
5
  "license": "UNLICENSED",
6
6
  "imports": {
@@ -77,5 +77,5 @@
77
77
  "e2b": "^2.18.0",
78
78
  "ink-testing-library": "^4.0.0"
79
79
  },
80
- "devboxReleasedAt": "2026-09-14T01:04:27Z"
80
+ "devboxReleasedAt": "2026-09-16T18:38:29Z"
81
81
  }