@boxes-dev/dvb-runtime 1.0.1050 → 1.0.1051

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]="24d3240a-70f6-599c-abcc-85e678461e94")}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]="7b8078e5-c984-5e42-8f1e-d9d4348ee2f4")}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";
@@ -69474,9 +69474,9 @@ var init_sentry = __esm({
69474
69474
  uncaughtExceptionMonitorInstalled = false;
69475
69475
  currentDevboxSentryUser = null;
69476
69476
  readBuildMetadata = () => {
69477
- const rawPackageVersion = "1.0.1050";
69478
- const rawGitSha = "ef46dfbfec3389cfd62ac373db540193c0c4cd0d";
69479
- const rawSentryRelease = "boxes-dev-dvb@1.0.1050+ef46dfbfec3389cfd62ac373db540193c0c4cd0d";
69477
+ const rawPackageVersion = "1.0.1051";
69478
+ const rawGitSha = "a146f896d6bb73d0ee0446cd7d2f7fbf92250dd8";
69479
+ const rawSentryRelease = "boxes-dev-dvb@1.0.1051+a146f896d6bb73d0ee0446cd7d2f7fbf92250dd8";
69480
69480
  const packageVersion = typeof rawPackageVersion === "string" ? rawPackageVersion : void 0;
69481
69481
  const gitSha = typeof rawGitSha === "string" ? rawGitSha : void 0;
69482
69482
  const sentryRelease = typeof rawSentryRelease === "string" ? rawSentryRelease : void 0;
@@ -73702,11 +73702,104 @@ var init_desktopInitAssets = __esm({
73702
73702
  }
73703
73703
  });
73704
73704
 
73705
+ // ../../../../shared/devboxCore/dist/setupFinalResponsePrompt.js
73706
+ var renderSetupFinalResponsePrompt;
73707
+ var init_setupFinalResponsePrompt = __esm({
73708
+ "../../../../shared/devboxCore/dist/setupFinalResponsePrompt.js"() {
73709
+ "use strict";
73710
+ renderSetupFinalResponsePrompt = (snapshotMode) => {
73711
+ const snapshotGuidance = snapshotMode === "automatic" ? "Explain that boxes.dev will finish setup by saving a snapshot of this machine's filesystem and memory as the starting point for future devboxes." : "Explain that a snapshot saves the machine's filesystem and memory, then report the result of the requested snapshot command. Say the snapshot was saved only if the command succeeded. If it failed or is still pending, explain that and the next step; do not claim future devboxes already include this setup.";
73712
+ const snapshotExample = snapshotMode === "automatic" ? "boxes.dev will finish setup by saving a snapshot of this machine's filesystem and memory. That snapshot will be the starting point for your tasks." : "<If the snapshot command succeeded: I saved a snapshot of this machine's filesystem and memory. That snapshot will be the starting point for your tasks. Otherwise, explain the snapshot status and next step.>";
73713
+ return `Final user-facing response:
73714
+
73715
+ The user is new to boxes.dev. This setup request is automated, but later
73716
+ messages in this thread will be from the user directly.
73717
+
73718
+ Your final response must introduce using boxes.dev directly. Include all of
73719
+ the following:
73720
+
73721
+ - Welcome the user to boxes.dev and explain that this Template box is a cloud
73722
+ machine containing their project's development environment.
73723
+ - Briefly explain what you set up, what you validated, and anything that still
73724
+ needs attention. Do not claim the app is fully runnable unless you verified
73725
+ it. Offer to help finish any remaining setup or run the app with
73726
+ port forwarding when relevant.
73727
+ - ${snapshotGuidance}
73728
+ - Make **New devbox + thread** the main next action. Explain that it will
73729
+ create an isolated machine from the Template box snapshot for the task,
73730
+ allowing several tasks to run in parallel with their own files and environments.
73731
+ - Explain that **New thread** on an existing devbox will start another agent
73732
+ conversation sharing that devbox's files and running environment.
73733
+ - Explain Slack mentions and Linear issue delegation: after configuring and
73734
+ activating their default behavior under **Integrations**, each can start an
73735
+ agent on a new devbox and deliver replies back to Slack or Linear. Do not
73736
+ imply either integration is already connected or active unless you know it is.
73737
+ - Explain that **Automations** can run a saved prompt on a schedule or through
73738
+ an API, with a new devbox for each run. Give one simple example.
73739
+ - Explain that **Create devboxes and threads** and **Message other agents**
73740
+ under **Agent permissions** let agents start other agent threads and exchange
73741
+ updates and results. Explicitly name both choices for delegated threads: on
73742
+ the same devbox, or on a new devbox. These permissions are
73743
+ off by default; messaging must be enabled on both participating boxes. The
73744
+ project defaults live under **Project settings \u2192 Agent permissions for this
73745
+ project**. Describe these choices without enabling them or creating work.
73746
+ - Explain that the user can keep talking here for setup help, and that saving a
73747
+ new snapshot after Template box environment changes will update the starting
73748
+ point for future devboxes.
73749
+
73750
+ Keep it friendly, casual, and concise: aim for about 300\u2013400 words, with a short
73751
+ setup result, a prominent first action, and brief bullets for the other ways to
73752
+ work. Adapt the example to the actual outcome. Use the boxes-product-docs skill
73753
+ when you need more product detail.
73754
+
73755
+ Example:
73756
+
73757
+ \`\`\`text
73758
+ Welcome to boxes.dev! We're in the cloud: this is your **Template box**, a cloud
73759
+ machine with your project's development environment.
73760
+
73761
+ <Briefly describe what was installed, what was validated, and anything that
73762
+ still needs attention.>
73763
+
73764
+ ${snapshotExample}
73765
+
73766
+ **Start your first task:** click **New devbox + thread** and ask the agent to
73767
+ build or fix something. It will get its own machine\u2014a **devbox**\u2014created from
73768
+ your Template box snapshot. You can work on several tasks in parallel, each
73769
+ with its own files and environment.
73770
+
73771
+ A few other ways to work:
73772
+
73773
+ - **Another thread on the same devbox:** choose **New thread** on an existing
73774
+ devbox for another agent conversation sharing its files and environment.
73775
+ - **Slack:** set up and activate Slack under **Integrations**, then mention
73776
+ \`@boxes.dev\` with a task. It will start an agent on a new devbox, and you
73777
+ can follow up and receive its replies in Slack.
73778
+ - **Linear:** set up and activate Linear under **Integrations**, then delegate
73779
+ an issue to boxes.dev. The agent will work on its own devbox and report
73780
+ progress and results in Linear.
73781
+ - **Automations:** save a prompt to run on a schedule or trigger through an
73782
+ API\u2014for example, a daily test run. Each run will get a new devbox.
73783
+ - **Agents working together:** enable **Create devboxes and threads** and
73784
+ **Message other agents** under **Agent permissions** to let agents delegate
73785
+ work on the same devbox or new ones and exchange updates and results. Both
73786
+ are off by default; enable messaging on the boxes involved. You can set
73787
+ project defaults in **Project settings \u2192 Agent permissions for this project**.
73788
+
73789
+ Keep talking to me here for help with setup, running your app, or using
73790
+ boxes.dev. When you update the Template box's environment, save a new snapshot
73791
+ so future devboxes will inherit those changes.
73792
+ \`\`\``;
73793
+ };
73794
+ }
73795
+ });
73796
+
73705
73797
  // ../../../../shared/devboxCore/dist/remoteSetupPrompt.js
73706
73798
  var REMOTE_SETUP_APPLY_E2B_TEMPLATE, renderTemplate, joinPosixPath, buildRemoteSetupEntrypointsBlock, buildRemoteSetupCompletionBlock, buildRemoteSetupGitConfigReviewBlock, buildRemoteSetupDatabaseRestoreBlock, getSurfacePromptValues, renderRemoteSetupApplyPrompt;
73707
73799
  var init_remoteSetupPrompt = __esm({
73708
73800
  "../../../../shared/devboxCore/dist/remoteSetupPrompt.js"() {
73709
73801
  "use strict";
73802
+ init_setupFinalResponsePrompt();
73710
73803
  REMOTE_SETUP_APPLY_E2B_TEMPLATE = `You're on a headless dev machine running in an E2B sandbox based on Ubuntu 24.04.
73711
73804
  It's a full Linux environment, and local ports are forwarded, so
73712
73805
  we can just run things here as if it were our local machine (i.e. use localhost).
@@ -73899,46 +73992,11 @@ Write a short, actionable summary to \`{{setup_todo_path}}\` with:
73899
73992
 
73900
73993
  ---
73901
73994
 
73902
- Final user-facing response:
73903
-
73904
- The user you're responding to is new to boxes.dev, and you're getting them set up
73905
- with their project running on a Template box. This setup message is automated, but all
73906
- later interactions in this thread will be with the user directly.
73907
-
73908
73995
  After you finish the setup work and write \`{{setup_todo_path}}\`, send a final
73909
73996
  assistant response in this thread. Do not put this user-facing response in
73910
73997
  \`{{setup_todo_path}}\`; that file is only the durable setup summary.
73911
73998
 
73912
- Your final response must:
73913
-
73914
- - Welcome the user to boxes.dev.
73915
- - Explain, in simple terms, what is set up and what still remains. Say whether
73916
- the app/project appears fully runnable when you know that; if you do not know,
73917
- say what you validated and what still needs checking.
73918
- - Offer to help them continue onboarding and learn how boxes.dev works.
73919
- - Offer to help them try out or validate their project/app setup, including
73920
- running the app and using port forwarding when relevant.
73921
- - If setup.todo contains remaining setup steps, offer to help finish those steps.
73922
- - Stay friendly, casual, and helpful. Avoid technical detail unless it is needed
73923
- for the user's next step.
73924
-
73925
- Use a message along these lines, adjusted to match what actually happened:
73926
-
73927
- \`\`\`text
73928
- Welcome to boxes.dev!
73929
-
73930
- I've set up your Template box. <Briefly say whether the app is runnable, what was
73931
- validated, and what still needs attention.>
73932
-
73933
- From here, I recommend trying out the platform:
73934
- 1. Create a new devbox + thread and ask the coding agent to build something small.
73935
- I can explain how this works or talk you through it.
73936
- 2. Run your app here and open it in your local browser with port forwarding. I
73937
- can run the app and walk you through it, or you can start it from the
73938
- terminal yourself.
73939
- 3. Finish any remaining setup. If the app will not run or something important is
73940
- missing for development, tell me and we can figure it out.
73941
- \`\`\``;
73999
+ {{final_response_block}}`;
73942
74000
  renderTemplate = (template, values) => template.replace(/\{\{([a-z_]+)\}\}/gu, (_2, key) => {
73943
74001
  const value = values[key];
73944
74002
  if (value === void 0) {
@@ -74051,6 +74109,7 @@ below.`;
74051
74109
  setup_path: setupPath,
74052
74110
  entrypoints_block: buildRemoteSetupEntrypointsBlock(entrypoints),
74053
74111
  setup_todo_path: setupTodoPath,
74112
+ final_response_block: renderSetupFinalResponsePrompt("automatic"),
74054
74113
  git_config_review_block: buildRemoteSetupGitConfigReviewBlock(gitConfigReviewPath),
74055
74114
  setup_completion_block: buildRemoteSetupCompletionBlock(completionMode, setupTodoPath),
74056
74115
  database_restore_block: buildRemoteSetupDatabaseRestoreBlock({
@@ -74693,7 +74752,7 @@ var init_packageVersion = __esm({
74693
74752
  return path17.join(process.cwd(), "dvb");
74694
74753
  };
74695
74754
  readEmbeddedPackageVersion = () => {
74696
- const raw = "1.0.1050";
74755
+ const raw = "1.0.1051";
74697
74756
  return trimVersion(raw);
74698
74757
  };
74699
74758
  readNearestPackageMetadata = (basePath) => {
@@ -295835,4 +295894,4 @@ react/cjs/react-jsx-runtime.development.js:
295835
295894
  *)
295836
295895
  */
295837
295896
 
295838
- //# debugId=24d3240a-70f6-599c-abcc-85e678461e94
295897
+ //# debugId=7b8078e5-c984-5e42-8f1e-d9d4348ee2f4
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]="2eaa96d1-a2e9-509f-880e-a4ccbcd051a9")}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]="a9afcb43-4806-5154-9842-36529ed47771")}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";
@@ -64612,9 +64612,9 @@ var init_sentry = __esm({
64612
64612
  uncaughtExceptionMonitorInstalled = false;
64613
64613
  currentDevboxSentryUser = null;
64614
64614
  readBuildMetadata = () => {
64615
- const rawPackageVersion = "1.0.1050";
64616
- const rawGitSha = "ef46dfbfec3389cfd62ac373db540193c0c4cd0d";
64617
- const rawSentryRelease = "boxes-dev-dvb@1.0.1050+ef46dfbfec3389cfd62ac373db540193c0c4cd0d";
64615
+ const rawPackageVersion = "1.0.1051";
64616
+ const rawGitSha = "a146f896d6bb73d0ee0446cd7d2f7fbf92250dd8";
64617
+ const rawSentryRelease = "boxes-dev-dvb@1.0.1051+a146f896d6bb73d0ee0446cd7d2f7fbf92250dd8";
64618
64618
  const packageVersion = typeof rawPackageVersion === "string" ? rawPackageVersion : void 0;
64619
64619
  const gitSha = typeof rawGitSha === "string" ? rawGitSha : void 0;
64620
64620
  const sentryRelease = typeof rawSentryRelease === "string" ? rawSentryRelease : void 0;
@@ -66631,10 +66631,18 @@ var init_desktopInitAssets = __esm({
66631
66631
  }
66632
66632
  });
66633
66633
 
66634
+ // ../../../../shared/devboxCore/dist/setupFinalResponsePrompt.js
66635
+ var init_setupFinalResponsePrompt = __esm({
66636
+ "../../../../shared/devboxCore/dist/setupFinalResponsePrompt.js"() {
66637
+ "use strict";
66638
+ }
66639
+ });
66640
+
66634
66641
  // ../../../../shared/devboxCore/dist/remoteSetupPrompt.js
66635
66642
  var init_remoteSetupPrompt = __esm({
66636
66643
  "../../../../shared/devboxCore/dist/remoteSetupPrompt.js"() {
66637
66644
  "use strict";
66645
+ init_setupFinalResponsePrompt();
66638
66646
  }
66639
66647
  });
66640
66648
 
@@ -66813,7 +66821,7 @@ var init_packageVersion = __esm({
66813
66821
  return path8.join(process.cwd(), "dvb");
66814
66822
  };
66815
66823
  readEmbeddedPackageVersion = () => {
66816
- const raw = "1.0.1050";
66824
+ const raw = "1.0.1051";
66817
66825
  return trimVersion(raw);
66818
66826
  };
66819
66827
  readNearestPackageMetadata = (basePath) => {
@@ -79960,4 +79968,4 @@ smol-toml/dist/index.js:
79960
79968
  *)
79961
79969
  */
79962
79970
 
79963
- //# debugId=2eaa96d1-a2e9-509f-880e-a4ccbcd051a9
79971
+ //# debugId=a9afcb43-4806-5154-9842-36529ed47771
@@ -341,8 +341,8 @@ terminal bell can request attention without adding an unread thread.
341
341
  ## Search Your Threads
342
342
 
343
343
  Press **Cmd+F** (Ctrl+F), or choose the search button (a magnifying glass)
344
- beside the back button, to open thread search. It searches the text of your
345
- own Codex and Claude threads across all of your projects, including archived
344
+ beside the back button, to open thread search. It searches the titles and
345
+ text of your own Codex and Claude threads across all of your projects, including archived
346
346
  threads, threads on sleeping machines,
347
347
  and threads kept in cold storage. Searching never wakes a machine.
348
348
 
@@ -351,17 +351,21 @@ words in that order. Straight and curly double quotes work. Capitalization
351
351
  and punctuation do not need to match; words outside quotes help pick the best
352
352
  matches.
353
353
 
354
- Search covers your messages and each agent's final replies. Progress
355
- updates, tool activity and output, and attachments are not included. A new
356
- message becomes searchable a few seconds after the agent's reply finishes,
354
+ Message search covers your messages and each agent's final replies. Progress
355
+ updates, tool activity and output, and attachments are not included. A
356
+ thread's new title is searchable as soon as it changes. A new message becomes
357
+ searchable a few seconds after the agent's reply finishes,
357
358
  and the thread's earlier messages stay searchable while the agent is still
358
359
  working. A deleted thread leaves the results as soon as you delete it.
359
360
 
360
- Results show one row per thread for up to 30 threads, ordered by how well
361
- they match. Each row shows the thread title, how long ago the thread was last
362
- active, and a highlighted excerpt labeled with who wrote the matching
363
- message. Archived threads have an archive icon, and each
364
- row names its project when the results come from more than one project. Use
361
+ Results show one row per thread for up to 30 threads, best match first. A
362
+ thread ranks higher when its title contains every search word, when several
363
+ of its messages match, and when it was active recently. The last word also
364
+ matches the start of a title word, so titles match while you type. Each row
365
+ shows the thread title, how long ago the thread was last active, and a
366
+ highlighted excerpt labeled with who wrote the matching message. A thread
367
+ found by its title alone shows no excerpt. Archived threads have an archive
368
+ icon, and each row names its project when the results come from more than one project. Use
365
369
  the arrow keys and **Enter**, or click a row, to open that thread in its
366
370
  project.
367
371
 
@@ -56,10 +56,11 @@ twice.
56
56
  ## Thread List
57
57
 
58
58
  Tap **Search messages in all threads** above the list on Home or in a project to
59
- search your messages and the final replies in your own Codex and Claude
60
- threads across all projects. Results include archived and cold-stored
61
- conversations, list the closest matches first, and show
62
- highlighted excerpts. Tap a result to open the thread. Searching does not wake a machine.
59
+ search the titles, your messages, and the final replies in your own Codex and
60
+ Claude threads across all projects. Results include archived and cold-stored
61
+ conversations and list the best matches first, favoring threads whose title
62
+ contains every search word and threads that were active recently. Message
63
+ matches show highlighted excerpts. Tap a result to open the thread. Searching does not wake a machine.
63
64
  Team admins can also find matches from their Team Template editing threads;
64
65
  open those threads in the desktop app.
65
66
 
@@ -875,7 +875,8 @@ They may lag active work and shorten long messages. They do not wake boxes,
875
875
  mark threads read, claim links, or expose full tool logs. Without `--scope`,
876
876
  the existing `list` and `read` commands still select delegated children only.
877
877
 
878
- To find your own threads by what was said in them, search instead of listing:
878
+ To find your own threads by title or by what was said in them, search
879
+ instead of listing:
879
880
 
880
881
  ```bash
881
882
  dvb-onbox threads search --scope user --query "flaky deploy" --json
@@ -884,8 +885,8 @@ dvb-onbox threads read --scope user --thread <id> --cursor <readCursor> --turns
884
885
  ```
885
886
 
886
887
  Search uses the same index as thread search in the desktop and mobile apps. It
887
- covers your messages and the agents' final replies in your own Codex and
888
- Claude threads, including archived ones. Commentary, tool activity,
888
+ covers thread titles, your messages, and the agents' final replies in your
889
+ own Codex and Claude threads, including archived ones. Commentary, tool activity,
889
890
  attachments, and Team Template editing threads are not included. It accepts only the `project` and `user` scopes,
890
891
  which need the same permission levels as listing them. Put a phrase in double
891
892
  quotes to require those words together in that order.
@@ -897,6 +898,8 @@ conversation at the match, run `threads read` with the same scope, the
897
898
  thread's `id`, and `readCursor` as `--cursor`: the page ends with the matching
898
899
  turn, and its returned cursor continues to older messages. If the thread's history has been rebuilt since it was
899
900
  indexed, the read reports `cursor_expired`; read it without a cursor instead.
901
+ When only the thread's title matched, those four `match` fields are null, so
902
+ read that thread without a cursor.
900
903
  A new message becomes searchable a few seconds after the agent's reply
901
904
  finishes.
902
905
 
@@ -19,6 +19,15 @@ through a guided wizard. Both upload local project state and start a setup
19
19
  thread on the Template box. That thread applies the setup plan, installs
20
20
  missing project dependencies, checks important app entrypoints, and writes a
21
21
  setup summary or follow-up list when it finishes.
22
+
23
+ The setup thread's final reply explains what was validated and introduces the
24
+ Template box, snapshots, **New devbox + thread**, and additional threads on an
25
+ existing devbox. It also explains how to get started with Slack, Linear,
26
+ automations, and agent delegation and messaging. You can keep talking in that
27
+ thread for help with setup or using boxes.dev. The reply can arrive before
28
+ boxes.dev finishes saving the first snapshot; wait for setup to finish before
29
+ starting your first devbox.
30
+
22
31
  **Create from GitHub** is the fallback for a repository the user does not have
23
32
  locally: it clones one or more selected repositories into a new Template box,
24
33
  without env files, secrets, or untracked local work, and leaves environment
@@ -7,8 +7,9 @@ teammate's shared threads or Team Template administration.
7
7
 
8
8
  ## Connect and choose access
9
9
 
10
- Add the boxes.dev plugin or remote MCP connection in your assistant, then
11
- follow its authorization link. Sign in to boxes.dev and check the requesting
10
+ Add the boxes.dev plugin or a remote MCP connection to
11
+ `https://api.boxes.dev/mcp` in your assistant, then follow its authorization
12
+ link. Sign in to boxes.dev and check the requesting
12
13
  domain, return address, account and requested permissions. A client name marked unverified is
13
14
  supplied by the client, not an endorsement from boxes.dev.
14
15
 
@@ -87,11 +87,13 @@ the main thread list alongside other devbox threads.
87
87
 
88
88
  To start your own thread, mention `@boxes.dev` and write your request. Under
89
89
  **Who else can trigger a new thread?**, choose **No one** (the default),
90
- **Teammates I choose**, or **Any teammate with Slack connected**. This setting
91
- belongs to you: teammates cannot give themselves access. Anyone you allow must
92
- be an active member of the same boxes.dev team with a linked identity in the
93
- connected Slack workspace. They can start a thread in your workspace by
94
- mentioning `@boxes.dev @YourName`, followed by their request.
90
+ **Teammates I choose**, **Any teammate with Slack connected**, or **Teammates
91
+ and bots**. This setting belongs to you: teammates cannot give themselves
92
+ access. Anyone you allow must be an active member of the same boxes.dev team
93
+ with a linked identity in the connected Slack workspace. They can start a
94
+ thread in your workspace by mentioning `@boxes.dev @YourName`, followed by
95
+ their request. **Teammates and bots** also lets bots in the connected Slack
96
+ workspace start threads the same way; see [Requests From Bots](#requests-from-bots).
95
97
 
96
98
  ## Create A Slack Named Command Automation
97
99
 
@@ -120,7 +122,9 @@ shared with another organization is always a choice you make. When you choose
120
122
  and a shared channel is marked **External** there.
121
123
 
122
124
  For named commands, choose who can run it. The owner can always run it; you can
123
- also allow chosen teammates or any teammate with Slack connected.
125
+ also allow chosen teammates or any teammate with Slack connected. **Me,
126
+ teammates, and bots** allows any teammate with Slack connected plus bots in the
127
+ connected Slack workspace; see [Requests From Bots](#requests-from-bots).
124
128
 
125
129
  ## Running From Slack
126
130
 
@@ -175,6 +179,41 @@ agent's final answer back into the same Slack thread or DM.
175
179
  To return to the original Slack conversation from the desktop workbench, click
176
180
  the Slack icon beside the thread title. Hover over it to see **Open Slack thread**.
177
181
 
182
+ ### Requests From Bots
183
+
184
+ Bots and apps installed in the connected Slack workspace, such as a signup or
185
+ alerting bot, can start an automation whose access setting is **Me, teammates,
186
+ and bots** (named commands) or **Teammates and bots** (the default receiver).
187
+ Every other setting ignores bots.
188
+
189
+ A bot has no boxes.dev account, so its message has to name the owner:
190
+
191
+ - For a named command, the bot uses the full command with the owner's name,
192
+ such as `@boxes.dev !ananya/onboarding New signup: sam@example.com`. The
193
+ automation editor shows the exact command. A bot's `!onboarding` without the
194
+ owner's name, or a plain `@boxes.dev` request, does nothing.
195
+ - For a default receiver, the bot mentions the owner after `@boxes.dev`, as a
196
+ teammate would: `@boxes.dev @Ananya <request>`.
197
+
198
+ A bot that posts through the Slack API writes each mention as `<@MEMBER_ID>`
199
+ using the Slack member IDs of the boxes.dev app and the owner.
200
+
201
+ The run belongs to the automation owner and uses the owner's project, devbox,
202
+ credentials, and usage. The agent is told that a Slack bot sent the request
203
+ and that instructions inside bot messages can come from people outside the
204
+ team. Anyone who can make an allowed bot post in Slack, for example by
205
+ submitting a form the bot relays, can send requests with the owner's access,
206
+ so allow bots only on automations you are comfortable exposing that way.
207
+
208
+ boxes.dev never starts work from its own messages, deleted bots, or bots that
209
+ belong to another organization in a Slack Connect channel. The location
210
+ setting still applies. When boxes.dev does not accept a bot's message, it
211
+ posts no help or rejection reply. Once a bot starts a run, started messages
212
+ and final replies follow the automation's activity settings, and the owner
213
+ does not get the teammate DM. An allowed bot can send follow-ups in the linked
214
+ thread by mentioning `@boxes.dev` again, and boxes.dev replies to those
215
+ follow-ups as it does for people. Files that bots post are never imported.
216
+
178
217
  ## Choose What Appears In Slack
179
218
 
180
219
  In the automation editor, **What should boxes.dev post in the Slack thread?**
@@ -188,13 +227,23 @@ checkboxes. For quiet customer channels, choose **None** under **Slack Connect**
188
227
  are enabled. Leave it off for a short status and link. It starts off for Slack
189
228
  Connect. Turning off the parent reply keeps the full-response choice for later.
190
229
 
230
+ **Messages the agent is asked to post** lets the agent post its own messages in
231
+ the Slack thread with `boxes-slack reply`, such as updates during long work.
232
+ It starts off for both audiences and is separate from the end-of-run reply
233
+ rows. The agent posts only when the request or the automation's instructions
234
+ ask it to, and it does not repeat a final reply that boxes.dev already posts.
235
+ This matters for threads that keep working after the Slack request, because
236
+ boxes.dev posts automatic replies only for turns that start from Slack.
237
+
191
238
  The location menu still decides where new runs can start. The Slack Connect
192
239
  column appears when that location can include shared channels; hiding the
193
240
  column keeps its saved choices. Attachment warnings can remain on even when
194
241
  started messages or follow-up confirmations are off.
195
242
 
196
243
  Changes apply to new Slack threads. Existing linked threads keep the choices
197
- they started with. These settings control automatic activity for this
244
+ they started with, except for agent messages: the current setting applies each
245
+ time an agent posts, so turning it off also stops agents in existing threads.
246
+ These settings control automatic activity for this
198
247
  automation; help and replies before boxes.dev can identify an automation are
199
248
  separate. Turning activity off does not send replacement DMs. The existing DM
200
249
  to an owner when a teammate starts work in their workspace is unchanged.
@@ -207,10 +256,10 @@ mention stay in Slack and are not sent to the agent.
207
256
 
208
257
  Anyone allowed to run the automation can send follow-ups in its linked Slack
209
258
  threads, including threads the owner started. Each follow-up reaches the agent
210
- with a note naming its sender. When the sender is a teammate, that note also
211
- names the project owner, says the work runs in the owner's project with the
212
- owner's credentials, and asks the agent to keep the owner's secrets and
213
- credentials out of its replies. A run a teammate starts carries the same note
259
+ with a note naming its sender; for a bot, the note says a bot sent it. When the
260
+ sender is a teammate or a bot, that note also names the project owner, says the
261
+ work runs in the owner's project with the owner's credentials, and asks the
262
+ agent to keep the owner's secrets and credentials out of its replies. A run a teammate starts carries the same note
214
263
  in its first prompt.
215
264
 
216
265
  To start a new teammate-owned run from an already linked Slack thread,
@@ -287,9 +336,11 @@ current Slack integration. A member of another organization in a shared channel
287
336
  cannot start a thread, send a follow-up, be assigned work, or have their files
288
337
  imported.
289
338
 
290
- Agent Slack access is read-only. In Slack-triggered runs, the agent can read
291
- the triggering Slack thread and direct Slack links the user provides, but it
292
- does not receive Slack tokens and cannot browse the workspace.
339
+ In Slack-triggered runs, the agent can read the triggering Slack thread and
340
+ direct Slack links the user provides. When **Messages the agent is asked to
341
+ post** is on for that conversation, it can also post to the triggering Slack
342
+ thread, and nowhere else. It does not receive Slack tokens and cannot browse
343
+ the workspace.
293
344
 
294
345
  ## Troubleshooting
295
346
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@boxes-dev/dvb-runtime",
3
- "version": "1.0.1050",
3
+ "version": "1.0.1051",
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",
@@ -79,5 +79,5 @@
79
79
  "e2b": "^2.18.0",
80
80
  "ink-testing-library": "^4.0.0"
81
81
  },
82
- "devboxReleasedAt": "2026-10-02T17:17:03Z"
82
+ "devboxReleasedAt": "2026-10-03T17:57:33Z"
83
83
  }