@boxes-dev/dvb-runtime 1.0.970 → 1.0.972
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 +6 -6
- package/dist/bin/dvbd.mjs +6 -6
- package/dist/product-docs/references/index.md +3 -0
- package/dist/product-docs/references/managed-environment-files.md +149 -0
- package/dist/product-docs/references/shared-storage.md +26 -22
- package/dist/product-docs/references/threads-and-agents.md +26 -0
- package/package.json +2 -2
package/dist/bin/dvb.mjs
CHANGED
|
@@ -101145,8 +101145,8 @@ var init_otel = __esm({
|
|
|
101145
101145
|
return trimmed && trimmed.length > 0 ? trimmed : void 0;
|
|
101146
101146
|
};
|
|
101147
101147
|
readBuildMetadata = () => {
|
|
101148
|
-
const rawPackageVersion = "1.0.
|
|
101149
|
-
const rawGitSha = "
|
|
101148
|
+
const rawPackageVersion = "1.0.972";
|
|
101149
|
+
const rawGitSha = "df088f5669889dbe4bceeb116f12934d988bed48";
|
|
101150
101150
|
const packageVersion = typeof rawPackageVersion === "string" ? rawPackageVersion : void 0;
|
|
101151
101151
|
const gitSha = typeof rawGitSha === "string" ? rawGitSha : void 0;
|
|
101152
101152
|
return { packageVersion, gitSha };
|
|
@@ -133552,9 +133552,9 @@ var init_sentry = __esm({
|
|
|
133552
133552
|
uncaughtExceptionMonitorInstalled = false;
|
|
133553
133553
|
currentDevboxSentryUser = null;
|
|
133554
133554
|
readBuildMetadata2 = () => {
|
|
133555
|
-
const rawPackageVersion = "1.0.
|
|
133556
|
-
const rawGitSha = "
|
|
133557
|
-
const rawSentryRelease = "boxes-dev-dvb@1.0.
|
|
133555
|
+
const rawPackageVersion = "1.0.972";
|
|
133556
|
+
const rawGitSha = "df088f5669889dbe4bceeb116f12934d988bed48";
|
|
133557
|
+
const rawSentryRelease = "boxes-dev-dvb@1.0.972+df088f5669889dbe4bceeb116f12934d988bed48";
|
|
133558
133558
|
const packageVersion = typeof rawPackageVersion === "string" ? rawPackageVersion : void 0;
|
|
133559
133559
|
const gitSha = typeof rawGitSha === "string" ? rawGitSha : void 0;
|
|
133560
133560
|
const sentryRelease = typeof rawSentryRelease === "string" ? rawSentryRelease : void 0;
|
|
@@ -138737,7 +138737,7 @@ var init_packageVersion = __esm({
|
|
|
138737
138737
|
return path17.join(process.cwd(), "dvb");
|
|
138738
138738
|
};
|
|
138739
138739
|
readEmbeddedPackageVersion = () => {
|
|
138740
|
-
const raw = "1.0.
|
|
138740
|
+
const raw = "1.0.972";
|
|
138741
138741
|
return trimVersion(raw);
|
|
138742
138742
|
};
|
|
138743
138743
|
readNearestPackageMetadata = (basePath) => {
|
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.
|
|
96332
|
-
const rawGitSha = "
|
|
96331
|
+
const rawPackageVersion = "1.0.972";
|
|
96332
|
+
const rawGitSha = "df088f5669889dbe4bceeb116f12934d988bed48";
|
|
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.
|
|
128628
|
-
const rawGitSha = "
|
|
128629
|
-
const rawSentryRelease = "boxes-dev-dvb@1.0.
|
|
128627
|
+
const rawPackageVersion = "1.0.972";
|
|
128628
|
+
const rawGitSha = "df088f5669889dbe4bceeb116f12934d988bed48";
|
|
128629
|
+
const rawSentryRelease = "boxes-dev-dvb@1.0.972+df088f5669889dbe4bceeb116f12934d988bed48";
|
|
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;
|
|
@@ -130818,7 +130818,7 @@ var init_packageVersion = __esm({
|
|
|
130818
130818
|
return path8.join(process.cwd(), "dvb");
|
|
130819
130819
|
};
|
|
130820
130820
|
readEmbeddedPackageVersion = () => {
|
|
130821
|
-
const raw = "1.0.
|
|
130821
|
+
const raw = "1.0.972";
|
|
130822
130822
|
return trimVersion(raw);
|
|
130823
130823
|
};
|
|
130824
130824
|
readNearestPackageMetadata = (basePath) => {
|
|
@@ -43,6 +43,9 @@ Use this terminology consistently:
|
|
|
43
43
|
copied-data boundaries.
|
|
44
44
|
- `template-box-environment.md`: the Template box machine environment, baseline
|
|
45
45
|
development tools, setup constraints, local-run verification, and snapshots.
|
|
46
|
+
- `managed-environment-files.md`: centrally managed dotenv files, initial
|
|
47
|
+
import, managed-prefix ownership, Team Template Team/member values,
|
|
48
|
+
reveal/export, outages, snapshots, security boundaries, and limits.
|
|
46
49
|
- `shared-storage.md`: the shared `/project` folder, recommended uses and
|
|
47
50
|
limitations, Claude project memory, persistence, access, and turning it off.
|
|
48
51
|
- `core-concepts.md`: short definitions for projects, Template boxes, devboxes,
|
|
@@ -0,0 +1,149 @@
|
|
|
1
|
+
# Managed Environment Files
|
|
2
|
+
|
|
3
|
+
Use this doc for questions about centrally managed `.env` files, project
|
|
4
|
+
values, Team Template value requirements, imports, reveal/export, or sync
|
|
5
|
+
behavior.
|
|
6
|
+
|
|
7
|
+
## What boxes.dev Manages
|
|
8
|
+
|
|
9
|
+
A project owner can register a project-relative dotenv file such as
|
|
10
|
+
`.env.local` in **Project settings → Environment files**. Each registered file
|
|
11
|
+
has its own list of names, values, optional inline comments, and descriptions.
|
|
12
|
+
The saved values are the source of truth: Template boxes and devboxes receive
|
|
13
|
+
updates, but changes made on a box never update the central copy.
|
|
14
|
+
|
|
15
|
+
boxes.dev writes a managed section at the start of the file and ends it with:
|
|
16
|
+
|
|
17
|
+
```dotenv
|
|
18
|
+
# >>> BOXES_MANAGED_ENV_v1 <<<
|
|
19
|
+
```
|
|
20
|
+
|
|
21
|
+
The section above and including that marker is replaced during sync. Everything
|
|
22
|
+
after it is local machine content and is preserved byte for byte. Do not edit
|
|
23
|
+
the managed section directly; use Project settings. A local value below the
|
|
24
|
+
marker may duplicate a managed name, but boxes.dev does not parse that tail or
|
|
25
|
+
treat duplicate names as a supported override mechanism.
|
|
26
|
+
|
|
27
|
+
New files are created with owner-only permissions. Existing regular files keep
|
|
28
|
+
their current owner, group, mode, and content below the marker. Unsafe paths,
|
|
29
|
+
symbolic-link traversal, and non-file destinations are refused.
|
|
30
|
+
|
|
31
|
+
## Adding An Existing File
|
|
32
|
+
|
|
33
|
+
When a project owner first registers a path, boxes.dev checks that path on the
|
|
34
|
+
project's Template box. If an ordinary dotenv file exists, the editor recognizes
|
|
35
|
+
conservative single-line assignments and lets the owner choose for each one:
|
|
36
|
+
|
|
37
|
+
- **Manage**: save the value centrally and move the assignment into the managed
|
|
38
|
+
section;
|
|
39
|
+
- **Keep local**: leave the assignment in the file's local tail; or
|
|
40
|
+
- **Remove**: remove that recognized assignment when management starts.
|
|
41
|
+
|
|
42
|
+
Comments, blank lines, shell expressions, multiline constructs, and anything
|
|
43
|
+
else the importer does not recognize stay local. The file must still match the
|
|
44
|
+
version that was reviewed when the import is applied. If it changed, boxes.dev
|
|
45
|
+
leaves it alone and asks the owner to review it again. Import is a one-time
|
|
46
|
+
setup step; boxes.dev never imports later edits from an already managed file.
|
|
47
|
+
|
|
48
|
+
If the file does not exist, boxes.dev creates it. If it is too large or is not
|
|
49
|
+
valid UTF-8, automatic import is skipped and the complete existing file is
|
|
50
|
+
preserved below the new managed section.
|
|
51
|
+
|
|
52
|
+
When a team admin adds a file to a Team Template, boxes.dev checks the retained
|
|
53
|
+
source box for the latest saved release. Before the first release, it checks
|
|
54
|
+
that admin's current Team Template editing session. The admin must explicitly
|
|
55
|
+
classify every imported assignment as a Team value, a Member value, local
|
|
56
|
+
content, or removed content before saving.
|
|
57
|
+
|
|
58
|
+
Each derived or team-managed project applies that import decision once. If its
|
|
59
|
+
file still matches the reviewed source, boxes.dev moves or removes the selected
|
|
60
|
+
assignments. If the file has changed, boxes.dev adds the managed section but
|
|
61
|
+
preserves the complete existing file below it. This may leave a duplicate name
|
|
62
|
+
for the project owner to resolve, but does not discard local content.
|
|
63
|
+
|
|
64
|
+
## Team Template Values
|
|
65
|
+
|
|
66
|
+
A team admin can add environment-file defaults to a Team Template. Each row is
|
|
67
|
+
either:
|
|
68
|
+
|
|
69
|
+
- **Team**: the admin supplies the shared value; or
|
|
70
|
+
- **Member**: each member supplies their own value during project creation.
|
|
71
|
+
|
|
72
|
+
A Member row can be required or optional and can include a description and
|
|
73
|
+
instructions for obtaining the value. Required values block creation of that
|
|
74
|
+
new project until they are entered; they do not block unrelated existing
|
|
75
|
+
devboxes or agent startup. Optional or otherwise missing values are omitted
|
|
76
|
+
from the file.
|
|
77
|
+
|
|
78
|
+
A normal project created from a Team Template receives an independent copy of
|
|
79
|
+
the definitions and the Team/member values entered for that project. Later Team
|
|
80
|
+
Template changes do not update it, and another project created from the same
|
|
81
|
+
template does not share its value objects.
|
|
82
|
+
|
|
83
|
+
A Team Template-managed project follows the current Team Template definitions
|
|
84
|
+
and Team values. Each member's values belong only to that member's exact
|
|
85
|
+
project. Members can replace, remove, reveal, copy, or export their own project
|
|
86
|
+
values, but cannot add centrally managed files or rows in this first version.
|
|
87
|
+
Team admins cannot read member values.
|
|
88
|
+
|
|
89
|
+
If an admin changes where a Member value will be written by renaming it or
|
|
90
|
+
moving its file, boxes.dev omits the old saved value. The member must review the
|
|
91
|
+
new destination and choose **Use saved value here**, or enter a replacement.
|
|
92
|
+
Other managed values continue syncing while that one is unresolved.
|
|
93
|
+
|
|
94
|
+
## Sync And Outages
|
|
95
|
+
|
|
96
|
+
Managed files reconcile when a Template box or devbox starts or wakes, when a
|
|
97
|
+
change is observed, and during periodic retry. Changing a value does not wake a
|
|
98
|
+
paused machine. A failure in one file does not stop other files from updating.
|
|
99
|
+
|
|
100
|
+
If boxes.dev, its key service, or the network is temporarily unavailable, an
|
|
101
|
+
existing file remains unchanged and the machine continues starting. The daemon
|
|
102
|
+
retries later. A newly restored machine may therefore use the copy already in
|
|
103
|
+
its snapshot until sync succeeds.
|
|
104
|
+
|
|
105
|
+
## Viewing And Recovering Current Values
|
|
106
|
+
|
|
107
|
+
Values are masked in normal project settings. Revealing values, showing a
|
|
108
|
+
value-bearing file preview, copying the managed file, or exporting it requires
|
|
109
|
+
a fresh confirmation with the Google account linked to the current boxes.dev
|
|
110
|
+
account. That confirmation applies only to the current signed-in session and
|
|
111
|
+
lasts five minutes. Closing the editor, navigating away, switching accounts,
|
|
112
|
+
signing out, or reaching the expiry removes the revealed plaintext from the
|
|
113
|
+
UI.
|
|
114
|
+
|
|
115
|
+
A Team Template admin can use the same confirmation to reveal or export the
|
|
116
|
+
Team values saved on that template. Member values are project-local and are
|
|
117
|
+
never revealed to the Team Template admin. A member can confirm with their own
|
|
118
|
+
Google account to reveal, copy, or export the current managed file for their
|
|
119
|
+
own Team Template-managed project.
|
|
120
|
+
|
|
121
|
+
boxes.dev keeps only the current central value. There is no per-value version
|
|
122
|
+
history, rollback, or recovery window. Replace or delete carefully, and rotate
|
|
123
|
+
credentials through their issuing service when necessary.
|
|
124
|
+
|
|
125
|
+
## Security Boundaries
|
|
126
|
+
|
|
127
|
+
Central values are encrypted before they are stored, using a separate key scope
|
|
128
|
+
for each project or other value owner. The central database stores ciphertext,
|
|
129
|
+
not plaintext values or usable root encryption keys. Authorized boxes.dev
|
|
130
|
+
services can still decrypt current values when they must deliver, reveal, copy,
|
|
131
|
+
or export them; this is not end-to-end or zero-knowledge encryption.
|
|
132
|
+
|
|
133
|
+
Delivered files contain plaintext. A project owner, root user, process, or
|
|
134
|
+
coding agent on that machine can read them. Use development, staging, sandbox,
|
|
135
|
+
or narrowly scoped credentials rather than broad production credentials.
|
|
136
|
+
|
|
137
|
+
Snapshots preserve their filesystem, including managed environment files.
|
|
138
|
+
Replacing or deleting a central value does not erase an older value from an
|
|
139
|
+
existing snapshot, backup, running process, or already delivered machine.
|
|
140
|
+
Rotate or revoke the credential at its provider when that distinction matters.
|
|
141
|
+
|
|
142
|
+
## Limits
|
|
143
|
+
|
|
144
|
+
The protective limits are:
|
|
145
|
+
|
|
146
|
+
- 64 KiB per value;
|
|
147
|
+
- 500 managed rows per file;
|
|
148
|
+
- 1 MiB for the rendered managed section; and
|
|
149
|
+
- 2 MiB for automatic import of an existing file.
|
|
@@ -1,9 +1,13 @@
|
|
|
1
1
|
# Shared Project Storage
|
|
2
2
|
|
|
3
|
-
Project storage gives a project one persistent folder shared by its
|
|
4
|
-
It is on by default during open beta and appears at
|
|
5
|
-
|
|
6
|
-
|
|
3
|
+
Project storage gives a project one persistent folder shared by its Template
|
|
4
|
+
box and devboxes. It is on by default during open beta and appears at
|
|
5
|
+
`/project` on each machine.
|
|
6
|
+
|
|
7
|
+
You can snapshot the Template box while `/project` is mounted. The snapshot
|
|
8
|
+
does not copy or replace the stored contents. When boxes.dev creates a devbox
|
|
9
|
+
from that snapshot, it reconnects `/project` for that devbox before the devbox
|
|
10
|
+
is ready.
|
|
7
11
|
|
|
8
12
|
Use project storage for information that should follow work across devboxes,
|
|
9
13
|
such as agent memory, reference files, handoff files, stable project data, and
|
|
@@ -14,14 +18,13 @@ package caches, logs, queues, build trees, or other high-churn workloads.
|
|
|
14
18
|
## Claude project memory
|
|
15
19
|
|
|
16
20
|
When `/project` is mounted normally, boxes.dev directs Claude's automatic
|
|
17
|
-
memory to the shared project storage. A memory Claude writes
|
|
18
|
-
therefore inform Claude
|
|
21
|
+
memory to the shared project storage. A memory Claude writes on the Template
|
|
22
|
+
box or a devbox can therefore inform Claude on the project's other machines.
|
|
19
23
|
|
|
20
24
|
Before broad launch, boxes.dev migrated eligible Claude auto memory from each
|
|
21
25
|
existing project's Template box into `/project/.claude/memory`. It did not
|
|
22
|
-
combine memory that existed only on other devboxes. The Template box
|
|
23
|
-
|
|
24
|
-
`/project`.
|
|
26
|
+
combine memory that existed only on other devboxes. The Template box and
|
|
27
|
+
devboxes now use the shared memory while `/project` is mounted.
|
|
25
28
|
|
|
26
29
|
Claude's own settings still take precedence. `autoMemoryEnabled: false` keeps
|
|
27
30
|
automatic memory off, and an explicitly supplied memory directory remains in
|
|
@@ -32,24 +35,25 @@ boxes.dev does not redirect Codex state or transcripts there.
|
|
|
32
35
|
|
|
33
36
|
## Concurrent access and durability
|
|
34
37
|
|
|
35
|
-
|
|
36
|
-
second to become visible elsewhere, and truly simultaneous
|
|
37
|
-
file can fail or conflict. Avoid workflows that depend on
|
|
38
|
-
strict cache coherence, atomic appends from several
|
|
39
|
-
many processes rewriting the same files.
|
|
38
|
+
The Template box and multiple devboxes can read and write the folder. Updates
|
|
39
|
+
can take about a second to become visible elsewhere, and truly simultaneous
|
|
40
|
+
writes to the same file can fail or conflict. Avoid workflows that depend on
|
|
41
|
+
local-disk latency, strict cache coherence, atomic appends from several
|
|
42
|
+
writers, file locking, or many processes rewriting the same files.
|
|
40
43
|
|
|
41
|
-
Project storage survives
|
|
42
|
-
Deleting the boxes.dev project deletes its
|
|
43
|
-
keep another copy of anything you cannot
|
|
44
|
+
Project storage survives machine sleep and reset, as well as devbox
|
|
45
|
+
destruction and replacement. Deleting the boxes.dev project deletes its
|
|
46
|
+
project storage. During open beta, keep another copy of anything you cannot
|
|
47
|
+
recreate.
|
|
44
48
|
|
|
45
49
|
## Turning project storage off
|
|
46
50
|
|
|
47
51
|
Open **Project settings** for the project and use **Project storage** to turn
|
|
48
52
|
the mount off or back on. Turning it off detaches `/project` from the project's
|
|
49
|
-
devboxes and removes their access, but it does not delete
|
|
50
|
-
Re-enabling it mounts the same storage again.
|
|
53
|
+
Template box and devboxes and removes their access, but it does not delete
|
|
54
|
+
stored files. Re-enabling it mounts the same storage again.
|
|
51
55
|
|
|
52
56
|
Machine access and thread sharing are separate. Anyone who is authorized to
|
|
53
|
-
operate a
|
|
54
|
-
Sharing an agent thread by itself does not grant
|
|
55
|
-
permission, or access to project storage.
|
|
57
|
+
operate a project machine can naturally access the files mounted inside that
|
|
58
|
+
machine. Sharing an agent thread by itself does not grant machine access,
|
|
59
|
+
project-setting permission, or access to project storage.
|
|
@@ -115,6 +115,32 @@ directory before the first prompt is sent. The options are the project
|
|
|
115
115
|
directory and the tracked repo directories in that project. Existing threads
|
|
116
116
|
continue in the working directory they were originally started with.
|
|
117
117
|
|
|
118
|
+
## Recorded Agent Activity
|
|
119
|
+
|
|
120
|
+
boxes.dev records compact hourly token measurements from retained Codex and
|
|
121
|
+
Claude transcripts. These measurements describe activity visible in the
|
|
122
|
+
transcripts; they are separate from the provider's rate-limit windows and may
|
|
123
|
+
not match how the provider calculates quota use.
|
|
124
|
+
|
|
125
|
+
The prepared dialog is scoped to the thread that opens it. It shows that
|
|
126
|
+
thread's share of recorded tokens, model-call count, average and largest input
|
|
127
|
+
context, and the balance of new input, cached input, and generated output. Its
|
|
128
|
+
chart compares that thread with one aggregate `Other activity` series; it does
|
|
129
|
+
not name or link to other threads.
|
|
130
|
+
|
|
131
|
+
Activity includes the currently selected saved account when the running agent
|
|
132
|
+
can prove that account binding, plus earlier or transitional activity whose
|
|
133
|
+
thread is known but whose account cannot be matched safely. The dialog discloses
|
|
134
|
+
that uncertain account amount without assigning it to the selected account. A
|
|
135
|
+
known extraction gap is partial history, not zero usage.
|
|
136
|
+
|
|
137
|
+
The prepared usage-details dialog reads a 24-hour or seven-day point-in-time
|
|
138
|
+
snapshot and shows when it was recorded. The 24-hour chart is hourly; the
|
|
139
|
+
seven-day chart can show one-hour or one-day bars. Refreshing requests a new
|
|
140
|
+
snapshot; it does not subscribe to transcript changes. The dialog's production
|
|
141
|
+
entrypoint remains unavailable until the bounded seven-day history backfill and
|
|
142
|
+
release checks are complete.
|
|
143
|
+
|
|
118
144
|
## Continuing In A New Chat
|
|
119
145
|
|
|
120
146
|
On a completed Codex or Claude response, choose **Continue in new chat** and
|
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.972",
|
|
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-
|
|
80
|
+
"devboxReleasedAt": "2026-09-01T05:07:08Z"
|
|
81
81
|
}
|