@boxes-dev/dvb-runtime 1.0.1100 → 1.0.1101

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.
@@ -401,7 +401,8 @@ runs first if you need to remove the automation.
401
401
 
402
402
  For non-Slack and non-Linear automations, you can add Slack output destinations
403
403
  if your team has a working Slack connection. Destinations can be Slack channels
404
- or linked-user DMs.
404
+ or linked-user DMs. A private channel needs your linked Slack account to be a
405
+ member of it when you save the destination.
405
406
 
406
407
  Each destination can receive selected events from the turn started by the
407
408
  automation run:
@@ -108,6 +108,13 @@ available.
108
108
  If a team member is not a team admin, billing controls usually show status and
109
109
  tell the member to contact a team admin.
110
110
 
111
+ New teams that sign up at boxes.dev/alien will receive three months of Pro
112
+ free. The account that creates the team will get the first Pro seat, including
113
+ 250 box-hours each month. Extra usage will require prepaid credits. No card is
114
+ required for the offer. Pro will end after three months unless a team admin
115
+ chooses **Keep plan** in Billing; continuing will use the normal Pro price.
116
+ The offer does not replace an existing account's or team's billing.
117
+
111
118
  ## Overage Credits
112
119
 
113
120
  Paid-plan overage uses prepaid usage credits. Team admins on an active Starter,
@@ -65,11 +65,15 @@ npm install -g @boxes-dev/cli
65
65
  or:
66
66
 
67
67
  ```bash
68
- curl -fsSL https://boxes.dev/install.sh | sh
68
+ curl -fsSL https://deploy.boxes.dev/cli/install.sh | sh
69
69
  ```
70
70
 
71
- With Node.js 22 or newer, `npm install -g @boxes-dev/dvb` installs a build
72
- that uses the local Node.js runtime instead.
71
+ With Node.js 22.19 or newer (24.5 or newer on Node.js 24),
72
+ `npm install -g @boxes-dev/dvb` installs a build that uses the local Node.js
73
+ runtime instead. On older Node.js versions, `dvb` exits with an error, because
74
+ those versions trust certificate authorities that were compromised in October
75
+ 2026. To switch to the build with its own Node.js, run
76
+ `npm uninstall -g @boxes-dev/dvb`, then `npm install -g @boxes-dev/cli`.
73
77
 
74
78
  ## Sign In And Agent Setup
75
79
 
@@ -53,6 +53,15 @@ permissions, known users, known channels, administrative activity, and
53
53
  technical details. The same team-level information remains available in Team
54
54
  Settings.
55
55
 
56
+ boxes.dev follows Slack's rule that a private channel's name and messages are
57
+ only for its members. A private channel's name appears only to people whose
58
+ linked Slack account is in that channel; everyone else sees **Private
59
+ channel**, and automation channel pickers leave it out. Someone without a
60
+ linked Slack account sees no private channel names. Slack email addresses
61
+ appear only to team admins, plus each person's own address. boxes.dev checks
62
+ channel membership with Slack each time it verifies the channel, such as when
63
+ the app is mentioned there or an admin chooses **Check**.
64
+
56
65
  Disconnecting Slack stops Slack triggers, automation posts, and agent access to
57
66
  Slack for the team. Data stored for the Slack connection is deleted within
58
67
  14 business days. Uninstalling the app from the Slack workspace, or revoking
@@ -185,6 +194,32 @@ when Claude uses a claude.ai login. Owners should allow only teammates they
185
194
  would trust with that access, including on named commands that allow
186
195
  teammates.
187
196
 
197
+ In a private channel, a teammate or an allowed bot can start work in the
198
+ owner's workspace only when the owner's linked Slack account is a member of
199
+ that channel, because the run would bring the channel's name and messages into
200
+ the owner's boxes.dev thread. Otherwise boxes.dev starts nothing. When started
201
+ messages are on, it replies to a teammate in the Slack thread naming the
202
+ owner: someone in the channel needs to add the owner, or the teammate can use
203
+ their own automation. Bots get no reply. The owner's own requests are
204
+ unaffected.
205
+
206
+ The same check applies to a Slack thread that is already linked to a run. If
207
+ its channel has become private without the owner, or the owner has left a
208
+ private channel, boxes.dev does not pass a teammate's or bot's follow-up on to
209
+ the owner's thread (when follow-up confirmations are on, a teammate gets a
210
+ reply explaining why), and the agent's Slack read tools refuse to read the
211
+ thread. Agent reads of a channel granted to agents check the channel with
212
+ Slack each time and refuse one that has become private.
213
+
214
+ A task from a private channel starts a private boxes.dev thread, whoever
215
+ requested it. Teammates cannot browse or read it under any **Thread access**
216
+ setting until the owner shares it, which clears the private setting. Privacy
217
+ is set when the run starts, from the channel as boxes.dev last checked it with
218
+ Slack: when the owner mentioned the app, for the owner's own request, or at
219
+ launch for a teammate's or bot's. A thread started while its channel was
220
+ public keeps the team's access if the channel later becomes private. Tasks
221
+ from public channels and DMs with the app follow the team's setting.
222
+
188
223
  boxes.dev starts each automation run on a fresh devbox from the latest
189
224
  Template box snapshot for an independent project, or the current saved Team
190
225
  Template version for a managed project. The agent sees the automation prompt
@@ -372,7 +407,10 @@ column. The **Internal** column controls replies in your own workspace.
372
407
 
373
408
  Manual, scheduled, and API automations can separately send selected events to
374
409
  Slack channels or linked-user DMs. Those output destinations can receive final
375
- output, needs-input, and failed-run events.
410
+ output, needs-input, and failed-run events. A private channel can be saved as
411
+ a destination only by an owner whose linked Slack account is in the channel.
412
+ boxes.dev checks this when the destination is saved, so a saved destination
413
+ keeps working if the owner later leaves the channel.
376
414
 
377
415
  ## Shared Thread Previews
378
416
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@boxes-dev/dvb-runtime",
3
- "version": "1.0.1100",
3
+ "version": "1.0.1101",
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-21T20:43:36Z"
80
+ "devboxReleasedAt": "2026-10-22T00:38:03Z"
81
81
  }