@downcity/agent 1.1.206 → 1.1.208

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.
Files changed (37) hide show
  1. package/bin/agent/local/AgentInstructions.d.ts +1 -0
  2. package/bin/agent/local/AgentInstructions.d.ts.map +1 -1
  3. package/bin/agent/local/AgentInstructions.js +10 -10
  4. package/bin/agent/local/AgentInstructions.js.map +1 -1
  5. package/bin/executor/composer/system/default/StaticPromptCatalog.d.ts +4 -0
  6. package/bin/executor/composer/system/default/StaticPromptCatalog.d.ts.map +1 -1
  7. package/bin/executor/composer/system/default/StaticPromptCatalog.js +4 -0
  8. package/bin/executor/composer/system/default/StaticPromptCatalog.js.map +1 -1
  9. package/bin/executor/composer/system/default/SystemDomain.d.ts +1 -1
  10. package/bin/executor/composer/system/default/SystemDomain.d.ts.map +1 -1
  11. package/bin/executor/composer/system/default/SystemDomain.js +2 -7
  12. package/bin/executor/composer/system/default/SystemDomain.js.map +1 -1
  13. package/bin/executor/composer/system/default/SystemPromptAssets.d.ts +0 -4
  14. package/bin/executor/composer/system/default/SystemPromptAssets.d.ts.map +1 -1
  15. package/bin/executor/composer/system/default/SystemPromptAssets.js +0 -5
  16. package/bin/executor/composer/system/default/SystemPromptAssets.js.map +1 -1
  17. package/bin/executor/composer/system/default/assets/core.prompt.d.ts +1 -1
  18. package/bin/executor/composer/system/default/assets/core.prompt.d.ts.map +1 -1
  19. package/bin/executor/composer/system/default/assets/core.prompt.js +1 -1
  20. package/bin/executor/composer/system/default/assets/core.prompt.js.map +1 -1
  21. package/package.json +3 -3
  22. package/scripts/agent-env-shell-sandbox.test.mjs +105 -0
  23. package/scripts/session-system-blocks.test.mjs +73 -0
  24. package/scripts/shell-sandbox-env.test.mjs +18 -0
  25. package/src/agent/local/AgentInstructions.ts +10 -10
  26. package/src/executor/composer/system/default/StaticPromptCatalog.ts +4 -0
  27. package/src/executor/composer/system/default/SystemDomain.ts +1 -9
  28. package/src/executor/composer/system/default/SystemPromptAssets.ts +0 -6
  29. package/src/executor/composer/system/default/assets/core.prompt.ts +1 -1
  30. package/src/executor/composer/system/default/assets/core.prompt.ts.txt +37 -15
  31. package/tsconfig.tsbuildinfo +1 -1
  32. package/bin/executor/composer/system/default/assets/plugin.prompt.d.ts +0 -7
  33. package/bin/executor/composer/system/default/assets/plugin.prompt.d.ts.map +0 -1
  34. package/bin/executor/composer/system/default/assets/plugin.prompt.js +0 -8
  35. package/bin/executor/composer/system/default/assets/plugin.prompt.js.map +0 -1
  36. package/src/executor/composer/system/default/assets/plugin.prompt.ts +0 -9
  37. package/src/executor/composer/system/default/assets/plugin.prompt.ts.txt +0 -20
@@ -1,7 +0,0 @@
1
- /**
2
- * 自动生成文件,请勿手改。
3
- * 源文件:由同路径 `*.ts.txt` 生成。
4
- */
5
- declare const TEXT_MODULE_CONTENT = "# Plugin State\n\nYou are working in a plugin-based execution environment.\n\n## Plugin Call Rules\n\n- When you need plugin capabilities, prefer invoking the plugin action through the available tools.\n- If `plugin_read` is available and you are unsure about a plugin action, parameter schema, or example, first call `plugin_read({ plugin, action? })` to read metadata.\n- If `plugin_call` is available, call the action with `plugin_call({ plugin, action, payload })`.\n- `plugin_call.plugin` is the plugin name, for example `skill`, `task`, `memory`, or `contact`.\n- `plugin_call.action` is the action name, for example `list`, `lookup`, `create`, or `run`.\n- `plugin_call.payload` is a structured JSON payload. Pass `{}` when there are no parameters. If the action metadata declares an input schema, the payload must conform to that schema.\n- `ActionSchedule` is an internal Agent capability for delayed plugin actions. It is not a standalone plugin.\n\n## Available Plugin Overview\n\n- Current built-in managed plugins: `shell` / `chat` / `task` / `memory` / `contact`.\n- Current built-in local plugins: `auth` / `skill`.\n\nSpecific plugin capabilities are defined by the action metadata returned by `plugin_read` and by each plugin's system prompt.\n";
6
- export default TEXT_MODULE_CONTENT;
7
- //# sourceMappingURL=plugin.prompt.d.ts.map
@@ -1 +0,0 @@
1
- {"version":3,"file":"plugin.prompt.d.ts","sourceRoot":"","sources":["../../../../../../src/executor/composer/system/default/assets/plugin.prompt.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAGH,QAAA,MAAM,mBAAmB,kvCAAkvC,CAAC;AAE5wC,eAAe,mBAAmB,CAAC"}
@@ -1,8 +0,0 @@
1
- /**
2
- * 自动生成文件,请勿手改。
3
- * 源文件:由同路径 `*.ts.txt` 生成。
4
- */
5
- // Source: src/executor/composer/system/default/assets/plugin.prompt.ts.txt
6
- const TEXT_MODULE_CONTENT = "# Plugin State\n\nYou are working in a plugin-based execution environment.\n\n## Plugin Call Rules\n\n- When you need plugin capabilities, prefer invoking the plugin action through the available tools.\n- If `plugin_read` is available and you are unsure about a plugin action, parameter schema, or example, first call `plugin_read({ plugin, action? })` to read metadata.\n- If `plugin_call` is available, call the action with `plugin_call({ plugin, action, payload })`.\n- `plugin_call.plugin` is the plugin name, for example `skill`, `task`, `memory`, or `contact`.\n- `plugin_call.action` is the action name, for example `list`, `lookup`, `create`, or `run`.\n- `plugin_call.payload` is a structured JSON payload. Pass `{}` when there are no parameters. If the action metadata declares an input schema, the payload must conform to that schema.\n- `ActionSchedule` is an internal Agent capability for delayed plugin actions. It is not a standalone plugin.\n\n## Available Plugin Overview\n\n- Current built-in managed plugins: `shell` / `chat` / `task` / `memory` / `contact`.\n- Current built-in local plugins: `auth` / `skill`.\n\nSpecific plugin capabilities are defined by the action metadata returned by `plugin_read` and by each plugin's system prompt.\n";
7
- export default TEXT_MODULE_CONTENT;
8
- //# sourceMappingURL=plugin.prompt.js.map
@@ -1 +0,0 @@
1
- {"version":3,"file":"plugin.prompt.js","sourceRoot":"","sources":["../../../../../../src/executor/composer/system/default/assets/plugin.prompt.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAEH,2EAA2E;AAC3E,MAAM,mBAAmB,GAAG,+uCAA+uC,CAAC;AAE5wC,eAAe,mBAAmB,CAAC"}
@@ -1,9 +0,0 @@
1
- /**
2
- * 自动生成文件,请勿手改。
3
- * 源文件:由同路径 `*.ts.txt` 生成。
4
- */
5
-
6
- // Source: src/executor/composer/system/default/assets/plugin.prompt.ts.txt
7
- const TEXT_MODULE_CONTENT = "# Plugin State\n\nYou are working in a plugin-based execution environment.\n\n## Plugin Call Rules\n\n- When you need plugin capabilities, prefer invoking the plugin action through the available tools.\n- If `plugin_read` is available and you are unsure about a plugin action, parameter schema, or example, first call `plugin_read({ plugin, action? })` to read metadata.\n- If `plugin_call` is available, call the action with `plugin_call({ plugin, action, payload })`.\n- `plugin_call.plugin` is the plugin name, for example `skill`, `task`, `memory`, or `contact`.\n- `plugin_call.action` is the action name, for example `list`, `lookup`, `create`, or `run`.\n- `plugin_call.payload` is a structured JSON payload. Pass `{}` when there are no parameters. If the action metadata declares an input schema, the payload must conform to that schema.\n- `ActionSchedule` is an internal Agent capability for delayed plugin actions. It is not a standalone plugin.\n\n## Available Plugin Overview\n\n- Current built-in managed plugins: `shell` / `chat` / `task` / `memory` / `contact`.\n- Current built-in local plugins: `auth` / `skill`.\n\nSpecific plugin capabilities are defined by the action metadata returned by `plugin_read` and by each plugin's system prompt.\n";
8
-
9
- export default TEXT_MODULE_CONTENT;
@@ -1,20 +0,0 @@
1
- # Plugin State
2
-
3
- You are working in a plugin-based execution environment.
4
-
5
- ## Plugin Call Rules
6
-
7
- - When you need plugin capabilities, prefer invoking the plugin action through the available tools.
8
- - If `plugin_read` is available and you are unsure about a plugin action, parameter schema, or example, first call `plugin_read({ plugin, action? })` to read metadata.
9
- - If `plugin_call` is available, call the action with `plugin_call({ plugin, action, payload })`.
10
- - `plugin_call.plugin` is the plugin name, for example `skill`, `task`, `memory`, or `contact`.
11
- - `plugin_call.action` is the action name, for example `list`, `lookup`, `create`, or `run`.
12
- - `plugin_call.payload` is a structured JSON payload. Pass `{}` when there are no parameters. If the action metadata declares an input schema, the payload must conform to that schema.
13
- - `ActionSchedule` is an internal Agent capability for delayed plugin actions. It is not a standalone plugin.
14
-
15
- ## Available Plugin Overview
16
-
17
- - Current built-in managed plugins: `shell` / `chat` / `task` / `memory` / `contact`.
18
- - Current built-in local plugins: `auth` / `skill`.
19
-
20
- Specific plugin capabilities are defined by the action metadata returned by `plugin_read` and by each plugin's system prompt.