@boxes-dev/dvb-runtime 1.0.1109 → 1.0.1111

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.
@@ -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 Team
115
- Template 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. Existing threads
117
- continue in the working directory they were originally started with.
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
 
@@ -443,6 +445,15 @@ to answer, or stop the turn. Automated turns can wait for an answer too;
443
445
  don't rely on an unanswered request timing out. If an older app cannot show
444
446
  the request, update boxes.dev and reopen the thread.
445
447
 
448
+ Pending Codex questions and forms can appear while the app is still connecting
449
+ to the agent. Read the request while you wait; answering, approving, or opening
450
+ a service's browser flow requires the connection. The initial preview omits
451
+ prefilled form values and browser destinations. A long request may show a
452
+ shortened preview first. Once connected, the app shows only requests the agent
453
+ still has pending, so a question answered elsewhere disappears.
454
+ Read-only thread viewers can see the pending request, but only the owner can
455
+ answer it.
456
+
446
457
  ## Plugins
447
458
 
448
459
  Open **Integrations → Codex/Claude Plugins** in the desktop app. The page talks
@@ -800,12 +811,13 @@ answer. Choose an option to advance to the next question or send the answers
800
811
  on the last question. For a custom answer, type it and select **Continue** or
801
812
  **Send**. Your answer will reach the running turn, and any text or attachments
802
813
  already in the reply box will stay there. Use **Skip** to
803
- leave a question unanswered. Once you send or skip the last question, the panel
804
- closes for the rest of the turn. **Dismiss** minimizes the panel instead;
805
- select **Answer questions** to reopen it. Historical questions do not
806
- automatically reopen when you return to the thread; any you have not sent or
807
- skipped stay under **Answer questions**. An untouched panel minimizes after 30
808
- seconds without sending anything. If
814
+ leave a question unanswered. When several questions are waiting, the panel
815
+ shows your position among them; use its arrows or the Left and Right arrow keys
816
+ to move between them. Once you send or skip the last question, the panel
817
+ closes for the rest of the turn. The X or Esc minimizes the panel instead,
818
+ without stopping the turn; select **Answer questions** to reopen it. Historical
819
+ questions do not automatically reopen when you return to the thread; any you
820
+ have not sent or skipped stay under **Answer questions**. If
809
821
  the turn ends, edited answers that you have not sent will move to the reply box.
810
822
  Answers reach the running turn even if ordinary replies are set to Queue.
811
823
 
@@ -839,16 +851,19 @@ older boxes.dev service won't show a live list
839
851
  until its normal automatic update runs.
840
852
 
841
853
  Codex also shows context-window usage when available. When the context window
842
- gets full, the composer can show an auto-compaction warning and a Compact now
843
- action.
854
+ gets full, the composer can show an auto-compaction warning. On desktop, clicking
855
+ the context meter in a Codex or Claude thread offers **Compact context now** at
856
+ any time. Hovering over the meter shows the same details, and offers that action
857
+ only at high usage, with a confirmation first.
844
858
 
845
859
  The Codex rate-limit indicator shows remaining session, weekly, and available
846
860
  model-specific quotas with countdowns to their resets. Limits for the selected
847
861
  model use warning colors; quotas for other models remain visible in muted
848
862
  colors. When the connected ChatGPT account has credits, the indicator also
849
863
  shows the credit balance. Codex keeps working on credits after the ordinary
850
- session or weekly limit runs out, so that limit shows an amber warning instead
851
- of the red alert, and the balance is marked in use. When the account has banked
864
+ session or weekly limit runs out. That limit shows red at 0% and the balance is
865
+ marked In use, while the indicator icon stays amber instead of showing the red
866
+ alert. When the account has banked
852
867
  usage limit resets, the same indicator shows how many are available and when
853
868
  the next three expire; that row is omitted when reset inventory is unavailable.
854
869
  The indicator's details name the account the limits belong to. When Codex is
@@ -936,7 +951,8 @@ supports slash commands when the thread surface has command lookup
936
951
  enabled. Type `/` in a Claude reply box on desktop or mobile to list Claude's
937
952
  commands and skills; choosing one adds it to the message. Skill rows show
938
953
  Project, Personal, Plugin, or Account (skills synced from the claude.ai
939
- account). Before the box's live list is ready, including in a new thread, the composer
954
+ account). When Claude runs in the project directory, the list also includes the
955
+ 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
940
956
  uses the project's most recently opened Claude thread for project and personal
941
957
  skills, and the selected Claude account's last list for its synced skills and
942
958
  Claude's built-in commands, which depend on the account's plan. On mobile, the
@@ -1208,7 +1224,8 @@ cancellation, before an active response exists, still cancels the pending start.
1208
1224
  Claude steers already accepted by Claude are different: Stop may leave them
1209
1225
  waiting for Claude's next response, and they cannot be taken back through the
1210
1226
  Queue controls. A steer that Claude already read remains in the thread even
1211
- if its response is stopped.
1227
+ if its response is stopped. If Claude doesn't respond to Stop, any steer it
1228
+ hasn't read yet returns to the user's reply box unsent.
1212
1229
 
1213
1230
  Interrupt availability depends on the agent, current turn state, and runtime
1214
1231
  state. If the UI says interrupt is unavailable, wait for the current operation
@@ -1275,7 +1292,8 @@ activity orders, each row's time and date group show its last activity.
1275
1292
  an agent started under the devbox that started it. It is off by default and
1276
1293
  saved on the account, so every computer and phone follows it. A slim row under
1277
1294
  the parent shows whether any of those devboxes are working, unread, or need the
1278
- user, and selecting the row opens them. On desktop the row also counts them.
1295
+ user, and selecting the row shows or hides them. On desktop the row starts
1296
+ closed and also counts them; on a phone it starts open.
1279
1297
  When a devbox started only one, that devbox shows directly under its parent
1280
1298
  without the row.
1281
1299
  Devboxes nest under the devbox that started them at every level, and in the
@@ -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
@@ -366,6 +393,22 @@ local port.
366
393
  If there are no forwarded ports, make sure the app or service is actually
367
394
  running inside the selected box.
368
395
 
396
+ ## Public link or Project URL timed out
397
+
398
+ A public link can show `Application timed out` (HTTP 504) when the app sends
399
+ nothing for 2 minutes while the request waits for its response. A routed
400
+ Project URL returns 504 when the app does not send its response status and
401
+ headers within 10 seconds. If the app sent only its headers, either surface
402
+ returns an unavailable-application error (HTTP 502) after 2 minutes instead.
403
+ Raising the app's own timeout does not extend these limits. If the caller gave
404
+ up sooner, check its own timeout. The work the
405
+ request started may still be running or may have finished, so check the app's
406
+ own receipt or job status before retrying. Reuse the original idempotency key
407
+ only if the app or API supports one. To avoid the timeout, stream progress or
408
+ return a job ID; see
409
+ [Public app links](ports-terminal-and-runtime.md#public-app-links) for the
410
+ limits and both patterns.
411
+
369
412
  ## Files Or Git Will Not Load
370
413
 
371
414
  Files and git status require the selected box to be awake. Wake the box
@@ -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. Expired holds remain
81
- visible until dismissed. The separate automatic background-task limits do
82
- not change when an explicit hold is saved.
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.1109",
3
+ "version": "1.0.1111",
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-31T08:09:38Z"
80
+ "devboxReleasedAt": "2026-11-03T05:30:51Z"
81
81
  }