@boxes-dev/dvb-runtime 1.0.1114 → 1.0.1116
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 +1525 -902
- package/dist/bin/dvbd.mjs +923 -347
- package/dist/product-docs/references/automations.md +2 -0
- package/dist/product-docs/references/desktop-workbench.md +10 -0
- package/dist/product-docs/references/files-git-and-review.md +8 -3
- package/dist/product-docs/references/fork-workflows.md +5 -0
- package/dist/product-docs/references/onbox-agent-tools.md +95 -10
- package/dist/product-docs/references/slack.md +3 -1
- package/dist/product-docs/references/team-template.md +10 -1
- package/dist/product-docs/references/threads-and-agents.md +15 -3
- package/dist/product-docs/references/troubleshooting.md +7 -2
- package/package.json +3 -3
|
@@ -280,6 +280,8 @@ title, agent settings, placement, and notification behavior. Omit `threadTitle`
|
|
|
280
280
|
and `execution` for this target. Omit `prompt` to send the saved automation prompt.
|
|
281
281
|
The automation's devbox cleanup and Slack output destinations do not apply to
|
|
282
282
|
these follow-ups.
|
|
283
|
+
A Claude follow-up can run once its response has ended, even if a background
|
|
284
|
+
command is still running. The command will continue running.
|
|
283
285
|
A sleeping target's box will wake if capacity is available. An awake target
|
|
284
286
|
needs no additional awake slot.
|
|
285
287
|
|
|
@@ -739,6 +739,16 @@ the user to complete the passkey flow themselves; the resulting Browser profile
|
|
|
739
739
|
session remains shared with the agent afterwards. If the user disabled passkey
|
|
740
740
|
forwarding, they can re-enable it under **Settings > Browser**.
|
|
741
741
|
|
|
742
|
+
When an agent needs the user to act in the Browser, such as signing in or
|
|
743
|
+
completing a passkey prompt, it can run `dvb-onbox browser request` from its
|
|
744
|
+
thread (see `onbox-agent-tools.md`). The titlebar's Browser button then shows a
|
|
745
|
+
small blue dot, the same dot the thread list uses for unread threads, while a
|
|
746
|
+
thread on that box is selected. The dot pops in with two rings when it appears
|
|
747
|
+
during use and stays still after that. It disappears when the user opens the
|
|
748
|
+
Browser on that box, when they send their next message in the requesting
|
|
749
|
+
thread, or when the agent withdraws the request. The button's label and icon
|
|
750
|
+
don't change, and the mobile app doesn't show the dot.
|
|
751
|
+
|
|
742
752
|
Users can also review specific page elements from the Browser. Select the
|
|
743
753
|
review control to enter a focused **Reviewing** mode, hover to preview a target,
|
|
744
754
|
and click an element to open a compact comment editor beside it. The cancel
|
|
@@ -32,8 +32,8 @@ right preview. For images, click the preview to open a
|
|
|
32
32
|
full-screen, zoomable view (scroll or use the toolbar to zoom, drag to pan); the
|
|
33
33
|
full-screen Files window zooms the image in place instead. Clicking an image
|
|
34
34
|
file link in a thread opens Files and also opens that full-screen image view.
|
|
35
|
-
Files that cannot be previewed inline
|
|
36
|
-
|
|
35
|
+
Files that cannot be previewed inline, including images, videos, and PDFs over
|
|
36
|
+
100 MB, open in a download-only view.
|
|
37
37
|
|
|
38
38
|
Supported text files can also be edited directly in Files. Changes auto-save
|
|
39
39
|
after you stop typing and before file switches, pane close, or pop-out changes.
|
|
@@ -65,6 +65,11 @@ to reveal the saved file (Open in folder on Windows and Linux). When the selecte
|
|
|
65
65
|
file has Git changes, use Git/Review from the file header to open the matching
|
|
66
66
|
diff in Git/Review.
|
|
67
67
|
|
|
68
|
+
The desktop app downloads files up to 5 GiB each, and active downloads count
|
|
69
|
+
toward the same 10 GiB per-user limit as uploads. A box or desktop app awaiting
|
|
70
|
+
an update may still have the previous 100 MB download limit; retry after it
|
|
71
|
+
updates. The mobile app downloads files up to 100 MB.
|
|
72
|
+
|
|
68
73
|
### Creating And Managing Files And Folders
|
|
69
74
|
|
|
70
75
|
Use New file or New folder above the tree. The destination starts at the
|
|
@@ -140,7 +145,7 @@ Uploads can run in parallel. The file tree shows a slim row for each active
|
|
|
140
145
|
upload with progress; successful rows clear after completion, and failed rows
|
|
141
146
|
can be retried or dismissed. After successful uploads, the target directory
|
|
142
147
|
reloads. Desktop uploads support files up to 5 GiB each, with up to 10 GiB of
|
|
143
|
-
active uploads per user at a time. Before uploading, boxes.dev checks the
|
|
148
|
+
active uploads and downloads per user at a time. Before uploading, boxes.dev checks the
|
|
144
149
|
box's free disk space and warns if the files will not fit. It checks again
|
|
145
150
|
before copying each file onto the box. Free up space or choose fewer files
|
|
146
151
|
if an upload is blocked. A box awaiting an update may still have the previous
|
|
@@ -164,6 +164,11 @@ existing devboxes, running agent sessions, or Template box threads. Clearing
|
|
|
164
164
|
the setting removes an older boxes.dev-managed project-guidance block from
|
|
165
165
|
subsequently created devboxes while preserving other user and managed content.
|
|
166
166
|
|
|
167
|
+
In a project that a Team Template manages, each new devbox also gets the
|
|
168
|
+
template's current agent guidance, placed before the project's own guidance.
|
|
169
|
+
A team admin's change to the template's guidance therefore reaches these
|
|
170
|
+
projects' new devboxes without editing each project.
|
|
171
|
+
|
|
167
172
|
Creation uses the guidance current when the devbox is prepared, including for
|
|
168
173
|
environment-only creation and paused or draft-prepared devboxes. If guidance
|
|
169
174
|
cannot be fully applied, devbox creation still succeeds and boxes.dev shows a
|
|
@@ -294,8 +294,13 @@ start from the Template box's saved checkout.
|
|
|
294
294
|
Inspect `origin` to identify the source Team Template and saved version, the
|
|
295
295
|
captured `projectConfigurationInput`, and its `configurationSource` when
|
|
296
296
|
recorded. These show what was copied when the project was created. Compare
|
|
297
|
-
those inputs with `team-template settings get` to explain inherited
|
|
298
|
-
changing template defaults will not replace an existing project's copy.
|
|
297
|
+
those inputs with `team-template settings get` to explain inherited settings;
|
|
298
|
+
changing template defaults will not replace an existing project's copy. Agent
|
|
299
|
+
Guidance is the exception for a project the Team Template manages
|
|
300
|
+
(`kind: team_template_managed`): its new devboxes get the template's current
|
|
301
|
+
guidance, a blank line, and then the project's own `lifecycle.agentGuidance`.
|
|
302
|
+
A project created before this behavior may still hold a copy of the template's
|
|
303
|
+
guidance in its own field, so its devboxes would get that text twice.
|
|
299
304
|
Older projects without recorded creation inputs report a null origin.
|
|
300
305
|
|
|
301
306
|
Team Template output includes its identity, description, source/repositories,
|
|
@@ -326,6 +331,29 @@ including from an independent project created from it. Request only the minimum
|
|
|
326
331
|
permission returned by a denied write. Agent permission defaults remain
|
|
327
332
|
user-only even with an editing grant.
|
|
328
333
|
|
|
334
|
+
#### Teammates' project settings
|
|
335
|
+
|
|
336
|
+
A team admin's agent can open any project owned by a current member of the
|
|
337
|
+
team, including a teammate's project or another of the admin's own projects,
|
|
338
|
+
by adding `--project` with a `projectId` from `team settings get`:
|
|
339
|
+
|
|
340
|
+
```bash
|
|
341
|
+
dvb-onbox project settings get --project <project-id> --json
|
|
342
|
+
dvb-onbox project settings set --settings-file /home/boxes/settings-edit.json --project <project-id> --json
|
|
343
|
+
```
|
|
344
|
+
|
|
345
|
+
Reads need only team admin and return that project's settings without its
|
|
346
|
+
environment metadata. Saves also need the thread's `edit-team-template` grant.
|
|
347
|
+
They support `lifecycle`, `git`, `ports_enabled`, `ports`, `default_branches`,
|
|
348
|
+
`storage`, `browser`, `agent_settings`, `maintenance`, `maintenance_delete`,
|
|
349
|
+
`maintenance_watches`, and the Project URL sections. Other sections fail with
|
|
350
|
+
`member_project_section_unsupported`, because they act on the calling box or
|
|
351
|
+
thread, the owner's account, the owner's connected integrations, or the
|
|
352
|
+
owner's own environment values and member files. `admin_required` means the
|
|
353
|
+
user isn't a team admin; `project_not_found` means no current member of the
|
|
354
|
+
team owns that project. Saved changes apply to the owner's future devboxes,
|
|
355
|
+
and the owner isn't notified.
|
|
356
|
+
|
|
329
357
|
### Integration status and setup
|
|
330
358
|
|
|
331
359
|
The project read includes `integrations.isTeamAdmin` and
|
|
@@ -573,8 +601,12 @@ dvb-onbox team settings set --settings-file /home/boxes/team-edit.json --json
|
|
|
573
601
|
|
|
574
602
|
Reads list the team's name, members and roles, invites, allowed domains,
|
|
575
603
|
teammate thread access policy, idle sleep default, and static egress
|
|
576
|
-
destinations.
|
|
577
|
-
|
|
604
|
+
destinations. `memberProjects` lists every project owned by a current member,
|
|
605
|
+
including the admin's own, with its `projectId`, `alias`, `kind`,
|
|
606
|
+
`teamTemplateId`, `archived`, and `owner`; pass a `projectId` to
|
|
607
|
+
[`project settings --project`](#teammates-project-settings). Changes need the
|
|
608
|
+
thread's `edit-team-template` grant; only team admins can read or change these
|
|
609
|
+
settings.
|
|
578
610
|
|
|
579
611
|
| Section | Fields |
|
|
580
612
|
| --- | --- |
|
|
@@ -1042,9 +1074,10 @@ own environment and member-file values, to share the current thread, and to
|
|
|
1042
1074
|
change the user's [account preferences](#account-preferences). It cannot change
|
|
1043
1075
|
agent permission defaults. Request
|
|
1044
1076
|
`edit-team-template` from any box in one of the user's projects to edit
|
|
1045
|
-
[team settings](#team-settings)
|
|
1046
|
-
|
|
1047
|
-
|
|
1077
|
+
[team settings](#team-settings), the settings of any project on the team
|
|
1078
|
+
([`--project`](#teammates-project-settings)), and, in a project created from a
|
|
1079
|
+
Team Template, that Team Template's settings, including environment and
|
|
1080
|
+
member-file definitions; only a team admin can receive it. Request `edit-personal-environment` from a devbox in a Team
|
|
1048
1081
|
Template project to edit the user's own environment variables for that
|
|
1049
1082
|
project; any member can receive it, and a thread that already has
|
|
1050
1083
|
`edit-team-template` or `edit-project-settings` does not need it. A thread holds one of these grants at a
|
|
@@ -1113,7 +1146,7 @@ dvb-onbox threads get-title --json
|
|
|
1113
1146
|
|
|
1114
1147
|
The result includes the title source (`manual`, `generated`, `first_message`,
|
|
1115
1148
|
or `placeholder`) and whether title editing is enabled on the current box. The
|
|
1116
|
-
command
|
|
1149
|
+
command works even when editing is disabled.
|
|
1117
1150
|
|
|
1118
1151
|
Users can independently enable **Update thread titles** from the **Agent
|
|
1119
1152
|
permissions** control in an owned Codex or Claude thread header. That header
|
|
@@ -1134,8 +1167,14 @@ dvb-onbox threads set-title --title "New central topic" --json
|
|
|
1134
1167
|
The title must be non-empty and at most 120 Unicode characters. Managed-agent
|
|
1135
1168
|
guidance limits edits to meaningful central-topic changes and requires the
|
|
1136
1169
|
agent to ask before replacing a manual title. The command does not rename a
|
|
1137
|
-
provider-native Codex or Claude session and cannot clear
|
|
1138
|
-
|
|
1170
|
+
provider-native Codex or Claude session and cannot clear a title.
|
|
1171
|
+
|
|
1172
|
+
Only the project coordinator can name another thread, with
|
|
1173
|
+
`--thread <thread-id>` on `get-title` or `set-title`. It can name any of the
|
|
1174
|
+
user's unarchived threads in its project, including Template box threads,
|
|
1175
|
+
except its own chat; other targets return `thread_not_found`. Its own **Update
|
|
1176
|
+
thread titles** permission decides whether it can rename them. Other agents
|
|
1177
|
+
that pass `--thread` get `invalid_request`.
|
|
1139
1178
|
|
|
1140
1179
|
When a user-required title change returns `title_editing_disabled`, request
|
|
1141
1180
|
only `update-thread-titles` through the Agent permissions command above. Do not
|
|
@@ -1247,6 +1286,39 @@ codes:
|
|
|
1247
1286
|
| `unauthorized` | boxes.dev rejected this box's credentials. | `false` |
|
|
1248
1287
|
| `service_unavailable` | Presence is temporarily unavailable. Wait a minute and try again. | `true` |
|
|
1249
1288
|
|
|
1289
|
+
## Browser Requests
|
|
1290
|
+
|
|
1291
|
+
When the user has to do something in the box's Browser themselves, such as
|
|
1292
|
+
signing in, completing a passkey prompt, or solving a captcha, an agent can
|
|
1293
|
+
point them to it:
|
|
1294
|
+
|
|
1295
|
+
```bash
|
|
1296
|
+
dvb-onbox browser request
|
|
1297
|
+
dvb-onbox browser clear-request
|
|
1298
|
+
```
|
|
1299
|
+
|
|
1300
|
+
`request` puts a small blue dot on the Browser button in the owner's desktop
|
|
1301
|
+
app while a thread on this box is selected. The dot stays until one of these
|
|
1302
|
+
happens:
|
|
1303
|
+
|
|
1304
|
+
- The owner opens the Browser on this box, which clears every request on the
|
|
1305
|
+
box.
|
|
1306
|
+
- The owner sends their next message in the requesting thread. Scheduled
|
|
1307
|
+
checks, automation runs, automatic pull request follow-ups, and messages
|
|
1308
|
+
from other agents don't count.
|
|
1309
|
+
- The agent runs `clear-request`.
|
|
1310
|
+
|
|
1311
|
+
Requests from archived or deleted threads stop showing. A request carries no
|
|
1312
|
+
text, so the agent should still say in its reply what the user needs to do.
|
|
1313
|
+
Both commands act on the managed thread that runs them, take no thread ID, and
|
|
1314
|
+
need no permission. With `--json`, they print
|
|
1315
|
+
`{"schemaVersion": 1, "ok": true, "operation": "request"}` or
|
|
1316
|
+
`"operation": "clear"`. `thread_context_unavailable` means boxes.dev couldn't
|
|
1317
|
+
match the command to a managed Codex or Claude thread running on this box: it
|
|
1318
|
+
ran outside a managed thread, its thread identity didn't resolve to a thread on
|
|
1319
|
+
this box, or the box isn't running. `daemon_update_required` means the box's
|
|
1320
|
+
boxes.dev service predates the command. The mobile app doesn't show the dot.
|
|
1321
|
+
|
|
1250
1322
|
## Pull Request Follow-ups
|
|
1251
1323
|
|
|
1252
1324
|
boxes.dev can send a managed Codex or Claude thread a message when its pull
|
|
@@ -2323,6 +2395,12 @@ it. Template boxes, teammates' devboxes, and devboxes in other projects return
|
|
|
2323
2395
|
`invalid_request`; see
|
|
2324
2396
|
[Destroy And Archive The Current Devbox](#destroy-and-archive-the-current-devbox).
|
|
2325
2397
|
|
|
2398
|
+
The project coordinator has its own **Destroy and archive devboxes** setting
|
|
2399
|
+
with the levels **Started by the coordinator** and **In this project**. It
|
|
2400
|
+
never follows the project setting, so its requests can be allowed only for the
|
|
2401
|
+
coordinator. It can't destroy its own box. Its instructions limit destruction
|
|
2402
|
+
to a direct request from the user in its chat.
|
|
2403
|
+
|
|
2326
2404
|
Run this only when the user's task calls for it, such as after the devbox's
|
|
2327
2405
|
work has merged or has otherwise been preserved outside the machine. If it's
|
|
2328
2406
|
unclear which devboxes the user means, ask before requesting destruction.
|
|
@@ -2452,6 +2530,13 @@ The Template box cannot move itself. Sibling, manually created, indirect, stale,
|
|
|
2452
2530
|
cross-project, and cross-owner devboxes fail without revealing whether another
|
|
2453
2531
|
target exists.
|
|
2454
2532
|
|
|
2533
|
+
The project coordinator can move any of the user's devboxes in its project
|
|
2534
|
+
except its own box. For the coordinator, `folders list` also returns each
|
|
2535
|
+
folder's `devboxes`, with `devboxId`, `title`, and `folderRevision`, including
|
|
2536
|
+
pinned devboxes; the field is null for other boxes. Unfiled devboxes aren't
|
|
2537
|
+
listed: find them with `threads list --scope project` and read each one's
|
|
2538
|
+
revision with `folders get`.
|
|
2539
|
+
|
|
2455
2540
|
`folder_revision_conflict` means another person or agent changed the membership.
|
|
2456
2541
|
Run `get` again and reconsider the operation; moves never overwrite a newer
|
|
2457
2542
|
revision. Keep one idempotency key per logical create or move, and retry an
|
|
@@ -44,7 +44,9 @@ When a new connection finishes either way, the app DMs the Slack user who
|
|
|
44
44
|
approved it with getting-started steps and links to the Slack help article and
|
|
45
45
|
support. A reinstall while the workspace is still connected, for example to add
|
|
46
46
|
permissions, sends no DM; a reinstall after an uninstall, a disconnect, or a
|
|
47
|
-
connection that needed a reinstall does.
|
|
47
|
+
connection that needed a reinstall does. Anyone else who opens the app's
|
|
48
|
+
**Messages** tab before the app has messaged them gets a short welcome with how
|
|
49
|
+
to link their Slack account (`connect`) and see what they can do (`help`).
|
|
48
50
|
|
|
49
51
|
After Slack redirects back, the Slack integration home continues through the
|
|
50
52
|
remaining setup steps: link your identity, create your automation, and activate
|
|
@@ -375,7 +375,10 @@ creation. Saving a setting does not save a new filesystem version and does not
|
|
|
375
375
|
wait for the current editing session to close. Unsaved changes remain only in
|
|
376
376
|
that focused editor; there is no configuration draft, filesystem save,
|
|
377
377
|
history, or rollback. Existing projects keep these copied settings; managed
|
|
378
|
-
MCP definitions follow the separate live rules above.
|
|
378
|
+
MCP definitions follow the separate live rules above. Agent guidance is not
|
|
379
|
+
copied into managed projects: each new devbox in a managed project gets the
|
|
380
|
+
template's current guidance, followed by the guidance the member saved in their
|
|
381
|
+
own project settings. Independent projects receive a copy. An
|
|
379
382
|
independent project with its own Template box receives every applicable
|
|
380
383
|
setting; managed projects receive the same settings except setup instructions
|
|
381
384
|
and maintenance.
|
|
@@ -477,6 +480,12 @@ an ordinary devbox thread. Thread forks, delegated threads, devbox creation,
|
|
|
477
480
|
and other project-only actions are unavailable. More than one thread can exist
|
|
478
481
|
and run against the current checkout.
|
|
479
482
|
|
|
483
|
+
Editor threads use the Codex and Claude settings, instructions, and skills in
|
|
484
|
+
the editing machine's home folder, except that a skill in `~/.claude/skills` or
|
|
485
|
+
`~/.codex/skills` larger than 200 MB or with more than 5,000 files, including
|
|
486
|
+
any files it links to, is left out so the editing machine can start quickly.
|
|
487
|
+
Projects created from the Team Template still include every skill.
|
|
488
|
+
|
|
480
489
|
The conversation and the checkout filesystem are separate. Saving or
|
|
481
490
|
discarding does not attempt to prove that the files still match what an agent
|
|
482
491
|
saw. Before the editing machine is destroyed, boxes.dev saves the native
|
|
@@ -862,9 +862,13 @@ Codex threads expose model controls in the composer footer:
|
|
|
862
862
|
On desktop or mobile, type `$` in a Codex reply box to choose from the skills
|
|
863
863
|
available to Codex on that machine. Each row shows where the skill comes from:
|
|
864
864
|
Project, Personal, Plugin, Account (a plugin installed through your ChatGPT
|
|
865
|
-
account or workspace), Admin, or Built-in.
|
|
866
|
-
|
|
867
|
-
|
|
865
|
+
account or workspace), Admin, or Built-in. On desktop, choosing a skill adds
|
|
866
|
+
an inline tag whose file path is available on hover. The message retains that
|
|
867
|
+
path, so Codex will load the selected skill even when another has the same
|
|
868
|
+
name. On mobile, choosing a skill adds `$name`, which needs to be unique on
|
|
869
|
+
the box for Codex to load the skill automatically. Skills the user
|
|
870
|
+
chooses most often are listed first (see the ordering note under **Claude
|
|
871
|
+
Controls**). Before the box connects, including in a new thread, the composer
|
|
868
872
|
shows the skills boxes.dev last read from a Codex thread in the same project,
|
|
869
873
|
so its list fills in once a started Codex thread in that project has been
|
|
870
874
|
opened; Account skills appear there only while the Codex account they came from
|
|
@@ -982,6 +986,14 @@ list leaves out `/model` and `/fast`, which the model menu covers. On desktop, `
|
|
|
982
986
|
`/model <model>` switches directly to a known model. Older supported model generations appear
|
|
983
987
|
under **More models** in the picker.
|
|
984
988
|
|
|
989
|
+
The Codex `$` and Claude `/` lists put the skills and commands the user has
|
|
990
|
+
chosen most often first, and recent choices count more than older ones, so a
|
|
991
|
+
skill that stops being used gradually moves back down. Typed text still decides
|
|
992
|
+
which entries match and puts names that start with it ahead of other matches;
|
|
993
|
+
usage orders the entries within those. Choices are saved with
|
|
994
|
+
the user's boxes.dev account, so the order is the same on desktop and mobile,
|
|
995
|
+
and a skill with the same name in Codex and Claude shares one count.
|
|
996
|
+
|
|
985
997
|
`/clear`, `/new`, and `/reset` are unavailable in a Claude thread. The command
|
|
986
998
|
list leaves them out, and desktop, mobile, the CLI, and other agents can't send
|
|
987
999
|
them. Start a new thread to clear Claude's context. A message is refused only
|
|
@@ -144,8 +144,13 @@ and what setup observed:
|
|
|
144
144
|
- SSH sign-in succeeded, but the repository couldn't be read. Check the
|
|
145
145
|
repository URL and that the key's account or deploy key can read it.
|
|
146
146
|
- A follow-up SSH connection to the host failed, with the cause, such as
|
|
147
|
-
connection refused, reset, timed out, or host name not found.
|
|
148
|
-
|
|
147
|
+
connection refused, reset, timed out, or host name not found. The Template box
|
|
148
|
+
runs in the cloud, so it can't reach a Git host that accepts connections only
|
|
149
|
+
from certain networks or IP addresses, or whose name resolves only inside a
|
|
150
|
+
company network. If the host can allowlist an IP address, a **Static egress
|
|
151
|
+
IP** may help: add the host with that port as a destination in **Settings →
|
|
152
|
+
Integrations**, and allowlist the static IP at the Git host. Static egress is
|
|
153
|
+
enabled on request; see [Team Settings](desktop-workbench.md#team-settings).
|
|
149
154
|
- Sign-in didn't complete, although a follow-up check reached the host's SSH
|
|
150
155
|
server. The key may not be registered with the host, or the host key may have
|
|
151
156
|
changed. For agent-driven setup, `dvb agent-init diagnostics` includes the
|
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.1116",
|
|
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",
|
|
@@ -57,7 +57,7 @@
|
|
|
57
57
|
"@clack/core": "^1.0.0",
|
|
58
58
|
"@clack/prompts": "^1.0.0",
|
|
59
59
|
"cli-truncate": "^6.1.1",
|
|
60
|
-
"convex": "^1.
|
|
60
|
+
"convex": "^1.48.0",
|
|
61
61
|
"file-type": "^22.0.1",
|
|
62
62
|
"ink": "^7.1.1",
|
|
63
63
|
"jsonc-parser": "^3.3.1",
|
|
@@ -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-07T02:07:01Z"
|
|
81
81
|
}
|