@boxes-dev/dvb-runtime 1.0.945 → 1.0.946

package/dist/bin/dvb.mjs

@@ -101145,8 +101145,8 @@ var init_otel = __esm({
       return trimmed && trimmed.length > 0 ? trimmed : void 0;
     };
     readBuildMetadata = () => {
-      const rawPackageVersion = "1.0.945";
-      const rawGitSha = "d62fc40ab3d930ef251a963d96ff089c3a14693c";
+      const rawPackageVersion = "1.0.946";
+      const rawGitSha = "02ae8375bf2cc6661ce7e4be45a508564d6f7583";
       const packageVersion = typeof rawPackageVersion === "string" ? rawPackageVersion : void 0;
       const gitSha = typeof rawGitSha === "string" ? rawGitSha : void 0;
       return { packageVersion, gitSha };
@@ -133552,9 +133552,9 @@ var init_sentry = __esm({
     uncaughtExceptionMonitorInstalled = false;
     currentDevboxSentryUser = null;
     readBuildMetadata2 = () => {
-      const rawPackageVersion = "1.0.945";
-      const rawGitSha = "d62fc40ab3d930ef251a963d96ff089c3a14693c";
-      const rawSentryRelease = "boxes-dev-dvb@1.0.945+d62fc40ab3d930ef251a963d96ff089c3a14693c";
+      const rawPackageVersion = "1.0.946";
+      const rawGitSha = "02ae8375bf2cc6661ce7e4be45a508564d6f7583";
+      const rawSentryRelease = "boxes-dev-dvb@1.0.946+02ae8375bf2cc6661ce7e4be45a508564d6f7583";
       const packageVersion = typeof rawPackageVersion === "string" ? rawPackageVersion : void 0;
       const gitSha = typeof rawGitSha === "string" ? rawGitSha : void 0;
       const sentryRelease = typeof rawSentryRelease === "string" ? rawSentryRelease : void 0;
@@ -138717,7 +138717,7 @@ var init_packageVersion = __esm({
       return path17.join(process.cwd(), "dvb");
     };
     readEmbeddedPackageVersion = () => {
-      const raw = "1.0.945";
+      const raw = "1.0.946";
       return trimVersion(raw);
     };
     readNearestPackageMetadata = (basePath) => {

package/dist/bin/dvbd.mjs

@@ -96328,8 +96328,8 @@ var init_otel = __esm({
       return trimmed && trimmed.length > 0 ? trimmed : void 0;
     };
     readBuildMetadata = () => {
-      const rawPackageVersion = "1.0.945";
-      const rawGitSha = "d62fc40ab3d930ef251a963d96ff089c3a14693c";
+      const rawPackageVersion = "1.0.946";
+      const rawGitSha = "02ae8375bf2cc6661ce7e4be45a508564d6f7583";
       const packageVersion = typeof rawPackageVersion === "string" ? rawPackageVersion : void 0;
       const gitSha = typeof rawGitSha === "string" ? rawGitSha : void 0;
       return { packageVersion, gitSha };
@@ -128624,9 +128624,9 @@ var init_sentry = __esm({
     uncaughtExceptionMonitorInstalled = false;
     currentDevboxSentryUser = null;
     readBuildMetadata2 = () => {
-      const rawPackageVersion = "1.0.945";
-      const rawGitSha = "d62fc40ab3d930ef251a963d96ff089c3a14693c";
-      const rawSentryRelease = "boxes-dev-dvb@1.0.945+d62fc40ab3d930ef251a963d96ff089c3a14693c";
+      const rawPackageVersion = "1.0.946";
+      const rawGitSha = "02ae8375bf2cc6661ce7e4be45a508564d6f7583";
+      const rawSentryRelease = "boxes-dev-dvb@1.0.946+02ae8375bf2cc6661ce7e4be45a508564d6f7583";
       const packageVersion = typeof rawPackageVersion === "string" ? rawPackageVersion : void 0;
       const gitSha = typeof rawGitSha === "string" ? rawGitSha : void 0;
       const sentryRelease = typeof rawSentryRelease === "string" ? rawSentryRelease : void 0;
@@ -130818,7 +130818,7 @@ var init_packageVersion = __esm({
       return path8.join(process.cwd(), "dvb");
     };
     readEmbeddedPackageVersion = () => {
-      const raw = "1.0.945";
+      const raw = "1.0.946";
       return trimVersion(raw);
     };
     readNearestPackageMetadata = (basePath) => {

package/dist/product-docs/references/desktop-workbench.md

@@ -177,15 +177,16 @@ Template**; project creation does not start from the template detail page.
 Only one admin can edit a particular Team Template at a time; different
 templates have independent editing locks and release histories. **Take
 control** creates a private editing machine for the selected template, and
-**Continue editing** wakes that same machine after it sleeps. The dedicated
-workbench includes Terminal, Files, Git, and Browser, but it deliberately has
-no agent threads, thread composer, devbox creation, project setup completion,
-ordinary snapshot, restore, or reset actions.
-
-Use **Pause editing** to put the editing machine to sleep without giving up the
-checkout. **Discard changes** permanently destroys that checkout and every
-unsaved change while leaving the selected template's current release
-unchanged. Other team admins can see who holds a sleeping checkout and must
+**Continue editing** wakes that same machine after it sleeps. The editor uses
+the same workbench arrangement as a project — threads on the left, the selected
+conversation in the middle, and Terminal, Files, Git, or Browser on the right —
+but it deliberately has no devbox creation, project setup completion, ordinary
+snapshot, restore, or reset actions.
+
+Open the editing machine's status in the editor titlebar to pause it, which
+puts the machine to sleep without giving up the checkout. **Discard changes**
+permanently destroys that checkout and every unsaved change while leaving the
+selected template's current release unchanged. Other team admins can see who holds a sleeping checkout and must
 explicitly resolve the holder's changes before taking control. Team members can
 see safe current release information but cannot connect to the editing machine.
 

package/dist/product-docs/references/team-template.md

@@ -29,12 +29,12 @@ Templates have independent editing locks, so an admin can prepare more than one
 without crossing their files or release history. An editing session remains
 assigned to its admin if the desktop app closes or the machine sleeps.
 
-An admin can use an ordinary project Template box to host a Codex or Claude
-thread that helps with the Team Template checkout. The Team Template editor's
-**Agent** pane selects the exact source project and creates the ordinary thread
-there. The agent stays on that source box and reaches only the current editing
-session through the boxes.dev Team Template CLI; boxes.dev does not install the
-admin's agent credentials into the Team Template.
+An admin can create multiple Codex and Claude threads directly in the Team
+Template editor. These threads belong to the Team Template definition, not its
+temporary editing machine. They are private to the admin who created them for
+now. Agent credentials, native session files, and other private agent state are
+kept outside the Team Template's authored filesystem and are never copied into
+a release or a project created from it.
 
 ## Finding And Managing Team Templates
 
@@ -120,51 +120,46 @@ state are never copied.
 ## Editing And Publishing
 
 Open a Team Template, then choose **Take control** to start an editing session.
-The focused, full-window editor shows the source release and session age. It
-supports Terminal, Files, Git, Browser, and Agent panes, but it is not an
-ordinary project workbench: it does not host Codex or Claude itself, create
-devboxes, or offer normal project snapshot, restore, or reset controls.
-Use **Pause editing** to sleep the machine while keeping both the checkout and
-unsaved files for the same admin.
-
-The **Agent** pane currently supports one active chat for the editing session.
-Choose Codex or Claude and one of your eligible projects, then choose **Start
-agent**. The chat is an ordinary thread running on that project's Template box:
-normal shell commands affect the project, while Team Template CLI commands act
-on the editing machine. The pane always shows the source project and Team
-Template target above the chat. Agents and other processes on the selected
-source Template box can use the same checkout access while it is active.
-
-The agent can run bounded noninteractive commands against the checkout and can
-push one regular file from the project Template box into `/home/boxes` on the
-Team Template. A push is limited to 100 MiB, rejects directories and symbolic
-links, and does not replace an existing destination unless overwrite is
-explicit. Use this when a file already available in the source project should
-become part of the Team Template; ordinary shell commands on the source box do
-not move it automatically.
-
-Choosing **Stop agent** immediately ends permission to start another Team
-Template command. boxes.dev also asks the ordinary agent turn to stop, but a
-broken or slow source chat does not hold the editor open. The Team Template box
-waits for a command that already started there, then confirms that no delayed
-command can change the checkout before returning the Agent pane to setup.
-Switching panes or closing and reopening the desktop app does not end access on
-its own. The ordinary thread and transcript remain in the source project after
-Stop or after editing ends; they are never copied into the Team Template or a
-project created from its release.
+The focused, full-window editor uses the same workbench arrangement as a
+project: Team Template threads on the left, the selected Codex or Claude
+conversation in the middle, and the Terminal, Files, Git, or Browser tool on
+the right. Its single titlebar row carries the template name, the source
+release, the session age, the editing machine's status, **Save and close**,
+**Discard**, and the tool switcher. Each column can be resized, and the tool
+pane can be closed or expanded to fill the window; that layout is remembered
+per Team Template. The editor does not create devboxes or offer normal project
+snapshot, restore, reset, automation, Project URL, or sharing controls.
+
+Open the editing machine's status to pause it. Pausing sleeps the machine while
+keeping both the checkout and unsaved files for the same admin, and the machine
+also pauses on its own after a period of inactivity. Choose **Continue
+editing** to wake it.
+
+Until a thread is selected, the middle of the editor is the editing machine's
+terminal, because preparing files is usually the first thing an admin does.
+Choose the new-thread control in the thread list, then choose Codex or Claude.
+Threads support the same conversation, file attachment, and agent controls as
+an ordinary devbox thread. Thread forks, delegated threads, devbox creation,
+and other project-only actions are unavailable. More than one thread can exist
+and run against the current checkout.
+
+The conversation and the checkout filesystem are separate. Saving or
+discarding does not attempt to prove that the files still match what an agent
+saw. Before the editing machine is destroyed, boxes.dev saves the native
+session files for every restorable Team Template thread. The next time the same
+Team Template is edited, select a saved thread and restore it onto the current
+checkout. An untouched draft can simply be started on the current checkout.
 
 When editing is finished, choose one of these actions:
 
-- **Save and close** is available only after the admin explicitly stops the
-  agent. It closes terminal and browser sessions, removes
-  boxes.dev-managed state, runs the team's release cleanup script if one is
-  configured, and captures and verifies the next immutable release before
-  making it active. Before cleanup or capture, the Team Template box performs a
-  final checkout-wide check that all agent operations have finished. Saving
-  continues if the admin closes the window.
+- **Save and close** closes terminal and browser sessions, waits for active
+  agent work to settle, saves restorable Team Template threads, removes private
+  boxes.dev-managed agent state, runs the team's release cleanup script if one
+  is configured, and captures and verifies the next immutable release before
+  making it active. Saving continues if the admin closes the window.
 - **Discard changes** destroys the editing session and keeps the previous
-  active release unchanged. Agent access is fenced immediately, and the
-  confirmation requires typing `DISCARD`.
+  active release unchanged. Active agent work is fenced and restorable threads
+  are saved before teardown. The confirmation requires typing `DISCARD`.
 
 Members can continue creating projects from that template's active release
 while an admin edits a future release. Admins can also make an older ready

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@boxes-dev/dvb-runtime",
-  "version": "1.0.945",
+  "version": "1.0.946",
   "type": "module",
   "license": "UNLICENSED",
   "imports": {
@@ -81,5 +81,5 @@
     "e2b": "^2.18.0",
     "ink-testing-library": "^4.0.0"
   },
-  "devboxReleasedAt": "2026-08-21T22:44:23Z"
+  "devboxReleasedAt": "2026-08-22T01:08:01Z"
 }