@boxes-dev/dvb-runtime 1.0.1110 → 1.0.1112
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/agent-init-guides/flow.md +16 -5
- package/dist/bin/dvb.mjs +1329 -697
- package/dist/bin/dvbd.mjs +4515 -608
- package/dist/managed-codex-install/package-lock.json +28 -28
- package/dist/managed-codex-install/package.json +1 -1
- package/dist/product-docs/references/agent-tools.md +18 -0
- package/dist/product-docs/references/automations.md +9 -0
- package/dist/product-docs/references/aws.md +21 -0
- package/dist/product-docs/references/desktop-workbench.md +17 -0
- package/dist/product-docs/references/google-cloud.md +8 -0
- package/dist/product-docs/references/mobile.md +14 -4
- package/dist/product-docs/references/onbox-agent-tools.md +140 -8
- package/dist/product-docs/references/ports-terminal-and-runtime.md +16 -4
- package/dist/product-docs/references/project-setup.md +24 -10
- package/dist/product-docs/references/tailscale.md +14 -0
- package/dist/product-docs/references/team-template.md +27 -9
- package/dist/product-docs/references/template-box-environment.md +7 -0
- package/dist/product-docs/references/threads-and-agents.md +93 -18
- package/dist/product-docs/references/troubleshooting.md +27 -0
- package/dist/product-docs/references/unattended-work.md +10 -3
- package/package.json +2 -2
|
@@ -53,20 +53,31 @@ a saved version or a project created from it.
|
|
|
53
53
|
|
|
54
54
|
An admin can remove another member from **Team settings → Members** using the
|
|
55
55
|
member's menu. Select a remaining member as the work recipient, then choose
|
|
56
|
-
|
|
57
|
-
project
|
|
58
|
-
|
|
56
|
+
an action for every project. **Transfer threads** is the default: choose an
|
|
57
|
+
existing recipient-owned project for the conversations and attachments. Saved
|
|
58
|
+
conversations arrive under **Archived** and restore on the recipient's devboxes
|
|
59
|
+
using their credentials. The original project and machines follow Keep below.
|
|
60
|
+
**Transfer full project** moves the original machines as well. It is dangerous
|
|
61
|
+
when the former owner is untrusted: software they left behind may read future
|
|
62
|
+
code or credentials, even after access keys rotate. Each full project transfer
|
|
63
|
+
requires acknowledgement of this risk. Transferred work records its original
|
|
64
|
+
account. **Delete** uses permanent project deletion and requires confirmation
|
|
65
|
+
for each project.
|
|
59
66
|
Keep moves the project to the departing account's fresh personal team and
|
|
60
67
|
removes managed files, managed secrets, team access, and existing thread
|
|
61
68
|
sharing. Ordinary files and unmanaged environment-file content remain.
|
|
62
69
|
A kept managed project receives an independent Template box.
|
|
63
70
|
|
|
64
|
-
Sleeping boxes remain asleep during Transfer and Keep. Ownership
|
|
65
|
-
access change during removal; managed files and credentials are cleaned
|
|
66
|
-
the next wake, before the box is available. The first wake restarts the box
|
|
71
|
+
Sleeping boxes remain asleep during Transfer full project and Keep. Ownership
|
|
72
|
+
and team access change during removal; managed files and credentials are cleaned
|
|
73
|
+
up on the next wake, before the box is available. The first wake restarts the box
|
|
67
74
|
from its saved disk, preserving ordinary files and stopping old processes.
|
|
75
|
+
Thread transfer may wake a source box to archive native history; an initially
|
|
76
|
+
sleeping box returns to sleep after cleanup.
|
|
68
77
|
|
|
69
78
|
Running work stops during handoff, and automations pause for connection review.
|
|
79
|
+
Pending messages in reassigned threads require review before sending. Messages
|
|
80
|
+
with uncertain delivery retain their warning and do not replay automatically.
|
|
70
81
|
Account-specific connections require the new owner's authorization. The removed
|
|
71
82
|
account can continue using its personal team and will not automatically rejoin
|
|
72
83
|
the former team through its email domain. Remove its paid seat in Billing and
|
|
@@ -81,6 +92,8 @@ account; box preparation and the final handoff have separate progress updates.
|
|
|
81
92
|
The recipient can keep creating projects and devboxes while removal runs or
|
|
82
93
|
awaits retry. Names reserved for incoming work remain unavailable for new
|
|
83
94
|
projects and devboxes.
|
|
95
|
+
An existing project receiving threads cannot be deleted until transfer finishes;
|
|
96
|
+
other work in it can continue.
|
|
84
97
|
Team Template conversations transfer to the selected recipient, who must be
|
|
85
98
|
an admin when these conversations exist. Shared saved environments remain with
|
|
86
99
|
the team. The personal team needs its own billing setup before starting
|
|
@@ -529,7 +542,11 @@ boxes.dev GitHub connection and pull/push access. Any GitHub maintenance watch,
|
|
|
529
542
|
including a disabled watch, also requires access to the watched repository.
|
|
530
543
|
The flow presents
|
|
531
544
|
the existing connect, update-authorization, install, or grant-access action and
|
|
532
|
-
does not allocate the Template box until access is satisfied.
|
|
545
|
+
does not allocate the Template box until access is satisfied. If the member's
|
|
546
|
+
GitHub account can only read a repository, or can't reach one that boxes.dev
|
|
547
|
+
already has access to, the flow asks the member to get write access from an
|
|
548
|
+
owner of the repository's GitHub organization or account and offers a request
|
|
549
|
+
message to copy.
|
|
533
550
|
|
|
534
551
|
When creation starts, boxes.dev pins the selected filesystem version and the
|
|
535
552
|
current saved Project defaults as separate inputs. Later Team Template edits do
|
|
@@ -572,8 +589,9 @@ change. If waiting for preparation times out, the notice will say that completio
|
|
|
572
589
|
could not be confirmed and your message was not sent; it will retain your draft.
|
|
573
590
|
|
|
574
591
|
The new project is independent of later Team Template versions and save cleanup.
|
|
575
|
-
When removing a member, an admin chooses whether to transfer
|
|
576
|
-
that member keep
|
|
592
|
+
When removing a member, an admin chooses whether to transfer its threads,
|
|
593
|
+
transfer the full project, delete it, or let that member keep it under the
|
|
594
|
+
removal rules above.
|
|
577
595
|
Creating it uses a normal project slot and its
|
|
578
596
|
box uses the member's normal billing entitlement.
|
|
579
597
|
|
|
@@ -191,6 +191,13 @@ has actually stopped. A canceled run does not snapshot, and changes it made
|
|
|
191
191
|
before cancellation remain on the live Template box. Snapshot creation cannot
|
|
192
192
|
be canceled after a script has completed successfully.
|
|
193
193
|
|
|
194
|
+
boxes.dev keeps the Template box awake for the whole run, through the
|
|
195
|
+
snapshot, even when nobody is connected, so a script can use its full timeout.
|
|
196
|
+
If a run stops before the script reports a result, for example because someone
|
|
197
|
+
put the Template box to sleep, it takes no snapshot, records the reason, and
|
|
198
|
+
keeps the output captured so far. Changes the script made may remain on the
|
|
199
|
+
Template box, so review them before running the script again.
|
|
200
|
+
|
|
194
201
|
The Template page retains bounded diagnostics and recent run history, including
|
|
195
202
|
the final output of a canceled run behind a collapsed **Show output** control.
|
|
196
203
|
It offers the appropriate script or snapshot retry and lets the user dismiss a
|
|
@@ -111,10 +111,12 @@ ring. JSON thread status distinguishes an unsubmitted `draft`, an in-progress
|
|
|
111
111
|
|
|
112
112
|
In projects that track two or more repos, a new thread draft can choose its
|
|
113
113
|
starting working directory before the first prompt is sent. The options are the
|
|
114
|
-
project directory and the tracked repo directories in that project. When a
|
|
115
|
-
|
|
116
|
-
in that repo, whether they run on a new or an existing devbox.
|
|
117
|
-
|
|
114
|
+
project directory and the tracked repo directories in that project. When a
|
|
115
|
+
project tracks exactly one repo below the project directory, new threads start
|
|
116
|
+
in that repo, whether they run on a new or an existing devbox. In a project that
|
|
117
|
+
isn't managed by a Team Template, a thread started with `dvb threads start`
|
|
118
|
+
still starts in the project directory. Existing threads continue in the working
|
|
119
|
+
directory they were originally started with.
|
|
118
120
|
|
|
119
121
|
## Codex model providers
|
|
120
122
|
|
|
@@ -307,6 +309,9 @@ start selected under **Add to**; a pasted Codex or Claude setup command selects
|
|
|
307
309
|
only its agent. Adjust the selection, then choose **Add MCP** to save and
|
|
308
310
|
authorize the connection.
|
|
309
311
|
|
|
312
|
+
Large MCP results in Codex may appear as shortened raw data when you reopen a
|
|
313
|
+
thread. Keep a separate copy of any result you need in full.
|
|
314
|
+
|
|
310
315
|
Slack's official MCP server, `https://mcp.slack.com/mcp`, accepts OAuth sign-in
|
|
311
316
|
only from apps registered with Slack, so boxes.dev can't sign in to it. Pasting
|
|
312
317
|
that exact URL in **Add MCP** skips detection, opens **Advanced** with an
|
|
@@ -443,6 +448,15 @@ to answer, or stop the turn. Automated turns can wait for an answer too;
|
|
|
443
448
|
don't rely on an unanswered request timing out. If an older app cannot show
|
|
444
449
|
the request, update boxes.dev and reopen the thread.
|
|
445
450
|
|
|
451
|
+
Pending Codex questions and forms can appear while the app is still connecting
|
|
452
|
+
to the agent. Read the request while you wait; answering, approving, or opening
|
|
453
|
+
a service's browser flow requires the connection. The initial preview omits
|
|
454
|
+
prefilled form values and browser destinations. A long request may show a
|
|
455
|
+
shortened preview first. Once connected, the app shows only requests the agent
|
|
456
|
+
still has pending, so a question answered elsewhere disappears.
|
|
457
|
+
Read-only thread viewers can see the pending request, but only the owner can
|
|
458
|
+
answer it.
|
|
459
|
+
|
|
446
460
|
## Plugins
|
|
447
461
|
|
|
448
462
|
Open **Integrations → Codex/Claude Plugins** in the desktop app. The page talks
|
|
@@ -715,6 +729,17 @@ prepares. Free space is checked again before the files are copied onto the
|
|
|
715
729
|
box. If the files will not fit, free up space or choose fewer files and retry;
|
|
716
730
|
the warning keeps the existing draft intact.
|
|
717
731
|
|
|
732
|
+
When a Codex or Claude response finishes on desktop, the empty composer may show
|
|
733
|
+
a suggested next message in gray. Tab or Right Arrow moves it into the composer
|
|
734
|
+
for editing, Escape dismisses it, and typing replaces it. Enter does not send
|
|
735
|
+
it. Suggestions do not appear on mobile, and not every response gets one: some
|
|
736
|
+
Codex models and custom model providers do not support them, and Claude can skip
|
|
737
|
+
any response, including every response while the plan is close to a usage limit.
|
|
738
|
+
Suggestions use the person's agent plan or API credits. **Suggest
|
|
739
|
+
next messages** in **Settings → Agents → Agent replies** on desktop turns them
|
|
740
|
+
off. They disappear right away, though active Claude threads may keep generating
|
|
741
|
+
them.
|
|
742
|
+
|
|
718
743
|
When the agent is working, the composer may stay available for follow-ups. Some
|
|
719
744
|
follow-ups are queued and delivered after the current turn. They stay in the
|
|
720
745
|
same user-bubble queue used during startup and reconnect. Queued follow-ups can
|
|
@@ -722,8 +747,12 @@ be edited, deleted, or restored. During an active Codex turn, `Steer now`
|
|
|
722
747
|
interrupts the current turn and starts the oldest queued follow-up. Remaining
|
|
723
748
|
messages stay queued in order.
|
|
724
749
|
|
|
750
|
+
A **Steer** message joins Codex's current response and may discard text it was
|
|
751
|
+
still writing. Completed messages will stay in the conversation, and running
|
|
752
|
+
commands may continue while Codex changes direction.
|
|
753
|
+
|
|
725
754
|
Choose the default for both Codex and Claude in **Account → Agent replies** on
|
|
726
|
-
desktop or **Settings → Coding agents →
|
|
755
|
+
desktop or **Settings → Coding agents → Follow-up messages** on mobile.
|
|
727
756
|
**Queue** or **Steer** applies the same default across both apps. **App
|
|
728
757
|
defaults** preserves each app's existing preference. Desktop Enter and the
|
|
729
758
|
send button use that default; Cmd+Enter (Ctrl+Enter on Windows and Linux) uses
|
|
@@ -736,11 +765,13 @@ steer at its next available opportunity; a message sent during a final response
|
|
|
736
765
|
may get a separate response afterward. Both actions support Claude's existing
|
|
737
766
|
attachments.
|
|
738
767
|
|
|
739
|
-
With **App defaults**,
|
|
740
|
-
|
|
741
|
-
|
|
742
|
-
|
|
743
|
-
|
|
768
|
+
With **App defaults**, Claude uses Steer on desktop and mobile, unless the
|
|
769
|
+
user chose **Queue** with the mobile composer control on that phone. On
|
|
770
|
+
desktop, Enter and the send button steer, and Cmd+Enter (Ctrl+Enter on Windows
|
|
771
|
+
and Linux) queues. The send button's tooltip shows both shortcuts. Slash
|
|
772
|
+
commands always wait for the current response. An idle thread starts normally
|
|
773
|
+
either way. Once Claude accepts a steer, it cannot be edited or deleted as a
|
|
774
|
+
waiting Queue message. If a thread
|
|
744
775
|
can't accept a steer, such as while Claude waits for an answer to its question,
|
|
745
776
|
the message will show **Message send failed** instead of being queued.
|
|
746
777
|
**Edit message** will return it to the composer and show the reason; then queue
|
|
@@ -850,8 +881,9 @@ model-specific quotas with countdowns to their resets. Limits for the selected
|
|
|
850
881
|
model use warning colors; quotas for other models remain visible in muted
|
|
851
882
|
colors. When the connected ChatGPT account has credits, the indicator also
|
|
852
883
|
shows the credit balance. Codex keeps working on credits after the ordinary
|
|
853
|
-
session or weekly limit runs out
|
|
854
|
-
|
|
884
|
+
session or weekly limit runs out. That limit shows red at 0% and the balance is
|
|
885
|
+
marked In use, while the indicator icon stays amber instead of showing the red
|
|
886
|
+
alert. When the account has banked
|
|
855
887
|
usage limit resets, the same indicator shows how many are available and when
|
|
856
888
|
the next three expire; that row is omitted when reset inventory is unavailable.
|
|
857
889
|
The indicator's details name the account the limits belong to. When Codex is
|
|
@@ -939,7 +971,8 @@ supports slash commands when the thread surface has command lookup
|
|
|
939
971
|
enabled. Type `/` in a Claude reply box on desktop or mobile to list Claude's
|
|
940
972
|
commands and skills; choosing one adds it to the message. Skill rows show
|
|
941
973
|
Project, Personal, Plugin, or Account (skills synced from the claude.ai
|
|
942
|
-
account).
|
|
974
|
+
account). When Claude runs in the project directory, the list also includes the
|
|
975
|
+
project skills and commands of each tracked repo below it. Before the box's live list is ready, including in a new thread, the composer
|
|
943
976
|
uses the project's most recently opened Claude thread for project and personal
|
|
944
977
|
skills, and the selected Claude account's last list for its synced skills and
|
|
945
978
|
Claude's built-in commands, which depend on the account's plan. On mobile, the
|
|
@@ -1097,7 +1130,26 @@ question also includes **Type something else...** for a custom answer and
|
|
|
1097
1130
|
the current partial selections or custom text back as context so Claude can
|
|
1098
1131
|
reformulate the question; it does not record a completed answer. Some
|
|
1099
1132
|
single-choice answers submit immediately, while multi-select and custom
|
|
1100
|
-
answers use a Submit action.
|
|
1133
|
+
answers use a Submit action. Answering a question on a sleeping box wakes the
|
|
1134
|
+
box and sends the answer once the app reconnects.
|
|
1135
|
+
|
|
1136
|
+
To let Claude continue without an answer, choose **Question auto-continue
|
|
1137
|
+
timeout** under **Settings → Agents → Agent replies** on desktop or
|
|
1138
|
+
**Settings → Coding agents** on mobile. The account-wide choices are **Never**
|
|
1139
|
+
(the default), **60s**, **5m**, and **10m**. After the selected interval, Claude
|
|
1140
|
+
will receive a message explaining that you have not responded and asking it
|
|
1141
|
+
to proceed using its best judgment. This applies to Claude question cards,
|
|
1142
|
+
not permission requests or plan approvals.
|
|
1143
|
+
|
|
1144
|
+
The timer starts when each question appears and will restart when you interact
|
|
1145
|
+
with its card. When time runs out, Claude will receive any partial selections
|
|
1146
|
+
or custom text that reached the box. It will keep running with the app closed
|
|
1147
|
+
while the box is awake. Changing the setting will affect subsequent
|
|
1148
|
+
questions. A sleeping box must wake before Claude can continue. A box running
|
|
1149
|
+
an older version of boxes.dev will keep waiting until its software updates.
|
|
1150
|
+
Older apps cannot report card interaction or partial answers; update the app
|
|
1151
|
+
to use those behaviors. Claude's own terminal setting applies separately in
|
|
1152
|
+
the CLI view.
|
|
1101
1153
|
|
|
1102
1154
|
Claude Code turns can usually be stopped while Claude Code is working or
|
|
1103
1155
|
streaming. The composer and transcript show queued prompts that Claude Code
|
|
@@ -1108,9 +1160,12 @@ session and weekly quota with reset times. That quota is shared across
|
|
|
1108
1160
|
Template boxes and devboxes using the same Anthropic organization and account.
|
|
1109
1161
|
If a thread is still connected with credentials from before a re-authentication,
|
|
1110
1162
|
it continues to show the quota for the account scope that thread is actually
|
|
1111
|
-
using. The quota details name that account.
|
|
1112
|
-
|
|
1113
|
-
|
|
1163
|
+
using. The quota details name that account. If the account has extra usage
|
|
1164
|
+
turned on, Claude Code keeps working after a session or weekly limit runs out,
|
|
1165
|
+
and Anthropic bills that work as extra usage. The limit still shows red at 0%,
|
|
1166
|
+
and the quota details add **Using extra usage** in amber. When Claude Code is
|
|
1167
|
+
using an API key, the composer shows a key icon instead, with today's token
|
|
1168
|
+
usage for that key when available.
|
|
1114
1169
|
|
|
1115
1170
|
On desktop, boxes.dev folds intermediate activity for an older Claude Code turn
|
|
1116
1171
|
after the user prompt and final agent reply are both available. The current
|
|
@@ -1160,6 +1215,15 @@ editing. Desktop and mobile drop the rewound turns; file changes those turns
|
|
|
1160
1215
|
made stay on the machine. Codex refuses the rewind while a turn is running, so
|
|
1161
1216
|
stop the turn first.
|
|
1162
1217
|
|
|
1218
|
+
In Codex's managed terminal, the default `/plugins` list includes local
|
|
1219
|
+
marketplaces and plugins already installed for the signed-in ChatGPT account.
|
|
1220
|
+
Installed plugins remain available to mention in prompts when enabled and
|
|
1221
|
+
allowed by the account's admin. The default list omits uninstalled global
|
|
1222
|
+
ChatGPT catalog entries and their featured
|
|
1223
|
+
recommendations. Other plugin discovery and installation options are described
|
|
1224
|
+
under **Plugins** above. This applies to both the desktop CLI view and the
|
|
1225
|
+
boxes.dev CLI on the user's computer.
|
|
1226
|
+
|
|
1163
1227
|
A managed Claude Code CLI stays bound to the boxes.dev thread and working
|
|
1164
1228
|
directory it opened. Claude's Agent View and Remote Control are unavailable in
|
|
1165
1229
|
that CLI. Commands that would replace or move its session—`/clear`, `/new`,
|
|
@@ -1211,7 +1275,8 @@ cancellation, before an active response exists, still cancels the pending start.
|
|
|
1211
1275
|
Claude steers already accepted by Claude are different: Stop may leave them
|
|
1212
1276
|
waiting for Claude's next response, and they cannot be taken back through the
|
|
1213
1277
|
Queue controls. A steer that Claude already read remains in the thread even
|
|
1214
|
-
if its response is stopped.
|
|
1278
|
+
if its response is stopped. If Claude doesn't respond to Stop, any steer it
|
|
1279
|
+
hasn't read yet returns to the user's reply box unsent.
|
|
1215
1280
|
|
|
1216
1281
|
Interrupt availability depends on the agent, current turn state, and runtime
|
|
1217
1282
|
state. If the UI says interrupt is unavailable, wait for the current operation
|
|
@@ -1285,6 +1350,16 @@ without the row.
|
|
|
1285
1350
|
Devboxes nest under the devbox that started them at every level, and in the
|
|
1286
1351
|
main list a group moves up with its newest thread.
|
|
1287
1352
|
|
|
1353
|
+
On desktop, an open group lists its first 5 devboxes, and **Load more
|
|
1354
|
+
devboxes** adds 15 at a time. A devbox folds into an **N muted devboxes** row
|
|
1355
|
+
at the end of its group when all of its threads are muted, none is unread or
|
|
1356
|
+
waiting for input, and it hasn't started devboxes of its own. The row appears
|
|
1357
|
+
only when at least two devboxes fold and at least one stays listed. It shows
|
|
1358
|
+
how many muted devboxes are working, starts closed, remembers whether it was
|
|
1359
|
+
left open, and lists 15 muted devboxes at a time. While the row is closed, the
|
|
1360
|
+
devbox with the open thread stays listed. On a phone, groups don't page and
|
|
1361
|
+
don't fold muted devboxes.
|
|
1362
|
+
|
|
1288
1363
|
A pinned devbox stays under **Pinned**, and a devbox in a different folder from
|
|
1289
1364
|
its parent stays in its folder. A devbox in the same folder as its parent nests
|
|
1290
1365
|
under it there. Threads an agent starts on an existing devbox stay on that
|
|
@@ -70,6 +70,33 @@ runaway processes. boxes.dev reserves some resources for control, so this works
|
|
|
70
70
|
even when agent or user processes are stuck. If it still does not recover, use
|
|
71
71
|
**Machine > Reset**, then **Machine > Reboot** only if Reset fails.
|
|
72
72
|
|
|
73
|
+
## Corporate Network Certificate Errors
|
|
74
|
+
|
|
75
|
+
Desktop and CLI connections can use a company certificate authority trusted by
|
|
76
|
+
the operating system. If a connection encounters an untrusted certificate
|
|
77
|
+
chain, boxes.dev will load system certificates and retry while retaining its
|
|
78
|
+
protections against compromised certificates. A browser working does not prove
|
|
79
|
+
that every desktop connection will work: browsers and command-line tools can
|
|
80
|
+
use different certificate stores and proxy settings.
|
|
81
|
+
|
|
82
|
+
If a certificate error remains, ask the company's network administrator to
|
|
83
|
+
check that its inspection certificate is installed and trusted for HTTPS on
|
|
84
|
+
that computer. Fully quit and reopen the desktop app after certificate-store
|
|
85
|
+
changes, then retry the CLI command. Expired, revoked, and wrong-host
|
|
86
|
+
certificates need correction; do not disable certificate verification.
|
|
87
|
+
|
|
88
|
+
On some inspected Macs, reading system certificates can take several seconds.
|
|
89
|
+
The desktop app loads them once per launch when needed; each CLI command that
|
|
90
|
+
needs them can have the same delay. Commands that need no network connection
|
|
91
|
+
do not load system certificates.
|
|
92
|
+
|
|
93
|
+
An older CLI may be unable to download its own update on the inspected network.
|
|
94
|
+
On the user's own computer, use the curl installer described in
|
|
95
|
+
[CLI installation](cli.md#install), or update on a network permitted by the
|
|
96
|
+
company that does not inspect TLS. Installing through npm also depends on npm's
|
|
97
|
+
certificate configuration before boxes.dev can run. This recovery does not
|
|
98
|
+
configure proxy/PAC routing or change Codex and Claude's own certificate policy.
|
|
99
|
+
|
|
73
100
|
## A Build Or Command Was Terminated
|
|
74
101
|
|
|
75
102
|
When memory runs low, the boxes.dev memory watchdog may stop a large workload
|
|
@@ -77,9 +77,16 @@ beyond the user's agreed monitoring period.
|
|
|
77
77
|
|
|
78
78
|
Expiry or cancellation releases that request's protection without killing
|
|
79
79
|
commands or interrupting a foreground response. Other requests, background
|
|
80
|
-
work or the normal idle grace may keep the box awake.
|
|
81
|
-
|
|
82
|
-
|
|
80
|
+
work or the normal idle grace may keep the box awake. The separate automatic
|
|
81
|
+
background-task limits do not change when an explicit hold is saved.
|
|
82
|
+
|
|
83
|
+
The `keep-awake` commands report an active hold as `expired` once it reaches
|
|
84
|
+
its deadline. A saved response can go stale, but a hold can never protect the
|
|
85
|
+
box past its `expiresAtMs`. An expired hold stays visible until the user
|
|
86
|
+
dismisses it or a new request replaces it. Cancelling it succeeds and changes
|
|
87
|
+
nothing. Repeating `set` with its key also succeeds, but returns the same
|
|
88
|
+
expired hold without renewing it. A new hold needs a new key and must stay
|
|
89
|
+
within the agreed monitoring period.
|
|
83
90
|
|
|
84
91
|
## Costs and cancellation
|
|
85
92
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@boxes-dev/dvb-runtime",
|
|
3
|
-
"version": "1.0.
|
|
3
|
+
"version": "1.0.1112",
|
|
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-11-
|
|
80
|
+
"devboxReleasedAt": "2026-11-04T06:04:43Z"
|
|
81
81
|
}
|