@boxes-dev/dvb-runtime 1.0.975 → 1.0.977

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]="0c520c63-d7c8-5393-a9f1-15c69313dfbe")}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]="4e9f337b-4b95-51a0-96ad-d98a48ad93c5")}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";
@@ -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.975";
101149
- const rawGitSha = "f69bcc38da18d03feb293f5a12949f2c274b1ffa";
101148
+ const rawPackageVersion = "1.0.977";
101149
+ const rawGitSha = "317f983b87d121f5786386cc1ad4966e2d82630e";
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.975";
133556
- const rawGitSha = "f69bcc38da18d03feb293f5a12949f2c274b1ffa";
133557
- const rawSentryRelease = "boxes-dev-dvb@1.0.975+f69bcc38da18d03feb293f5a12949f2c274b1ffa";
133555
+ const rawPackageVersion = "1.0.977";
133556
+ const rawGitSha = "317f983b87d121f5786386cc1ad4966e2d82630e";
133557
+ const rawSentryRelease = "boxes-dev-dvb@1.0.977+317f983b87d121f5786386cc1ad4966e2d82630e";
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.975";
138740
+ const raw = "1.0.977";
138741
138741
  return trimVersion(raw);
138742
138742
  };
138743
138743
  readNearestPackageMetadata = (basePath) => {
@@ -358886,4 +358886,4 @@ react/cjs/react-jsx-runtime.development.js:
358886
358886
  *)
358887
358887
  */
358888
358888
 
358889
- //# debugId=0c520c63-d7c8-5393-a9f1-15c69313dfbe
358889
+ //# debugId=4e9f337b-4b95-51a0-96ad-d98a48ad93c5
package/dist/bin/dvbd.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]="0d0e785c-1415-558b-b714-3e0c681d9449")}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]="3aca243b-b652-5346-916a-65220deabcd7")}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";
@@ -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.975";
96332
- const rawGitSha = "f69bcc38da18d03feb293f5a12949f2c274b1ffa";
96331
+ const rawPackageVersion = "1.0.977";
96332
+ const rawGitSha = "317f983b87d121f5786386cc1ad4966e2d82630e";
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.975";
128628
- const rawGitSha = "f69bcc38da18d03feb293f5a12949f2c274b1ffa";
128629
- const rawSentryRelease = "boxes-dev-dvb@1.0.975+f69bcc38da18d03feb293f5a12949f2c274b1ffa";
128627
+ const rawPackageVersion = "1.0.977";
128628
+ const rawGitSha = "317f983b87d121f5786386cc1ad4966e2d82630e";
128629
+ const rawSentryRelease = "boxes-dev-dvb@1.0.977+317f983b87d121f5786386cc1ad4966e2d82630e";
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.975";
130821
+ const raw = "1.0.977";
130822
130822
  return trimVersion(raw);
130823
130823
  };
130824
130824
  readNearestPackageMetadata = (basePath) => {
@@ -144013,4 +144013,4 @@ long/umd/index.js:
144013
144013
  *)
144014
144014
  */
144015
144015
 
144016
- //# debugId=0d0e785c-1415-558b-b714-3e0c681d9449
144016
+ //# debugId=3aca243b-b652-5346-916a-65220deabcd7
@@ -6,8 +6,10 @@ behavior.
6
6
 
7
7
  ## What boxes.dev Manages
8
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
9
+ A project owner can register a project-relative dotenv file in **Project
10
+ settings → Environment files**. Accepted names are `.env`, `.env.*` and
11
+ `*.env` patterns such as `.env.local` or `config.env`, `.dev.vars`, and
12
+ `.flaskenv`. Each registered file
11
13
  has its own list of names, values, optional inline comments, and descriptions.
12
14
  The saved values are the source of truth: Template boxes and devboxes receive
13
15
  updates, but changes made on a box never update the central copy.
@@ -28,11 +30,46 @@ New files are created with owner-only permissions. Existing regular files keep
28
30
  their current owner, group, mode, and content below the marker. Unsafe paths,
29
31
  symbolic-link traversal, and non-file destinations are refused.
30
32
 
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:
33
+ ## Adding A File
34
+
35
+ **Add a file** starts by listing the dotenv files that already exist on the
36
+ source boxes.dev reads: the project's Template box, or for a Team Template its
37
+ latest saved version or the admin's current editing session. Check the files to
38
+ register and choose **Add file**, or **Add 3 files** for several at once, so the
39
+ ordinary case needs no typing. **Rescan** repeats the search. Files that are
40
+ already managed stay visible but cannot be added twice, and a very long list may
41
+ be shortened, in which case the editor says so.
42
+
43
+ Several files are reviewed one at a time rather than in bulk, because each file
44
+ gets its own set of choices about which values boxes.dev should manage. The
45
+ editor shows which file is in front of you, such as `Reviewing 2 of 3`, and each
46
+ file is saved as you finish it. A file that fails can be retried or skipped, and
47
+ the rest of the batch carries on; files already saved stay managed even if you
48
+ stop partway, and the editor says so before you do. On a Team Template, adding
49
+ several files reads the source once for the whole batch rather than once per
50
+ file.
51
+
52
+ Choose **New file…** to name a file that does not exist yet. The form is a
53
+ folder and a file name: the folder offers the folders already on the source and
54
+ also accepts one you type, and the line beneath echoes the full location the
55
+ file will have. Naming the folder separately matters because the two surfaces
56
+ resolve paths differently - an ordinary project against its project folder, a
57
+ Team Template against the machine's home directory with each of its repositories
58
+ as a child folder. A file name containing a slash, or a name the dotenv naming
59
+ rule does not accept, is reported straight away, before boxes.dev checks
60
+ anything.
61
+
62
+ If a checked path does not exist but a file with the same name was found in
63
+ another folder, the editor offers that file, so a mistyped folder takes one
64
+ click to correct. The offer is only a suggestion; keeping the path as entered
65
+ is a normal choice.
66
+
67
+ A Template box that has not finished updating shows only a single path box,
68
+ without the list of existing files or the folder chooser.
69
+
70
+ boxes.dev then checks the chosen path. If an ordinary dotenv file exists there,
71
+ the editor recognizes conservative single-line assignments and lets the owner
72
+ choose for each one:
36
73
 
37
74
  - **Manage**: save the value centrally and move the assignment into the managed
38
75
  section;
@@ -51,9 +88,10 @@ preserved below the new managed section.
51
88
 
52
89
  When a team admin adds a file to a Team Template, boxes.dev checks the retained
53
90
  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.
91
+ that admin's current Team Template editing session, and the editor says which of
92
+ the two it is reading. The admin must explicitly classify every imported
93
+ assignment as a Team value, a Member value, local content, or removed content
94
+ before saving.
57
95
 
58
96
  Each derived or team-managed project applies that import decision once. If its
59
97
  file still matches the reviewed source, boxes.dev moves or removes the selected
@@ -104,7 +142,10 @@ its snapshot until sync succeeds.
104
142
 
105
143
  ## Viewing And Recovering Current Values
106
144
 
107
- Values are masked in normal project settings. Revealing values, showing a
145
+ Saved values are masked in normal project settings. Values that have not been
146
+ saved yet stay readable, both in an import review and while someone types a new
147
+ value, so whoever decides what to manage can see what each value is. **Hide
148
+ values** covers them during a screen share. Revealing a saved value, showing a
108
149
  value-bearing file preview, copying the managed file, or exporting it requires
109
150
  a fresh confirmation with the Google account linked to the current boxes.dev
110
151
  account. That confirmation applies only to the current signed-in session and
@@ -1,8 +1,8 @@
1
1
  # Slack Integration
2
2
 
3
3
  The Slack integration lets you mention `@boxes.dev` to start an automation on a
4
- fresh devbox, send follow-ups to the linked agent thread, and receive final
5
- replies back in Slack.
4
+ fresh devbox, start a thread in an opted-in teammate's workspace, send
5
+ follow-ups to the linked agent thread, and receive final replies back in Slack.
6
6
 
7
7
  Use `automations.md` for general automation behavior. This doc covers the Slack
8
8
  parts.
@@ -68,6 +68,14 @@ Your default Slack receiver runs when you mention `@boxes.dev` without a named
68
68
  command. Each mention starts an agent thread on a fresh devbox and appears in
69
69
  the main thread list alongside other devbox threads.
70
70
 
71
+ To start your own thread, mention `@boxes.dev` and write your request. Under
72
+ **Who else can trigger a new thread?**, choose **No one** (the default),
73
+ **Teammates I choose**, or **Any teammate with Slack connected**. This setting
74
+ belongs to you: teammates cannot give themselves access. Anyone you allow must
75
+ be an active member of the same boxes.dev team with a linked identity in the
76
+ connected Slack workspace. They can start a thread in your workspace by
77
+ mentioning `@boxes.dev @YourName`, followed by their request.
78
+
71
79
  ## Create A Slack Named Command Automation
72
80
 
73
81
  In the desktop workbench, create an automation and choose **Slack** as the
@@ -90,7 +98,7 @@ When you choose **Only selected channels**, the editor shows the channel
90
98
  picker below the menu.
91
99
 
92
100
  For named commands, choose who can run it. The owner can always run it; you can
93
- also allow linked team members.
101
+ also allow chosen teammates or any teammate with Slack connected.
94
102
 
95
103
  ## Running From Slack
96
104
 
@@ -106,6 +114,18 @@ For a named command:
106
114
  @boxes.dev !bugfix investigate the auth error above and suggest a fix
107
115
  ```
108
116
 
117
+ To start a thread in a teammate's workspace:
118
+
119
+ ```text
120
+ @boxes.dev @Ananya investigate the failed deploy above
121
+ ```
122
+
123
+ The teammate mention must immediately follow `@boxes.dev`, and a request must
124
+ follow the teammate mention. The teammate must have allowed you through their
125
+ default Slack receiver's access setting. The new agent thread belongs to that
126
+ teammate and uses their automation, Template box, devbox, credentials, and
127
+ usage. It does not copy either teammate's existing devbox filesystem.
128
+
109
129
  boxes.dev starts each automation run on a fresh devbox from the latest
110
130
  Template box snapshot. The agent sees the automation prompt plus Slack context,
111
131
  including the triggering message and available Slack thread messages. If Slack
@@ -117,9 +137,11 @@ time, subject to awake devbox capacity. If Slack retries the same event,
117
137
  boxes.dev reuses the already linked automation run instead of starting a
118
138
  duplicate.
119
139
 
120
- Slack receives a started reply with a link to the boxes.dev thread. If final
121
- Slack replies are enabled, boxes.dev posts the agent's final answer back into
122
- the same Slack thread or DM.
140
+ Slack receives a started reply with a link to the boxes.dev thread. When a
141
+ teammate starts a thread in your workspace, the reply names you and boxes.dev
142
+ sends you a direct message with links to the source Slack message and new
143
+ boxes.dev thread. If final Slack replies are enabled, boxes.dev posts the
144
+ agent's final answer back into the same Slack thread or DM.
123
145
 
124
146
  ## Follow-Ups And Controls
125
147
 
@@ -127,6 +149,10 @@ After a Slack request starts a boxes.dev thread, mention `@boxes.dev` again in
127
149
  the same Slack thread to send a follow-up. Ordinary Slack replies without the
128
150
  mention stay in Slack and are not sent to the agent.
129
151
 
152
+ To start a new teammate-owned run from an already linked Slack thread,
153
+ explicitly name the teammate again: `@boxes.dev @Ananya <request>`. Later
154
+ unqualified follow-ups in that Slack thread go to the newest run.
155
+
130
156
  Use Slack controls in the linked thread:
131
157
 
132
158
  - `@boxes.dev !help` shows available commands when help is needed.
@@ -163,6 +189,10 @@ omission in Slack, and tells the agent which intended input was not delivered.
163
189
  If the work depends on an omitted file, attach it manually in the boxes.dev
164
190
  thread.
165
191
 
192
+ Slack file import transfers only the eligible Slack attachments included with
193
+ the request or its thread context. Starting a thread in a teammate's workspace
194
+ never transfers files from an existing teammate devbox.
195
+
166
196
  Change the setting in the automation's own editor. For the default
167
197
  `@boxes.dev` mention, open **Configure** on the **Default behavior** card on the
168
198
  Slack integration home to reach that editor.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@boxes-dev/dvb-runtime",
3
- "version": "1.0.975",
3
+ "version": "1.0.977",
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-02T23:15:49Z"
80
+ "devboxReleasedAt": "2026-09-03T01:40:50Z"
81
81
  }