@boxes-dev/dvb-runtime 1.0.1056 → 1.0.1058

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]="7d72dc90-582f-5b5e-adc3-cf59e376ab6d")}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]="6358e715-5d10-5bd8-bcb8-b3b8fafb5add")}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";
@@ -45,6 +45,13 @@ var __toESM = (mod, isNodeMode, target) => (target = mod != null ? __create(__ge
45
45
  mod
46
46
  ));
47
47
 
48
+ // ../../../../shared/devboxCore/dist/embeddedIdeProtocol.js
49
+ var init_embeddedIdeProtocol = __esm({
50
+ "../../../../shared/devboxCore/dist/embeddedIdeProtocol.js"() {
51
+ "use strict";
52
+ }
53
+ });
54
+
48
55
  // ../../../../node_modules/ws/lib/constants.js
49
56
  var require_constants = __commonJS({
50
57
  "../../../../node_modules/ws/lib/constants.js"(exports, module2) {
@@ -64667,9 +64674,9 @@ var init_sentry = __esm({
64667
64674
  uncaughtExceptionMonitorInstalled = false;
64668
64675
  currentDevboxSentryUser = null;
64669
64676
  readBuildMetadata = () => {
64670
- const rawPackageVersion = "1.0.1056";
64671
- const rawGitSha = "935b29ca6791fbe82f8e55d4255be7abc44b3f89";
64672
- const rawSentryRelease = "boxes-dev-dvb@1.0.1056+935b29ca6791fbe82f8e55d4255be7abc44b3f89";
64677
+ const rawPackageVersion = "1.0.1058";
64678
+ const rawGitSha = "9ffbfb9429091920831dcdea454c86b1db35ea19";
64679
+ const rawSentryRelease = "boxes-dev-dvb@1.0.1058+9ffbfb9429091920831dcdea454c86b1db35ea19";
64673
64680
  const packageVersion = typeof rawPackageVersion === "string" ? rawPackageVersion : void 0;
64674
64681
  const gitSha = typeof rawGitSha === "string" ? rawGitSha : void 0;
64675
64682
  const sentryRelease = typeof rawSentryRelease === "string" ? rawSentryRelease : void 0;
@@ -65401,7 +65408,7 @@ var init_forkStartupScript = __esm({
65401
65408
  });
65402
65409
 
65403
65410
  // ../../../../shared/devboxCore/dist/ports.js
65404
- var MIN_PORT, MAX_PORT2, DEFAULT_MANAGED_SSH_PORT, E2B_MANAGED_SSH_PORT, RPCBIND_PORT, SPRITE_DAEMON_SESSION_PORT, PROJECT_URL_LOCAL_API_PORT, MANAGED_DAEMON_CONTROL_PORT, REMOTE_BROWSER_CDP_PORT, LOOPBACK_PRIVACY_CANARY_PORT, LOOPBACK_PRIVACY_WILDCARD_CONTROL_PORT, LOOPBACK_PRIVACY_MIGRATION_CONTROL_PORT, RESERVED_SYSTEM_PORTS, normalizePort, getManagedSshPort, isManagedSshPort, isReservedSystemPort, normalizeRange, mergeRanges, normalizePortSpec, mergePortSpecs, toRanges, subtractPortSpecs, isPortAllowed, parsePortSpec;
65411
+ var MIN_PORT, MAX_PORT2, DEFAULT_MANAGED_SSH_PORT, E2B_MANAGED_SSH_PORT, RPCBIND_PORT, SPRITE_DAEMON_SESSION_PORT, PROJECT_URL_LOCAL_API_PORT, MANAGED_DAEMON_CONTROL_PORT, REMOTE_BROWSER_CDP_PORT, LOOPBACK_PRIVACY_CANARY_PORT, LOOPBACK_PRIVACY_WILDCARD_CONTROL_PORT, LOOPBACK_PRIVACY_MIGRATION_CONTROL_PORT, EMBEDDED_IDE_SERVER_PORT, RESERVED_SYSTEM_PORTS, normalizePort, getManagedSshPort, isManagedSshPort, isReservedSystemPort, normalizeRange, mergeRanges, normalizePortSpec, mergePortSpecs, toRanges, subtractPortSpecs, isPortAllowed, parsePortSpec;
65405
65412
  var init_ports = __esm({
65406
65413
  "../../../../shared/devboxCore/dist/ports.js"() {
65407
65414
  "use strict";
@@ -65417,6 +65424,7 @@ var init_ports = __esm({
65417
65424
  LOOPBACK_PRIVACY_CANARY_PORT = 47824;
65418
65425
  LOOPBACK_PRIVACY_WILDCARD_CONTROL_PORT = 47825;
65419
65426
  LOOPBACK_PRIVACY_MIGRATION_CONTROL_PORT = 47826;
65427
+ EMBEDDED_IDE_SERVER_PORT = 47827;
65420
65428
  RESERVED_SYSTEM_PORTS = /* @__PURE__ */ new Set([
65421
65429
  DEFAULT_MANAGED_SSH_PORT,
65422
65430
  RPCBIND_PORT,
@@ -65427,7 +65435,8 @@ var init_ports = __esm({
65427
65435
  REMOTE_BROWSER_CDP_PORT,
65428
65436
  LOOPBACK_PRIVACY_CANARY_PORT,
65429
65437
  LOOPBACK_PRIVACY_WILDCARD_CONTROL_PORT,
65430
- LOOPBACK_PRIVACY_MIGRATION_CONTROL_PORT
65438
+ LOOPBACK_PRIVACY_MIGRATION_CONTROL_PORT,
65439
+ EMBEDDED_IDE_SERVER_PORT
65431
65440
  ]);
65432
65441
  normalizePort = (value) => {
65433
65442
  if (!Number.isInteger(value))
@@ -66884,7 +66893,7 @@ var init_packageVersion = __esm({
66884
66893
  return path8.join(process.cwd(), "dvb");
66885
66894
  };
66886
66895
  readEmbeddedPackageVersion = () => {
66887
- const raw = "1.0.1056";
66896
+ const raw = "1.0.1058";
66888
66897
  return trimVersion(raw);
66889
66898
  };
66890
66899
  readNearestPackageMetadata = (basePath) => {
@@ -67119,6 +67128,7 @@ var init_authRefresh = __esm({
67119
67128
  var init_dist3 = __esm({
67120
67129
  "../../../../shared/devboxCore/dist/index.js"() {
67121
67130
  "use strict";
67131
+ init_embeddedIdeProtocol();
67122
67132
  init_codexLocalRenderer();
67123
67133
  init_codexLocalImageFrame();
67124
67134
  init_mcpCommandImport();
@@ -80036,4 +80046,4 @@ smol-toml/dist/index.js:
80036
80046
  *)
80037
80047
  */
80038
80048
 
80039
- //# debugId=7d72dc90-582f-5b5e-adc3-cf59e376ab6d
80049
+ //# debugId=6358e715-5d10-5bd8-bcb8-b3b8fafb5add
@@ -214,7 +214,7 @@ viewed. The default is 20 recent turns; follow the returned opaque cursor for
214
214
  earlier pages. Current Codex and Claude transcripts are supported. Threads of
215
215
  the retired `claude_code` type return a typed `unsupported_agent` transcript status.
216
216
 
217
- Send a follow-up only when the canonical thread is idle:
217
+ Send a follow-up to the canonical thread:
218
218
 
219
219
  ```bash
220
220
  idempotency_key="$(node -p 'require("node:crypto").randomUUID()')"
@@ -226,12 +226,29 @@ dvb threads send \
226
226
  --json
227
227
  ```
228
228
 
229
- Agent sends never queue, steer, interrupt, or wait. An active turn returns a
230
- durable failed operation with `thread_busy`. A thread owned by a native Claude
231
- terminal returns `thread_controlled_elsewhere`; the command does not evict or
232
- take over that terminal. Retry an uncertain result only with the same key.
233
- `operation_indeterminate` means the request may have reached the agent and
234
- must not be submitted again under a new key.
229
+ By default, a send starts a turn when the thread is idle and otherwise queues
230
+ behind the active turn, so you don't need to wait for the thread before
231
+ sending. Choose a stricter behavior with `--delivery`:
232
+
233
+ | Value | Behavior |
234
+ | --- | --- |
235
+ | `next` | Starts a turn when the thread is idle, or queues behind the active turn. This is the default. |
236
+ | `idle` | Starts a turn only when the thread is idle. Active work returns `thread_busy`. |
237
+ | `queue` | Queues only behind active work. An idle thread returns `turn_not_active`. |
238
+ | `steer` | Adds the follow-up to the exact active Codex turn given by `--turn <active-turn-id>`. Claude doesn't support steering. |
239
+
240
+ `idle`, `queue`, and `steer` never fall back to another mode. The operation's
241
+ `disposition` reports what happened: `started` or `steered` with a `turnId`,
242
+ or `queued` without one. A queued follow-up starts after the active turn ends,
243
+ including when that turn is interrupted, and appears in `threads read` once it
244
+ starts. Take `<active-turn-id>` from the thread's `activeTurnId` in
245
+ `threads list`.
246
+
247
+ A Claude terminal that a person is using stays off limits: the send returns
248
+ `thread_controlled_elsewhere` and doesn't take over that terminal. Retry an
249
+ uncertain result only with the same key and identical arguments, including
250
+ `--delivery` and `--turn`. `operation_indeterminate` means the request may
251
+ have reached the agent and must not be submitted again under a new key.
235
252
 
236
253
  Wait for one exact turn without polling the devbox:
237
254
 
@@ -24,6 +24,10 @@ The workbench has a few persistent areas:
24
24
  - The left pane lists threads, integrations, automations, Project URLs, an
25
25
  expandable Settings section, and the Template box when that project has one.
26
26
  Your account identity and a Help button stay pinned at the bottom.
27
+ If you haven't signed in to the mobile app, a **Code on the go!** banner
28
+ appears above your account. Scan its QR code to download the mobile app, or
29
+ select **X** to dismiss it for this account on this computer. Signing in on
30
+ mobile will also hide the banner.
27
31
  - The detail pane shows the selected thread, Project settings, an integration,
28
32
  an automation editor, or the Template box page when available.
29
33
  - The Terminal, Files, Git/Review, and Browser panes can be shown next to the
@@ -448,7 +448,7 @@ The request values are `create-devboxes-and-threads`,
448
448
  `create-team-templates`, `update-thread-titles`,
449
449
  `move-devboxes-to-folders`, `create-devbox-folders`,
450
450
  `edit-devbox-lifecycle`, `edit-template-maintenance`, `destroy-devbox`,
451
- `read-project-threads`, `read-user-threads`, `read-shared-threads`,
451
+ `destroy-created-devboxes`, `read-project-threads`, `read-user-threads`, `read-shared-threads`,
452
452
  `read-team-threads`, `message-agents`, `edit-template-box`,
453
453
  `edit-team-template`, `edit-personal-environment`, and `edit-automations`.
454
454
  Add `--json` for a stable structured result.
@@ -825,7 +825,8 @@ devboxes and threads** permission is checked on every observation and control.
825
825
  Prompt files are limited to 32 KiB.
826
826
 
827
827
  Delegation does not grant destruction permission or access to unrelated
828
- threads. Read-only thread and project discovery has its own permission below.
828
+ threads. To clean up a devbox created this way, see
829
+ [Destroy And Archive Created Devboxes](#destroy-and-archive-created-devboxes). Read-only thread and project discovery has its own permission below.
829
830
  `dvb-onbox` does not expose arbitrary direct exec, services, or generic machine
830
831
  management. The current-box public link commands above are its only port-control
831
832
  surface.
@@ -876,6 +877,12 @@ boxes.dev thread link, or the thread's Codex thread ID or Claude session ID.
876
877
  Listings and reads report that agent ID as `nativeThreadId`. If an agent ID
877
878
  matches more than one thread you can read, use the thread's `id` instead.
878
879
 
880
+ **Copy thread ID** in a teammate thread's `…` menu copies an ID for
881
+ `read --thread`. A `tsh_...` ID, copied from a share-link page, needs
882
+ `--scope shared`. A `thr_...` ID works with `--scope shared` when the user
883
+ opened that thread's invitation link, and with `--scope team` when team
884
+ settings allow reading it.
885
+
879
886
  Reads return stored visible user/assistant messages with older-page cursors.
880
887
  They may lag active work and shorten long messages. They do not wake boxes,
881
888
  mark threads read, claim links, or expose full tool logs. Without `--scope`,
@@ -972,8 +979,10 @@ archive** under **Agent permissions for this project** in Project settings.
972
979
  The project setting applies to existing and future devboxes without an
973
980
  individual override. After a `destruction_disabled` error, request
974
981
  `destroy-devbox`; the owner can choose **Allow** or **Always allow for project**.
975
- Either way, agents can destroy only their own ordinary devbox. Template boxes
976
- and other devboxes cannot be targeted.
982
+ Either way, this permission lets agents destroy only their own ordinary devbox.
983
+ Template boxes and other devboxes cannot be targeted. To destroy devboxes that
984
+ agents on this box created, see
985
+ [Destroy And Archive Created Devboxes](#destroy-and-archive-created-devboxes).
977
986
 
978
987
  Destruction permanently deletes the devbox's files and retains its thread
979
988
  history. Run this only when the user's task calls for destroying the devbox,
@@ -996,10 +1005,66 @@ dvb-onbox box cancel-destroy --json
996
1005
  ```
997
1006
 
998
1007
  Any managed agent on the same devbox can cancel its pending request without
999
- the destruction permission. The command returns `cancelled`, or `not_pending`
1008
+ the destruction permission, including a request made by the box that created
1009
+ the devbox. The command returns `cancelled`, or `not_pending`
1000
1010
  with a null `requestId` if there is nothing to cancel. Once archival has
1001
1011
  started, it returns `destruction_started`; it cannot undo that handoff.
1002
1012
 
1013
+ ## Destroy And Archive Created Devboxes
1014
+
1015
+ An agent on a Template box or devbox can request destruction of an ordinary
1016
+ devbox that an agent on the same box created with
1017
+ `dvb-onbox threads start --target new-devbox`:
1018
+
1019
+ ```bash
1020
+ dvb-onbox box destroy --devbox <devbox-id> --json
1021
+ ```
1022
+
1023
+ Use the `devboxId` returned by `threads start`. The separate **Destroy and
1024
+ archive created devboxes** permission on the requesting box is off by default.
1025
+ Enable it in the thread header's **Agent permissions**, or under **Agent
1026
+ permissions for this project** in Project settings. After a
1027
+ `destruction_disabled` error, request `destroy-created-devboxes`; the owner can
1028
+ choose **Allow** or **Always allow for project**. This permission is
1029
+ independent of **Create devboxes and threads** and of the created devbox's own
1030
+ **Destroy and archive this devbox** permission, and any agent on the
1031
+ requesting box can use it. Devboxes created by another box, devboxes where this
1032
+ box only started a thread, devboxes created by a created devbox, devboxes
1033
+ created by restoring an archived thread, and Template boxes return
1034
+ `devbox_not_found`.
1035
+
1036
+ Run this only when the user's task calls for it, such as after the devbox's
1037
+ work has merged or has otherwise been preserved outside the machine.
1038
+ Destruction permanently deletes the devbox's files and retains its thread
1039
+ history.
1040
+
1041
+ The request waits for every agent and queued message on that devbox to finish,
1042
+ and boxes.dev wakes a sleeping devbox to archive it. New work submitted to the
1043
+ devbox before destruction starts cancels the request, as does turning off the
1044
+ permission on the requesting box. A request that stays pending for 30 minutes
1045
+ expires. If the devbox already has a pending request, including one it made for
1046
+ itself, the command returns `already_requested` with that request's ID. Pending
1047
+ requests are also cancelled if the requesting box is destroyed first, so a box
1048
+ that will destroy itself should first wait until its created devboxes are
1049
+ archived.
1050
+
1051
+ `accepted` means only that the request was saved. `threads list
1052
+ --include-archived` shows the devbox's thread as archived once its history is
1053
+ saved and deletion of the machine has started; that does not prove the machine
1054
+ is gone. Listing delegated threads still requires **Create devboxes and
1055
+ threads**.
1056
+
1057
+ To withdraw a pending request, run:
1058
+
1059
+ ```bash
1060
+ dvb-onbox box cancel-destroy --devbox <devbox-id> --json
1061
+ ```
1062
+
1063
+ Cancellation does not require a destroy permission and also withdraws a
1064
+ request the devbox made for itself. It returns `cancelled`, or `not_pending`
1065
+ with a null `requestId` if there is nothing to cancel. Once archival has
1066
+ started, it returns `destruction_started`.
1067
+
1003
1068
  ## Devbox Folders
1004
1069
 
1005
1070
  Project folders group whole ordinary devboxes in the desktop thread list. They
@@ -42,8 +42,9 @@ which has three steps:
42
42
  paste into Codex or Claude Code in the project folder, which has the agent
43
43
  run the agent-driven terminal setup. The prompt includes a login code that
44
44
  signs the agent's CLI in to the same boxes.dev account. Each code works
45
- once and expires within 30 minutes, and the page always shows a current
46
- one.
45
+ once and expires within 30 minutes. The textbox automatically regenerates
46
+ the code after use and before it expires, so the user can copy a fresh
47
+ prompt if an earlier attempt fails.
47
48
  3. **Get the desktop app**: the agent gives the user the Mac app link once
48
49
  setup starts, and **Download for Mac now** is available right away. On
49
50
  Windows and Linux browsers that boxes.dev can confidently identify, this
@@ -174,6 +175,15 @@ untracked files, Git access, agent config, and so on) — and reviews it with
174
175
  the user. The manifest lives outside the repo, so setup leaves no changes in
175
176
  the project folder, and the user can read or edit it directly at any time.
176
177
 
178
+ The local agent can record its verified current agent and model in optional
179
+ `agents.setup: { backend: codex, model: gpt-6.1-sol }` (use `claude` for Claude
180
+ Code). Remote setup prefers that agent when selected and connected, and that
181
+ model when its runtime advertises it. If that model is unavailable, setup uses
182
+ the chosen agent's account default. Without a selected connected agent
183
+ preference, setup prefers Codex when both agents are available. It requests
184
+ high reasoning where supported, otherwise the model's advertised reasoning
185
+ default.
186
+
177
187
  The manifest can explicitly select environment files outside the project.
178
188
  Environment, secret, configuration, and extra file entries can also name an
179
189
  edited copy to upload while leaving the laptop original untouched. Bash and
@@ -355,6 +365,23 @@ key, re-auth, remove a saved credential, or disconnect an agent. The active
355
365
  Codex and Claude choices are independent and apply globally across the user's
356
366
  devboxes. On macOS, Configure agents is in the boxes.dev app menu.
357
367
 
368
+ With multiple subscriptions saved for an agent, desktop Configure agents offers
369
+ **Automatically rotate subscriptions when usage depleted**. Selecting a
370
+ subscription radio chooses the **Default** account while automatic selection
371
+ is enabled; **Active** marks the account currently in use. boxes.dev prefers
372
+ the default whenever its usage is available, switches to another subscription
373
+ when it is exhausted, and returns after quota resets. A saved API key also
374
+ exposes **Automatically switch to API when all subscriptions are exhausted**,
375
+ which requires a separate opt-in and incurs the API provider's charges. Unknown
376
+ quota and authentication failures alone do not authorize API switching.
377
+ Choosing an API row directly returns that agent to manual selection. Codex and
378
+ Claude settings are independent, global,
379
+ and affect conversations started from either desktop or mobile. Mobile can
380
+ still select accounts manually; these automatic controls are configured on
381
+ desktop. Account changes retain conversation history; an agent already working
382
+ may finish its current turn first. They do not automatically replay a turn that
383
+ stopped at a usage limit; the user can continue that conversation after switching.
384
+
358
385
  Configure agents manages the Codex and Claude accounts that run coding-agent
359
386
  threads. Remote MCP connections are managed separately from **Integrations →
360
387
  MCPs** in the main desktop window. Paste an MCP URL or a Codex or Claude setup
@@ -815,12 +842,22 @@ project-code problem, it records the failure for follow-up instead of rewriting
815
842
  the project merely to make a check pass. The approved setup note can authorize
816
843
  specific tracked edits when the user intentionally wants them as part of setup.
817
844
 
818
- While remote setup is actively working, boxes.dev keeps the Template box awake
819
- even if the setup thread is quiet for a while. If the user presses Stop during
820
- remote setup, setup pauses instead of automatically sending another setup
821
- message. The workbench shows **Setup paused**, preserves the reason, and
822
- offers **Open setup thread** so the user can continue the same conversation
823
- without creating another setup turn automatically.
845
+ New remote setups use the user's connected Codex or Claude Code account and
846
+ consume that account's usage allowance or API credits. Desktop guided setup
847
+ uses Codex when both agents are selected and connected, otherwise the selected
848
+ connected agent. It uses that account's default model with high reasoning
849
+ where supported. Agent-driven setup can prefer the local agent and model
850
+ recorded in the manifest, as described above. The setup conversation is an
851
+ ordinary thread that the user can continue after setup. Reconnect that agent
852
+ if its auth needs attention; retrying setup keeps the same agent. Setups
853
+ already started with temporary
854
+ setup access will finish using their existing access.
855
+
856
+ Stop and continue new setup conversations with the normal thread controls.
857
+ boxes.dev will not send another setup message automatically. Once the work
858
+ is ready, the agent will request validation and the final snapshot with its
859
+ setup completion command. Older setup conversations may show **Setup paused**;
860
+ choose **Open setup thread** to continue them.
824
861
 
825
862
  Setup may show a mobile-app prompt while remote setup is running. The prompt can
826
863
  email the user a mobile app link, and the mobile app can follow the same
@@ -845,6 +882,15 @@ The agent can then send its final response while the workbench shows
845
882
  **Finishing setup**. The setup banner disappears only after finalization
846
883
  actually completes.
847
884
 
885
+ If the setup agent has replied or was interrupted without requesting completion,
886
+ the desktop app will offer **Mark setup completed** in the selected setup thread's
887
+ banner while the agent is idle, alongside **Open setup thread**. Choose the
888
+ completion action when the environment is ready; it will
889
+ run the same validation, snapshot, and cleanup before marking setup complete,
890
+ even if the agent has not written its summary. Continue the ordinary thread
891
+ instead if more work is needed. The action is hidden during active work and
892
+ finalization; if finalization fails, it can retry that step.
893
+
848
894
  If the project still does not run, ask the setup thread to continue from its
849
895
  summary before it requests completion.
850
896
 
@@ -881,9 +927,10 @@ Common recovery paths:
881
927
  automatically continue after Stop. When the user and agent agree the setup
882
928
  work is ready, the agent's normal completion command starts finalization
883
929
  without a separate retry prompt.
884
- - Returning to a setup thread later can refresh its temporary setup access
885
- quietly. If boxes.dev cannot verify that access for the same project and
886
- Template box, use the shown action to start a new thread or restart setup.
930
+ - Agent-auth failure: reconnect the setup thread's agent in Configure agents
931
+ or **Settings → Agent accounts**, then continue the thread or retry setup.
932
+ Older setups using temporary setup access may refresh that access quietly;
933
+ follow the displayed recovery action if the refresh fails.
887
934
  - Remote provisioning pause: use the shown action, such as retry setup, rebuild
888
935
  the bundle, or manage billing.
889
936
  - Alias conflict: choose a different project name or delete the conflicting
@@ -942,13 +942,16 @@ history, and the CLI, but does not grant access or save the thread by itself.
942
942
  It always applies the current team policy, privacy setting, and share access.
943
943
  On a shared-thread browser page, choose **Open in app** to open the same
944
944
  read-only thread in the desktop app, or in the mobile app when viewed on a
945
- phone or tablet.
946
-
947
- To save an ordinary Team work thread, choose **Pin to my workbench**. A viewer
948
- can later choose **Remove from Shared with me** without revoking access.
949
- Opening the same active share link or pinning the thread again restores the
950
- row. Read and unread state is personal to each viewer and does not change the
951
- owner's state.
945
+ phone or tablet. If the viewer has never signed in to that app, the button
946
+ opens a page with a download option instead.
947
+
948
+ To save an ordinary Team work thread, choose **Pin to my workbench**. A
949
+ teammate's thread has a `…` menu in its header and on its **Shared with me**
950
+ row. Choose **Remove from Shared with me** there to remove the row without
951
+ revoking access; opening the same active share link or pinning the thread
952
+ again restores it. Choose **Copy thread ID** to give the thread to an agent
953
+ that has permission to read other threads. Read and unread state is personal
954
+ to each viewer and does not change the owner's state.
952
955
 
953
956
  Under **Thread titles**, a teammate can choose **Request access**. On desktop,
954
957
  the project sidebar's **Shared by me** section appears whenever the selected
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@boxes-dev/dvb-runtime",
3
- "version": "1.0.1056",
3
+ "version": "1.0.1058",
4
4
  "description": "Runtime for the boxes.dev CLI. Install @boxes-dev/dvb to use the CLI.",
5
5
  "homepage": "https://boxes.dev",
6
6
  "type": "module",
@@ -77,5 +77,5 @@
77
77
  "e2b": "^2.18.0",
78
78
  "ink-testing-library": "^4.0.0"
79
79
  },
80
- "devboxReleasedAt": "2026-10-05T22:36:40Z"
80
+ "devboxReleasedAt": "2026-10-07T21:45:14Z"
81
81
  }