@huaweidevtools/aishell-dsh-e2b 0.0.1-beta.5 → 0.0.1-beta.7

package/lib/index.js

@@ -2457,7 +2457,11 @@ If the request does not make clear which of these it is, ask the user before cho
 
 A sandbox is often the right place to work something out before committing real resources to it.
 
-This conversation works in at most one sandbox at a time. Create it with aishell__sandbox_create before the tools that use it, and choose its lifetime there — the value should match what the work needs, since the sandbox and its contents are deleted when it expires.`;
+This conversation works in at most one sandbox at a time. Create it with aishell__sandbox_create before the tools that use it, and choose its lifetime there — the value should match what the work needs, since the sandbox and its contents are deleted when it expires.
+
+Never put sensitive material in a sandbox. aishell__sandbox_get_port_url makes what you serve publicly reachable by anyone who has the address, for as long as the sandbox lives — which is exactly what makes a sandbox useful, and exactly why it must not hold anything private. That covers credentials and keys of any kind, personal data, internal documents, and content that is unlawful to publish: political material and adult, gambling or drug-related content among it. A public URL cannot be unpublished: anyone who opened it, or copied what it served, keeps that copy after the sandbox is deleted.
+
+If a request would require any of that, stop and say so rather than deploying it. Do not work around the rule by splitting the content, renaming files, or serving it from another port.`;
 /**
 * Register the guidance section.
 *

package/lib/types/prompt.d.ts

@@ -48,7 +48,7 @@ export declare const SANDBOX_PROMPT_ORDER = 110;
 /** Name this contribution registers under; unique across the assembled prompt. */
 export declare const SANDBOX_SECTION_NAME = "aishell:e2b";
 /** What the model reads about which tier to use. */
-export declare const SANDBOX_GUIDANCE = "A sandbox is a Linux environment running remotely. It exists for a bounded time, then is deleted along with everything in it. What it gives you that this machine does not is a public address.\n\nThat is the clearest signal: when the work has to be deployed somewhere reachable and the user wants a URL they can open \u2014 a web app, a demo, a service, a static page \u2014 use the sandbox tools (aishell__sandbox_*). Put the files there with aishell__sandbox_files_write, start the server with aishell__sandbox_commands_run and background: true, then call aishell__sandbox_get_port_url and give the user that address.\n\nAt the other end, a production system belongs in real infrastructure, deployed with the Terraform tools (aishell__terraform_* and their neighbours). It will cost money, it should keep running, and it will be operated. The sandbox is the wrong tier for it not because it is small but because it is deliberately short-lived \u2014 the address stops working when it expires.\n\nSo: a page or a demo, or anything that should end in a URL to open, is a sandbox. A system to run and keep running is Terraform.\n\nIf the request does not make clear which of these it is, ask the user before choosing. Say what the difference amounts to for them: a sandbox is throwaway and costs nothing to discard, while Terraform provisions real resources that are billed and meant to keep running. Follow what they pick.\n\nA sandbox is often the right place to work something out before committing real resources to it.\n\nThis conversation works in at most one sandbox at a time. Create it with aishell__sandbox_create before the tools that use it, and choose its lifetime there \u2014 the value should match what the work needs, since the sandbox and its contents are deleted when it expires.";
+export declare const SANDBOX_GUIDANCE = "A sandbox is a Linux environment running remotely. It exists for a bounded time, then is deleted along with everything in it. What it gives you that this machine does not is a public address.\n\nThat is the clearest signal: when the work has to be deployed somewhere reachable and the user wants a URL they can open \u2014 a web app, a demo, a service, a static page \u2014 use the sandbox tools (aishell__sandbox_*). Put the files there with aishell__sandbox_files_write, start the server with aishell__sandbox_commands_run and background: true, then call aishell__sandbox_get_port_url and give the user that address.\n\nAt the other end, a production system belongs in real infrastructure, deployed with the Terraform tools (aishell__terraform_* and their neighbours). It will cost money, it should keep running, and it will be operated. The sandbox is the wrong tier for it not because it is small but because it is deliberately short-lived \u2014 the address stops working when it expires.\n\nSo: a page or a demo, or anything that should end in a URL to open, is a sandbox. A system to run and keep running is Terraform.\n\nIf the request does not make clear which of these it is, ask the user before choosing. Say what the difference amounts to for them: a sandbox is throwaway and costs nothing to discard, while Terraform provisions real resources that are billed and meant to keep running. Follow what they pick.\n\nA sandbox is often the right place to work something out before committing real resources to it.\n\nThis conversation works in at most one sandbox at a time. Create it with aishell__sandbox_create before the tools that use it, and choose its lifetime there \u2014 the value should match what the work needs, since the sandbox and its contents are deleted when it expires.\n\nNever put sensitive material in a sandbox. aishell__sandbox_get_port_url makes what you serve publicly reachable by anyone who has the address, for as long as the sandbox lives \u2014 which is exactly what makes a sandbox useful, and exactly why it must not hold anything private. That covers credentials and keys of any kind, personal data, internal documents, and content that is unlawful to publish: political material and adult, gambling or drug-related content among it. A public URL cannot be unpublished: anyone who opened it, or copied what it served, keeps that copy after the sandbox is deleted.\n\nIf a request would require any of that, stop and say so rather than deploying it. Do not work around the rule by splitting the content, renaming files, or serving it from another port.";
 /**
  * Register the guidance section.
  *

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@huaweidevtools/aishell-dsh-e2b",
   "description": "Runs throwaway and preview deployments in E2B sandboxes on DSH — sandbox lifecycle, commands, and files as tools",
-  "version": "0.0.1-beta.5",
+  "version": "0.0.1-beta.7",
   "publishConfig": {
     "access": "public"
   },
@@ -27,7 +27,7 @@
   "license": "Apache-2.0",
   "dependencies": {
     "e2b": "2.59.0",
-    "@huaweidevtools/aishell-dsh-credentials-store": "0.0.1-beta.5"
+    "@huaweidevtools/aishell-dsh-credentials-store": "0.0.1-beta.7"
   },
   "peerDependencies": {
     "@deepseek-ai/cordis": "^4.0.4",