@boxes-dev/dvb-runtime 1.0.1047 → 1.0.1050

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.
@@ -51,6 +51,11 @@ boxes.dev does not guess either value. That choice becomes the default `boxes-de
51
51
  current project. Another project can reuse the same central sign-in and choose
52
52
  different assigned access without another browser sign-in.
53
53
 
54
+ If the account or permission-set list is empty or is missing expected access,
55
+ the company's AWS administrator needs to assign that access to the user's
56
+ identity. After that, choose **Refresh** in the picker to load the new
57
+ assignment with the existing sign-in; reconnecting is not required.
58
+
54
59
  AWS setup does not change the repository and does not require a Template box
55
60
  snapshot. New terminals start with `AWS_PROFILE=boxes-dev`. Existing Codex and
56
61
  Claude sessions keep current work running, then pick up AWS before their next
@@ -357,10 +357,10 @@ message becomes searchable a few seconds after the agent's reply finishes,
357
357
  and the thread's earlier messages stay searchable while the agent is still
358
358
  working. A deleted thread leaves the results as soon as you delete it.
359
359
 
360
- Results show one row per thread for up to 30 of the best matches, with the
361
- most recently active thread first. Each row shows the thread title, how long
362
- ago the thread was last active, and a highlighted excerpt labeled with who
363
- wrote the matching message. Archived threads have an archive icon, and each
360
+ Results show one row per thread for up to 30 threads, ordered by how well
361
+ they match. Each row shows the thread title, how long ago the thread was last
362
+ active, and a highlighted excerpt labeled with who wrote the matching
363
+ message. Archived threads have an archive icon, and each
364
364
  row names its project when the results come from more than one project. Use
365
365
  the arrow keys and **Enter**, or click a row, to open that thread in its
366
366
  project.
@@ -416,9 +416,13 @@ Browser tabs, cookies, local storage, downloads, uploads, and other profile
416
416
  state live on that runtime, so the user and agents can share the same web
417
417
  session. The Browser pane supports ordinary page interaction, file chooser
418
418
  prompts, downloads into the runtime, permission prompts, browser dialogs, and
419
- profile reset. **Restart browser** reloads the Browser process while preserving
420
- that profile data and asks for confirmation first; profile reset is the
421
- separate destructive action. Browser can also pop out from the side pane into
419
+ profile reset. **Restart browser** asks for confirmation, then opens one blank
420
+ tab while preserving sign-ins and saved profile data. Check **Restore open
421
+ tabs** in that confirmation to reload the current tabs instead; the choice
422
+ starts unchecked each time. Machines awaiting the browser update retain the
423
+ older confirmation, which says open tabs will reload and has no restoration
424
+ choice. Profile reset is the separate destructive action.
425
+ Browser can also pop out from the side pane into
422
426
  a near-full-window overlay and dock back into the workbench.
423
427
 
424
428
  When a site opens a foreground page, Browser selects that page and scrolls its
@@ -44,7 +44,7 @@ The field saves shell commands directly as a project setting; boxes.dev does
44
44
  not create a script file for it. The startup timeout defaults to 60 seconds and
45
45
  can be set from 1 to 120 seconds.
46
46
 
47
- When an ordinary project has a devbox startup script, boxes.dev may reserve a
47
+ When a project has a devbox startup script, boxes.dev may reserve a
48
48
  disposable devbox and run that script after the user starts typing, before the
49
49
  first prompt is sent. For Codex and Claude Code, boxes.dev may also prepare the conversation
50
50
  on that devbox after the script finishes, so a matching Send can reuse both
@@ -56,10 +56,11 @@ applies the current settings to a different devbox. An abandoned draft's devbox
56
56
  expires, but external side effects from a script cannot be undone, so startup
57
57
  scripts should be safe to run speculatively.
58
58
 
59
- Team Template member projects may prepare warm machines in advance, but their
60
- startup scripts wait until Send claims a devbox for the member. After the
61
- member's files and credentials are ready, the team startup script runs before
62
- the member's startup script and the first agent turn. Both startup scripts run
59
+ In a Team Template member project, that preparation runs the team startup
60
+ script and then the member's startup script, after the member's credentials
61
+ and required member files and values are ready and before the first agent turn.
62
+ A missing required member file or value blocks startup until the member adds
63
+ it in Project settings. Both startup scripts run
63
64
  in the sole repository when the template tracks exactly one, or in the project
64
65
  root otherwise. Teardown still runs in the project root. Team startup failures
65
66
  show warnings and do not block the member script, agent turn, or other members.
@@ -90,6 +90,9 @@ Use this terminology consistently:
90
90
  mentions, follow-ups, final replies, attachment import basics, and limits.
91
91
  - `linear.md`: Linear Agent App install, identity linking, assignment-triggered
92
92
  automations, issue updates, follow-ups, stop, and work-product URLs.
93
+ - `remote-assistants.md`: connecting an outside assistant to selected projects,
94
+ finding and continuing threads, progress and events, cancellation boundaries,
95
+ and removing access.
93
96
  - `aws.md`: central AWS IAM Identity Center sign-in, per-project account and
94
97
  role selection, the managed `boxes-dev` profile, credential precedence,
95
98
  refresh behavior, removal, and container limits.
@@ -58,7 +58,7 @@ twice.
58
58
  Tap **Search messages in all threads** above the list on Home or in a project to
59
59
  search your messages and the final replies in your own Codex and Claude
60
60
  threads across all projects. Results include archived and cold-stored
61
- conversations, list the most recently active threads first, and show
61
+ conversations, list the closest matches first, and show
62
62
  highlighted excerpts. Tap a result to open the thread. Searching does not wake a machine.
63
63
  Team admins can also find matches from their Team Template editing threads;
64
64
  open those threads in the desktop app.
@@ -477,8 +477,8 @@ pause, activate, run, and delete the owner's automations in that project; see
477
477
  [Automations](#automations). It is kept apart from the grants above, so a
478
478
  thread can hold it together with one of them.
479
479
 
480
- For thread reads, agent messaging, folder access, thread titles, and creating
481
- devboxes and threads, the owner can choose **Always allow for project**
480
+ For thread reads, agent messaging, folder access, thread titles, destroying
481
+ devboxes, and creating devboxes and threads, the owner can choose **Always allow for project**
482
482
  directly.
483
483
  This will enable the project's shared permission and make the requesting box
484
484
  use it. All existing and future devboxes will follow that setting, except
@@ -689,9 +689,11 @@ The target devbox must belong to the current box's project. An instance ID from
689
689
  another project is rejected even when both projects belong to the same user.
690
690
 
691
691
  The Template box may be a source but is never a delegated thread target. All
692
- forms return the child thread and devbox IDs. Retry an uncertain result with the
693
- same idempotency key and identical arguments, including model and reasoning
694
- effort and any explicit speed; changed arguments under the same key fail.
692
+ forms return the child thread and devbox IDs. The child appears in the user's
693
+ thread list as a regular thread, and the user can read and reply to it there.
694
+ Retry an uncertain result with the same idempotency key and identical
695
+ arguments, including model and reasoning effort and any explicit speed;
696
+ changed arguments under the same key fail.
695
697
 
696
698
  The source box can continue and inspect only the delegated children it created
697
699
  through this command. It cannot target another same-project thread. The default
@@ -730,10 +732,9 @@ dvb-onbox threads send \
730
732
  `next` starts a turn when the child is idle and otherwise queues behind its
731
733
  active turn. `idle` is the strict idle-only form. `steer` is Codex-only and
732
734
  changes the exact active turn. `queue` is the strict active-only form and
733
- enters Codex's persistent FIFO or Claude's native next-message queue, including
734
- a delegated Claude first turn that is still running in its unattended native
735
- terminal. `idle`, `steer`, and `queue` do not adapt to another delivery mode. A
736
- native terminal actively controlled by a person stays out of bounds.
735
+ enters Codex's persistent FIFO or Claude's next-message queue. `idle`, `steer`,
736
+ and `queue` do not adapt to another delivery mode. A Claude terminal that a
737
+ person is actively using stays out of bounds.
737
738
 
738
739
  Interrupt only an exact active turn:
739
740
 
@@ -874,6 +875,31 @@ They may lag active work and shorten long messages. They do not wake boxes,
874
875
  mark threads read, claim links, or expose full tool logs. Without `--scope`,
875
876
  the existing `list` and `read` commands still select delegated children only.
876
877
 
878
+ To find your own threads by what was said in them, search instead of listing:
879
+
880
+ ```bash
881
+ dvb-onbox threads search --scope user --query "flaky deploy" --json
882
+ dvb-onbox threads search --scope project --query '"setup script" timeout' -n 5 --json
883
+ dvb-onbox threads read --scope user --thread <id> --cursor <readCursor> --turns 3 --json
884
+ ```
885
+
886
+ Search uses the same index as thread search in the desktop and mobile apps. It
887
+ covers your messages and the agents' final replies in your own Codex and
888
+ Claude threads, including archived ones. Commentary, tool activity,
889
+ attachments, and Team Template editing threads are not included. It accepts only the `project` and `user` scopes,
890
+ which need the same permission levels as listing them. Put a phrase in double
891
+ quotes to require those words together in that order.
892
+
893
+ Results list 10 threads by default, best match first; pass `-n` for 1 to 30.
894
+ Each result has the same thread fields as a listing and a `match` with the
895
+ role, message time, a highlighted `snippet`, and `readCursor`. To read the
896
+ conversation at the match, run `threads read` with the same scope, the
897
+ thread's `id`, and `readCursor` as `--cursor`: the page ends with the matching
898
+ turn, and its returned cursor continues to older messages. If the thread's history has been rebuilt since it was
899
+ indexed, the read reports `cursor_expired`; read it without a cursor instead.
900
+ A new message becomes searchable a few seconds after the agent's reply
901
+ finishes.
902
+
877
903
  If a needed scope reports `thread_read_access_disabled`, request the matching
878
904
  `read-project-threads`, `read-user-threads`, `read-shared-threads`, or
879
905
  `read-team-threads` permission. Team visibility limits require a team setting
@@ -931,10 +957,14 @@ An agent can request destruction of its own ordinary devbox with:
931
957
  dvb-onbox box destroy --json
932
958
  ```
933
959
 
934
- The separate **Destroy and archive this devbox** permission is off by default
935
- and applies only to that devbox. Enable it in the thread header's **Agent
936
- permissions**, or request `destroy-devbox` after a `destruction_disabled` error.
937
- Template boxes and other devboxes cannot be targeted.
960
+ The separate **Destroy and archive this devbox** permission is off by default.
961
+ Enable it in the thread header's **Agent permissions**, or set **Destroy and
962
+ archive** under **Agent permissions for this project** in Project settings.
963
+ The project setting applies to existing and future devboxes without an
964
+ individual override. After a `destruction_disabled` error, request
965
+ `destroy-devbox`; the owner can choose **Allow** or **Always allow for project**.
966
+ Either way, agents can destroy only their own ordinary devbox. Template boxes
967
+ and other devboxes cannot be targeted.
938
968
 
939
969
  Destruction permanently deletes the devbox's files and retains its thread
940
970
  history. Run this only when the user's task calls for destroying the devbox,
@@ -0,0 +1,92 @@
1
+ # Connect an outside assistant to boxes.dev
2
+
3
+ An assistant connected to boxes.dev through its remote MCP server can find,
4
+ read and control your Codex and Claude conversations in projects you select.
5
+ The connection belongs to your account. It does not grant access to a
6
+ teammate's shared threads or Team Template administration.
7
+
8
+ ## Connect and choose access
9
+
10
+ Add the boxes.dev plugin or remote MCP connection in your assistant, then
11
+ follow its authorization link. Sign in to boxes.dev and check the requesting
12
+ domain, return address, account and requested permissions. A client name marked unverified is
13
+ supplied by the client, not an endorsement from boxes.dev.
14
+
15
+ Select the projects the assistant may access, then choose **Allow access**.
16
+ Read permission includes prompts, replies and saved history. Task-control
17
+ permission will let the assistant start agents, send follow-ups and interrupt
18
+ work with the agents' configured permissions and normal usage. Event permission
19
+ will let it receive completion, failure and input-required notifications.
20
+
21
+ New projects are not automatically included. Reconnect to change the selected
22
+ projects or permissions. Refreshing an existing sign-in does not widen access.
23
+
24
+ ## Find and continue work
25
+
26
+ The assistant can list recent conversations or search indexed prompts and
27
+ final replies, including conversations started in the apps. Search can lag
28
+ recent messages and returns a bounded result set. Read the thread before
29
+ continuing it; discovery includes whether it can accept a follow-up now.
30
+
31
+ A new task starts Codex or Claude in a new devbox from the project's saved
32
+ environment. Finish project setup and save its environment before starting.
33
+ Continuing an existing thread preserves its context and can wake its sleeping
34
+ devbox. Archived conversations need to be unarchived in boxes.dev first;
35
+ conversations in storage need to be restored. A history-only conversation
36
+ cannot continue. These recovery actions are not performed automatically.
37
+
38
+ Follow-ups queue by default while an agent is working. Codex also supports
39
+ steering to redirect current work; Claude steering is unavailable through this
40
+ connection. Claude follow-ups go directly to its session and do not appear in
41
+ the app's pending-message list. A Claude receipt marked not delivered is final;
42
+ a new attempt needs a new request key. Repeating an identical start or send with its original
43
+ idempotency key will return the same receipt; use a new key for a different
44
+ request. An accepted or delivered receipt does not mean the agent has finished.
45
+
46
+ ## Read progress and respond to events
47
+
48
+ Thread IDs identify conversations; operation IDs identify delivery receipts for
49
+ start or send requests. Keep the thread link and receipt when moving between
50
+ assistant chats. Delivered means the prompt was handed off, not that it
51
+ executed or completed.
52
+
53
+ Read the conversation for current activity and saved messages. Refresh to see
54
+ recent content, or page backward for earlier context. History previews can
55
+ omit content and shorten messages; read listed messages in full when needed.
56
+ For very large messages omitted from the preview, share the thread link.
57
+ Revert or rewind can remove messages from current history.
58
+
59
+ There is no per-request result mapping. The latest reply or completion notice
60
+ may reflect another message, a human's work or a background continuation.
61
+ An idle thread does not establish that all queued messages ran.
62
+
63
+ Assistants that support events can subscribe before starting work, then read
64
+ the thread's current state. Notifications identify the conversation, and saved
65
+ messages can arrive after an event. Subscriptions need renewal within 24 hours
66
+ and do not replay old events. Poll current activity when notifications are
67
+ unavailable or missed; legacy-only sessions may require polling.
68
+
69
+ For native approvals or interactive questions, share the thread link so the
70
+ user can respond in boxes.dev. A question may not appear in saved history and
71
+ may reject remote interruption. Sending a queued prompt does not answer the
72
+ native dialog.
73
+
74
+ ## Stop work or remove access
75
+
76
+ Stopping a thread can cancel its pending startup or interrupt current work.
77
+ Retrying the same stop request will not select newer work; use a new request
78
+ for a later stop. Stopping preserves files and queued follow-ups, which may start
79
+ immediately afterward. It cannot withdraw a message already handed to an agent's
80
+ queue or stop every future turn. A Codex prompt interrupted before its echo may
81
+ be returned to the boxes.dev composer as unsent text.
82
+
83
+ On older devboxes, Codex's first response can appear idle while it is still
84
+ running until the devbox receives the startup fix. Claude can also reject a
85
+ stop before its first activity is visible. If the assistant cannot confirm a
86
+ stop, open the conversation to inspect its work; an idle status alone does
87
+ not confirm it finished or stopped.
88
+
89
+ To disconnect an assistant, open **Account → Assistant connections**, choose
90
+ **Remove access** for that connection, then confirm. This will stop new requests
91
+ and future event deliveries. Tasks already accepted will continue; interrupt
92
+ those tasks separately if you also want them to stop.
@@ -182,7 +182,10 @@ Teardown scripts continue to run in the project root.
182
182
  For a managed template the startup sequence is:
183
183
 
184
184
  1. Start from the saved template and prepare the member's durable environment.
185
- 2. The prepared devbox may wait until that member needs it.
185
+ 2. The prepared devbox may wait until that member starts typing a first prompt
186
+ for a new devbox. Steps 3 to 5 can then run before the member sends it.
187
+ A missing required member file or value blocks steps 4 and 5 until the
188
+ member adds it.
186
189
  3. boxes.dev checks the member's configured connections and files.
187
190
  4. **Team startup script** (optional, team-owned). It runs with the same member
188
191
  environment as the member startup script, immediately before it. Saving
@@ -233,8 +233,10 @@ name, the scope, and which agents to add the connection to. The URL, the
233
233
  authentication mode, and the name the agents use sit under **Advanced**, which
234
234
  opens on its own when a header or API key still has to be typed in. New
235
235
  connections default to **This project**; choose **All projects** only when the
236
- same server and account should be available everywhere. Choose the agents under
237
- **Add to**, then choose **Add MCP** to save and authorize the connection.
236
+ same server and account should be available everywhere. Codex and Claude both
237
+ start selected under **Add to**; a pasted Codex or Claude setup command selects
238
+ only its agent. Adjust the selection, then choose **Add MCP** to save and
239
+ authorize the connection.
238
240
 
239
241
  Codex and Claude are enabled independently from the same connection row. OAuth
240
242
  opens a local browser sign-in for the selected agent, so enabling both agents
@@ -628,8 +630,12 @@ source thread's files and working directory. New devbox snapshots the exact
628
630
  Template box or devbox that hosts the source, then creates an independent
629
631
  devbox with that filesystem state. This includes the current working tree when
630
632
  the source is already a devbox. The source remains unchanged, and the source
631
- and child can continue independently. On mobile, long-press a completed reply
632
- to choose **Continue in current box** or **Continue in new devbox**. Fork
633
+ and child can continue independently. On mobile, tap the vertical three-dot
634
+ button beside a completed reply's timestamp to choose **Fork in current box** or
635
+ **Fork into new devbox**. To copy your message or an agent's final response,
636
+ tap its copy button beside the timestamp. On Android, long-press text and
637
+ adjust the selection handles to copy part of any message, including intermediate
638
+ updates. Fork
633
639
  controls are unavailable while the source is working, but they don't wait for
634
640
  the app to connect to the source machine. When you choose a fork action,
635
641
  boxes.dev will connect to the source, waking it if needed, before creating the
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@boxes-dev/dvb-runtime",
3
- "version": "1.0.1047",
3
+ "version": "1.0.1050",
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",
@@ -79,5 +79,5 @@
79
79
  "e2b": "^2.18.0",
80
80
  "ink-testing-library": "^4.0.0"
81
81
  },
82
- "devboxReleasedAt": "2026-10-01T16:46:44Z"
82
+ "devboxReleasedAt": "2026-10-02T17:17:03Z"
83
83
  }