@boxes-dev/dvb-runtime 1.0.1025 → 1.0.1026

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/dvb.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]="eefe7fac-f3db-52ff-9fb6-c9b945b86b1c")}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]="1070e312-ab17-583b-b7e7-a4fc9ca2001d")}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";
@@ -101146,8 +101146,8 @@ var init_otel = __esm({
101146
101146
  return trimmed && trimmed.length > 0 ? trimmed : void 0;
101147
101147
  };
101148
101148
  readBuildMetadata = () => {
101149
- const rawPackageVersion = "1.0.1025";
101150
- const rawGitSha = "72b94181c76002d6adbb16971c102a044295047c";
101149
+ const rawPackageVersion = "1.0.1026";
101150
+ const rawGitSha = "bb661b08ff5c9fc2e9417aabf09466ace1ac19a8";
101151
101151
  const packageVersion = typeof rawPackageVersion === "string" ? rawPackageVersion : void 0;
101152
101152
  const gitSha = typeof rawGitSha === "string" ? rawGitSha : void 0;
101153
101153
  return { packageVersion, gitSha };
@@ -133553,9 +133553,9 @@ var init_sentry = __esm({
133553
133553
  uncaughtExceptionMonitorInstalled = false;
133554
133554
  currentDevboxSentryUser = null;
133555
133555
  readBuildMetadata2 = () => {
133556
- const rawPackageVersion = "1.0.1025";
133557
- const rawGitSha = "72b94181c76002d6adbb16971c102a044295047c";
133558
- const rawSentryRelease = "boxes-dev-dvb@1.0.1025+72b94181c76002d6adbb16971c102a044295047c";
133556
+ const rawPackageVersion = "1.0.1026";
133557
+ const rawGitSha = "bb661b08ff5c9fc2e9417aabf09466ace1ac19a8";
133558
+ const rawSentryRelease = "boxes-dev-dvb@1.0.1026+bb661b08ff5c9fc2e9417aabf09466ace1ac19a8";
133559
133559
  const packageVersion = typeof rawPackageVersion === "string" ? rawPackageVersion : void 0;
133560
133560
  const gitSha = typeof rawGitSha === "string" ? rawGitSha : void 0;
133561
133561
  const sentryRelease = typeof rawSentryRelease === "string" ? rawSentryRelease : void 0;
@@ -138773,7 +138773,7 @@ var init_packageVersion = __esm({
138773
138773
  return path17.join(process.cwd(), "dvb");
138774
138774
  };
138775
138775
  readEmbeddedPackageVersion = () => {
138776
- const raw = "1.0.1025";
138776
+ const raw = "1.0.1026";
138777
138777
  return trimVersion(raw);
138778
138778
  };
138779
138779
  readNearestPackageMetadata = (basePath) => {
@@ -349576,7 +349576,9 @@ var init_claudeAuthProbe = __esm({
349576
349576
  }),
349577
349577
  "EOF",
349578
349578
  'cd "$tmpdir"',
349579
- `${REMOTE_MANAGED_CLAUDE_PATH} --devbox-disable-session-tracking -p --verbose --input-format stream-json --output-format stream-json --include-partial-messages --setting-sources user,project,local --permission-mode bypassPermissions --permission-prompt-tool stdio < "$input"`
349579
+ // Without --no-session-persistence, Claude saves the probe transcript and
349580
+ // the box imports it as a thread whose temporary working directory is gone.
349581
+ `${REMOTE_MANAGED_CLAUDE_PATH} --devbox-disable-session-tracking --no-session-persistence -p --verbose --input-format stream-json --output-format stream-json --include-partial-messages --setting-sources user,project,local --permission-mode bypassPermissions --permission-prompt-tool stdio < "$input"`
349580
349582
  ].join("\n");
349581
349583
  buildWriteManagedClaudeTokenToRemoteScript = ({
349582
349584
  authMode = "oauth",
@@ -359806,4 +359808,4 @@ react/cjs/react-jsx-runtime.development.js:
359806
359808
  *)
359807
359809
  */
359808
359810
 
359809
- //# debugId=eefe7fac-f3db-52ff-9fb6-c9b945b86b1c
359811
+ //# debugId=1070e312-ab17-583b-b7e7-a4fc9ca2001d
package/dist/bin/dvbd.mjs CHANGED
@@ -96328,8 +96328,8 @@ var init_otel = __esm({
96328
96328
  return trimmed && trimmed.length > 0 ? trimmed : void 0;
96329
96329
  };
96330
96330
  readBuildMetadata = () => {
96331
- const rawPackageVersion = "1.0.1025";
96332
- const rawGitSha = "72b94181c76002d6adbb16971c102a044295047c";
96331
+ const rawPackageVersion = "1.0.1026";
96332
+ const rawGitSha = "bb661b08ff5c9fc2e9417aabf09466ace1ac19a8";
96333
96333
  const packageVersion = typeof rawPackageVersion === "string" ? rawPackageVersion : void 0;
96334
96334
  const gitSha = typeof rawGitSha === "string" ? rawGitSha : void 0;
96335
96335
  return { packageVersion, gitSha };
@@ -128624,9 +128624,9 @@ var init_sentry = __esm({
128624
128624
  uncaughtExceptionMonitorInstalled = false;
128625
128625
  currentDevboxSentryUser = null;
128626
128626
  readBuildMetadata2 = () => {
128627
- const rawPackageVersion = "1.0.1025";
128628
- const rawGitSha = "72b94181c76002d6adbb16971c102a044295047c";
128629
- const rawSentryRelease = "boxes-dev-dvb@1.0.1025+72b94181c76002d6adbb16971c102a044295047c";
128627
+ const rawPackageVersion = "1.0.1026";
128628
+ const rawGitSha = "bb661b08ff5c9fc2e9417aabf09466ace1ac19a8";
128629
+ const rawSentryRelease = "boxes-dev-dvb@1.0.1026+bb661b08ff5c9fc2e9417aabf09466ace1ac19a8";
128630
128630
  const packageVersion = typeof rawPackageVersion === "string" ? rawPackageVersion : void 0;
128631
128631
  const gitSha = typeof rawGitSha === "string" ? rawGitSha : void 0;
128632
128632
  const sentryRelease = typeof rawSentryRelease === "string" ? rawSentryRelease : void 0;
@@ -130826,7 +130826,7 @@ var init_packageVersion = __esm({
130826
130826
  return path8.join(process.cwd(), "dvb");
130827
130827
  };
130828
130828
  readEmbeddedPackageVersion = () => {
130829
- const raw = "1.0.1025";
130829
+ const raw = "1.0.1026";
130830
130830
  return trimVersion(raw);
130831
130831
  };
130832
130832
  readNearestPackageMetadata = (basePath) => {
@@ -24,7 +24,7 @@ An automation has:
24
24
  - capacity behavior;
25
25
  - run history.
26
26
 
27
- Automation runs start new devboxes from the same reusable source as ordinary
27
+ By default, automation runs start new devboxes from the same reusable source as ordinary
28
28
  threads. For an ordinary project, that is the latest Template-box snapshot. For
29
29
  a Team Template member project, it is the Team Template's current saved
30
30
  version. Keep the source current when future automation runs need new
@@ -149,7 +149,33 @@ Requests support an optional `Idempotency-Key` header. Retrying the same
149
149
  normalized request with the same key returns the original run; reusing the key
150
150
  for different input returns a conflict.
151
151
 
152
- An accepted request returns `202`, the run id, a status URL, and the effective
152
+ To keep one devbox per issue, launch the first run without `target`, wait for
153
+ `thread_ready`, and save its returned `devboxId`. A later configurable request
154
+ can start a fresh run and conversation on that filesystem:
155
+
156
+ ```json
157
+ {
158
+ "prompt": "Implement the plan saved in issue-plan.md.",
159
+ "threadTitle": "Build the feature",
160
+ "target": { "kind": "existing_devbox", "devboxId": "<saved devboxId>" }
161
+ }
162
+ ```
163
+
164
+ Omit `target` to create a new devbox. Only devboxes created by the same
165
+ automation are eligible. Missing, still starting, archived, destroying, or inaccessible targets
166
+ return `409 devbox_unavailable`; no replacement devbox is created. A target
167
+ that becomes unavailable after acceptance can still cause a failed run during
168
+ startup. Use a new idempotency key for each workflow; changing the target also
169
+ changes the request for idempotency purposes.
170
+
171
+ Shared-devbox threads have separate conversations and share files. Pass context
172
+ through files or the prompt, and coordinate concurrent edits and branch changes.
173
+ Choose **Never** under **Devbox cleanup** for a persistent issue workspace.
174
+ The creating run retains cleanup ownership; existing cleanup preserves devboxes
175
+ with additional durable threads. The sidebar groups shared-devbox threads once,
176
+ while run history keeps each workflow separately.
177
+
178
+ An accepted request returns `202`, the run id, a status URL, nullable `devboxId`, and the effective
153
179
  thread title and agent controls without echoing the prompt. GET requests to the
154
180
  status URL require the same Bearer secret and report launch progress.
155
181
  `thread_ready` means the child thread exists and can be
@@ -160,7 +186,7 @@ runs in parallel; use `Idempotency-Key` to make retries reuse the original run.
160
186
 
161
187
  ## Capacity Behavior
162
188
 
163
- Each automation run needs awake devbox capacity. If you are at your awake devbox
189
+ Each new devbox needs awake devbox capacity. If you are at your awake devbox
164
190
  limit, the automation can be blocked unless you enable capacity behavior for
165
191
  that automation.
166
192
 
@@ -173,6 +199,11 @@ Capacity settings do not override billing limits or unavailable runtime state.
173
199
  They only help when the blocker is the awake devbox concurrency limit and an
174
200
  idle devbox can be slept.
175
201
 
202
+ An API request targeting an awake devbox needs no additional awake slot.
203
+ Sleeping targets wake if capacity is available. The sleep-idle option applies only
204
+ to new-devbox requests; a wake blocked by capacity produces a failed run with
205
+ `startup_active_fork_limit_reached` at its status URL.
206
+
176
207
  ## Automation Devbox Cleanup
177
208
 
178
209
  Scheduled and API automations whose runs stay nested under the automation can
@@ -104,7 +104,7 @@ snapshot used by future devboxes:
104
104
  dvb-onbox snapshot --json
105
105
  ```
106
106
 
107
- Snapshot creation works only from the Template box. It is a user-visible,
107
+ This command works only on the Template box itself. It is a user-visible,
108
108
  state-changing operation and should run only when the user asks to take or
109
109
  refresh a snapshot and the environment is ready to become the basis for future
110
110
  devboxes. The requesting Codex or Claude agent can remain active: boxes.dev will
@@ -112,6 +112,28 @@ pause it only during capture and resume it on the Template box. Future devboxes
112
112
  will receive the saved files and transcript history, but they will not continue
113
113
  the copied agent process.
114
114
 
115
+ ### Edit the Template box from a devbox
116
+
117
+ From a devbox in a project with its own Template box, an agent with the
118
+ `edit-template-box` permission for its current thread can change the project's
119
+ Template box and save a snapshot without a thread on the Template box:
120
+
121
+ ```bash
122
+ dvb-onbox template-box exec -- git -C /home/boxes/example status --short
123
+ dvb-onbox template-box exec --cwd /home/boxes/example -- direnv allow
124
+ dvb-onbox template-box run --script-file /home/boxes/setup-change.sh \
125
+ --idempotency-key <stable-key> --json
126
+ dvb-onbox template-box snapshot --json
127
+ ```
128
+
129
+ Each command wakes a sleeping Template box and runs as its `boxes` user.
130
+ `exec` runs one noninteractive command for up to 120 seconds with 1 MiB of
131
+ output per stream. `run` sends a regular script file of up to 3 MiB to `bash`,
132
+ runs it for up to 20 minutes, and returns up to 4 MiB per output stream; use it
133
+ to write files on the Template box. `snapshot` waits for the new snapshot that
134
+ future devboxes will use. Take one only when the user wants the change to reach
135
+ future devboxes. Ordinary shell commands still act on the current devbox.
136
+
115
137
  ## Devbox Lifecycle And Template Maintenance
116
138
 
117
139
  From the project's current ordinary Template box, an agent can inspect and edit
@@ -218,8 +240,10 @@ dvb-onbox permissions request \
218
240
  The request values are `create-devboxes-and-threads`,
219
241
  `create-team-templates`, `update-thread-titles`,
220
242
  `move-devboxes-to-folders`, `create-devbox-folders`,
221
- `edit-devbox-lifecycle`, `edit-template-maintenance`, and `destroy-devbox`. Add `--json` for a
222
- stable structured result.
243
+ `edit-devbox-lifecycle`, `edit-template-maintenance`, `destroy-devbox`,
244
+ `read-project-threads`, `read-user-threads`, `read-shared-threads`,
245
+ `read-team-threads`, `edit-template-box`, and `edit-team-template`. Add
246
+ `--json` for a stable structured result.
223
247
 
224
248
  The command creates one request for the exact managed thread and source box,
225
249
  then waits up to ten minutes while the owner sees **Deny**, **Allow**, and,
@@ -229,7 +253,17 @@ for every agent on that source box until the owner turns it off; it is not a
229
253
  one-operation grant. **Deny** declines this request without changing permission
230
254
  settings. An agent cannot answer its own request.
231
255
 
232
- For folder access, thread titles, and creating devboxes and threads, the owner
256
+ `edit-template-box` and `edit-team-template` work differently. They let only
257
+ the agent in the requesting thread edit the Template its devbox came from, and
258
+ the owner sees **Deny** and **Allow for 3 hours**. The grant expires 3 hours
259
+ after approval. Other threads and boxes never receive it, and no Agent
260
+ permissions switch or project setting can enable it. Request
261
+ `edit-template-box` from a devbox in a project with its own Template box.
262
+ Request `edit-team-template` from a devbox in a Team Template project; only a
263
+ team admin can receive it. After the grant expires, the next command reports
264
+ the missing permission and the agent needs a new request.
265
+
266
+ For thread reads, folder access, thread titles, and creating devboxes and threads, the owner
233
267
  can choose **Always allow for project** directly.
234
268
  This will enable the project's shared permission and make the requesting box
235
269
  use it. All existing and future devboxes will follow that setting, except
@@ -566,11 +600,63 @@ their devboxes or claiming a live input surface. The source box's live **Create
566
600
  devboxes and threads** permission is checked on every observation and control.
567
601
  Prompt files are limited to 32 KiB.
568
602
 
569
- Delegation does not grant destruction permission. `dvb-onbox` does not expose
570
- project inventory, arbitrary direct exec, services, or generic port and machine
603
+ Delegation does not grant destruction permission or access to unrelated
604
+ threads. Read-only thread and project discovery has its own permission below.
605
+ `dvb-onbox` does not expose arbitrary direct exec, services, or generic machine
571
606
  management. The current-box public link commands above are its only port-control
572
607
  surface.
573
608
 
609
+ ## Read Other Threads
610
+
611
+ With **Read other threads** enabled in Agent permissions, agents can discover
612
+ and read threads beyond their delegated children. The setting applies to every
613
+ agent on the source box. It is off by default, inherits the project's setting,
614
+ and can be overridden on a box. Higher levels include the preceding levels:
615
+ this project, all your projects, your threads plus shared threads, and your
616
+ threads plus teammates' threads you can access. This permission never grants
617
+ control of other threads.
618
+
619
+ ```bash
620
+ dvb-onbox threads access --json
621
+ dvb-onbox threads list --scope project --json
622
+ dvb-onbox threads projects --scope user --json
623
+ dvb-onbox threads list --scope user --project <project-id> --json
624
+ dvb-onbox threads list --scope shared --json
625
+ dvb-onbox threads list --scope team --owner <owner-id> --project <project-id> --json
626
+ dvb-onbox threads read --scope shared --thread <thread-id-or-share-link> --turns 20 --json
627
+ ```
628
+
629
+ `access` reports the grant, team visibility, and available scopes. `project`
630
+ selects your current project; `user` selects your projects. `shared` lists
631
+ teammate threads whose invitation link you previously opened and which still
632
+ grant access, including ones removed from Shared with me. Pins alone and
633
+ unopened links do not qualify. A supplied invitation URL can be read without
634
+ saving or claiming it. A permanent thread URL does not grant access.
635
+
636
+ `team` excludes your own threads and follows team settings: Shared links only
637
+ disables general discovery, Thread titles permits metadata, and All threads
638
+ permits transcripts. Valid personal shares can grant transcript access under
639
+ Thread titles. Private threads and revoked access remain unavailable.
640
+
641
+ Use project IDs and owner IDs returned by `projects` or `list`, not repository
642
+ names. Project filters apply to `user`, `shared`, and `team`; owner filters
643
+ apply to `shared` and `team`. Each listing page examines up to 50 candidate
644
+ records; filters and access checks can leave fewer results or an empty page.
645
+ Pass `pagination.nextCursor` as `--cursor` when you need more results, and
646
+ check `pagination.complete` to know when the inventory ends. Scoped commands
647
+ do not accept `--all`. Project discovery can repeat a project across pages;
648
+ deduplicate by project ID. Add `--include-archived` to thread listings for archived work.
649
+
650
+ Reads return stored visible user/assistant messages with older-page cursors.
651
+ They may lag active work and shorten long messages. They do not wake boxes,
652
+ mark threads read, claim links, or expose full tool logs. Without `--scope`,
653
+ the existing `list` and `read` commands still select delegated children only.
654
+
655
+ If a needed scope reports `thread_read_access_disabled`, request the matching
656
+ `read-project-threads`, `read-user-threads`, `read-shared-threads`, or
657
+ `read-team-threads` permission. Team visibility limits require a team setting
658
+ change; an agent permission cannot override them.
659
+
574
660
  ## Destroy And Archive The Current Devbox
575
661
 
576
662
  An agent can request destruction of its own ordinary devbox with:
@@ -790,9 +876,11 @@ Run `dvb-onbox box status --json` before choosing a workflow:
790
876
  box. To edit an associated Team Template, use **Work on a Team Template from
791
877
  an ordinary Template box**. To create a new definition from the current
792
878
  project, use **Create a Team Template from this project**.
793
- - `devbox`: local edits affect only this devbox. These creation and remote
794
- editing commands require an ordinary Template box; do not treat this devbox
795
- as the shared template.
879
+ - `devbox`: local edits affect only this devbox; do not treat it as the shared
880
+ template. In a Team Template project, a team admin's agent can edit that
881
+ Team Template after the user allows `edit-team-template` for the current
882
+ thread. Use **Work on a Team Template from a member devbox**. Creating a
883
+ Team Template requires an ordinary Template box.
796
884
 
797
885
  Skill availability is not proof of an editing association. If role inspection
798
886
  fails, report the command's error and use only the operations whose target is
@@ -1095,3 +1183,45 @@ second time. The command reports a request ID and may say that its output is
1095
1183
  unavailable; verify filesystem state before deciding whether another command
1096
1184
  is appropriate. Retrying the same `push` request after an uncertain response
1097
1185
  recovers its recorded result instead of writing the destination twice.
1186
+
1187
+ ### Work on a Team Template from a member devbox
1188
+
1189
+ This section applies to a devbox in a Team Template project whose user is a
1190
+ team admin. Ask the user for access, then request it for the current thread:
1191
+
1192
+ ```bash
1193
+ dvb-onbox permissions request --permission edit-team-template --json
1194
+ ```
1195
+
1196
+ After the user chooses **Allow for 3 hours**, connect this thread to the Team
1197
+ Template's editing session:
1198
+
1199
+ ```bash
1200
+ dvb-onbox team-template edit-box open --idempotency-key <stable-key> --json
1201
+ ```
1202
+
1203
+ `open` uses the Team Template of the devbox's project. It reuses the user's
1204
+ current editing session or starts a new one, which can take several minutes,
1205
+ and waits until the session is connected to this thread. It fails while
1206
+ another admin is editing the Team Template or another agent is connected to
1207
+ the session. The result includes the Team Template id and `editBox.id`. The
1208
+ target commands from the previous section then act on that editing machine:
1209
+
1210
+ ```bash
1211
+ dvb-onbox team-template exec --template <team-template-id> -- git status --short
1212
+ dvb-onbox team-template push --template <team-template-id> \
1213
+ --source /home/boxes/file-on-devbox \
1214
+ --destination /home/boxes/file-in-team-template
1215
+ dvb-onbox team-template edit-box run --edit-box <edit-box-id> \
1216
+ --script-file /home/boxes/setup-change.sh --idempotency-key <stable-key> --json
1217
+ dvb-onbox team-template edit-box status --edit-box <edit-box-id> --json
1218
+ dvb-onbox team-template edit-box save --edit-box <edit-box-id> \
1219
+ --idempotency-key <stable-key> --json
1220
+ ```
1221
+
1222
+ Save only when the user asked to publish the change. `save` uses the normal
1223
+ verified save pipeline, waits for it to finish, and ends this thread's access
1224
+ to that editing session. Access also ends when the grant expires or an admin
1225
+ saves the session in the desktop app. To make more changes, run `open` again
1226
+ with a new key. Member-file requirements and Team Template creation are not
1227
+ available from a devbox.
@@ -607,13 +607,13 @@ source thread's files and working directory. New devbox snapshots the exact
607
607
  Template box or devbox that hosts the source, then creates an independent
608
608
  devbox with that filesystem state. This includes the current working tree when
609
609
  the source is already a devbox. The source remains unchanged, and the source
610
- and child can continue independently. Mobile exposes only exact `/fork`, not a
611
- persistent action on each historical turn. Fork controls are hidden when the
612
- connected runtime does not support native Codex thread branching and are
613
- unavailable while the source is working. Desktop remembers confirmed support
614
- for each Template box and devbox, so its fork controls remain available while
615
- reconnecting. If you choose a fork action then, boxes.dev will connect to the
616
- source before creating the new chat.
610
+ and child can continue independently. On mobile, long-press a completed reply
611
+ to choose **Continue in current box** or **Continue in new devbox**. Fork
612
+ controls are unavailable while the source is working, but they don't wait for
613
+ the app to connect to the source machine. When you choose a fork action,
614
+ boxes.dev will connect to the source, waking it if needed, before creating the
615
+ new chat. If the source machine's boxes.dev service is too old to branch, the
616
+ new chat will show an error.
617
617
 
618
618
  Codex active turns can usually be interrupted with the Stop button or Escape.
619
619
  If interruption has already been requested, the UI shows that the turn is
@@ -186,6 +186,18 @@ before asking you to sign in again.
186
186
 
187
187
  ## Codex Stopped Before Finishing
188
188
 
189
+ If a large Codex thread asks you to reload or update boxes.dev, press Cmd+R in
190
+ the desktop app. On mobile, open **Settings → About → Release details** and
191
+ choose **Check for update**. If the installed app has no compatible update and
192
+ the message persists, install the latest app version or contact support.
193
+ Reloading the desktop app does not stop the agent running on the devbox.
194
+
195
+ If Retry says the thread is too large, send a new message to continue.
196
+ The failed turn stays in the history.
197
+
198
+ If the message says an older thread is too large to reopen, start a new thread
199
+ to continue. Updating the app does not remove this limitation for older threads.
200
+
189
201
  Codex failure cards distinguish several failure layers so the recovery step
190
202
  matches what happened:
191
203
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@boxes-dev/dvb-runtime",
3
- "version": "1.0.1025",
3
+ "version": "1.0.1026",
4
4
  "type": "module",
5
5
  "license": "UNLICENSED",
6
6
  "imports": {
@@ -77,5 +77,5 @@
77
77
  "e2b": "^2.18.0",
78
78
  "ink-testing-library": "^4.0.0"
79
79
  },
80
- "devboxReleasedAt": "2026-09-25T02:30:02Z"
80
+ "devboxReleasedAt": "2026-09-25T22:07:59Z"
81
81
  }