@downcity/agent 1.1.287 → 1.1.310

package/src/executor/composer/system/default/DefaultSessionSystemComposer.ts

@@ -9,10 +9,10 @@
 import type {
   SessionSystemComposer,
 } from "@executor/composer/system/SessionSystemComposer.js";
-import type { AgentContext } from "@/agent/AgentContext.js";
-import type { SessionRunContext } from "@/types/executor/SessionRunContext.js";
+import type { PluginContext } from "@/types/plugin/PluginContext.js";
+import type { SessionComposeInput } from "@/types/session/SessionComposer.js";
 import {
-  resolveSessionSystemMessages,
+  resolve_session_system_messages,
   type SystemProfile,
 } from "@executor/composer/system/default/SystemDomain.js";
 
@@ -20,17 +20,17 @@ type DefaultSessionSystemComposerOptions = {
   /**
    * 项目根目录，用于渲染运行时 system 模板。
    */
-  projectRoot: string;
+  project_root: string;
 
   /**
    * 读取当前生效的静态 system 文本集合。
    */
-  getStaticSystemPrompts: () => string[];
+  get_static_system_prompts: () => string[];
 
   /**
    * 读取当前执行上下文（用于加载 plugin system 文本）。
    */
-  getContext: () => AgentContext;
+  get_context: () => PluginContext;
 
   /**
    * system 档位（默认 chat）。
@@ -44,33 +44,33 @@ type DefaultSessionSystemComposerOptions = {
 export class DefaultSessionSystemComposer implements SessionSystemComposer {
   readonly name = "prompt_system";
 
-  private readonly projectRoot: string;
-  private readonly getStaticSystemPrompts: DefaultSessionSystemComposerOptions["getStaticSystemPrompts"];
-  private readonly getContext: DefaultSessionSystemComposerOptions["getContext"];
+  private readonly project_root: string;
+  private readonly get_static_system_prompts: DefaultSessionSystemComposerOptions["get_static_system_prompts"];
+  private readonly get_context: DefaultSessionSystemComposerOptions["get_context"];
   private readonly profile: SystemProfile;
 
   constructor(options: DefaultSessionSystemComposerOptions) {
-    const projectRoot = String(options.projectRoot || "").trim();
-    if (!projectRoot) {
-      throw new Error("DefaultSessionSystemComposer requires a non-empty projectRoot");
+    const project_root = String(options.project_root || "").trim();
+    if (!project_root) {
+      throw new Error("DefaultSessionSystemComposer requires a non-empty project_root");
     }
-    this.projectRoot = projectRoot;
-    this.getStaticSystemPrompts = options.getStaticSystemPrompts;
-    this.getContext = options.getContext;
+    this.project_root = project_root;
+    this.get_static_system_prompts = options.get_static_system_prompts;
+    this.get_context = options.get_context;
     this.profile = options.profile === "task" ? "task" : "chat";
   }
 
-  async resolve(run_context: SessionRunContext) {
-    const sessionId = String(run_context.sessionId || "").trim();
-    if (!sessionId) {
-      throw new Error("DefaultSessionSystemComposer.resolve requires a non-empty sessionId");
+  async resolve(input: SessionComposeInput) {
+    const session_id = input.session.session_id;
+    if (!session_id) {
+      throw new Error("DefaultSessionSystemComposer.resolve requires a non-empty session_id");
     }
-    return await resolveSessionSystemMessages({
-      projectRoot: this.projectRoot,
-      sessionId,
+    return await resolve_session_system_messages({
+      project_root: this.project_root,
+      session_id,
       profile: this.profile,
-      staticSystemPrompts: this.getStaticSystemPrompts(),
-      context: this.getContext(),
+      static_system_prompts: this.get_static_system_prompts(),
+      context: this.get_context(),
     });
   }
 }

package/src/executor/composer/system/default/PromptRenderer.ts

@@ -9,7 +9,7 @@
 
 import { type SystemModelMessage } from "ai";
 import {
-  replaceVariablesInPrompts,
+  replace_variables_in_prompts,
   type PromptVariableMode,
 } from "@executor/composer/system/default/variables/VariableReplacer.js";
 
@@ -19,7 +19,7 @@ import {
  * 关键点（中文）
  * - 自动过滤空串并执行变量替换。
  */
-export async function transformPromptsIntoSystemMessages(
+export async function transform_prompts_into_system_messages(
   prompts: string[],
   options?: {
     /**
@@ -30,7 +30,7 @@ export async function transformPromptsIntoSystemMessages(
     /**
      * 会话 ID（用于模板变量）。
      */
-    sessionId?: string;
+    session_id?: string;
 
     /**
      * 变量替换模式。
@@ -46,7 +46,7 @@ export async function transformPromptsIntoSystemMessages(
   return Promise.all(
     nonEmptyPrompts.map(async (item) => ({
       role: "system" as const,
-      content: await replaceVariablesInPrompts(item, options),
+      content: await replace_variables_in_prompts(item, options),
     })),
   );
 }

package/src/executor/composer/system/default/SystemDomain.ts

@@ -7,9 +7,9 @@
  */
 
 import type { SystemModelMessage } from "ai";
-import { transformPromptsIntoSystemMessages } from "@executor/composer/system/default/PromptRenderer.js";
-import type { AgentContext } from "@/agent/AgentContext.js";
-import { buildRuntimeClockSystemPrompt } from "@executor/composer/system/default/variables/VariableReplacer.js";
+import { transform_prompts_into_system_messages } from "@executor/composer/system/default/PromptRenderer.js";
+import type { PluginContext } from "@/types/plugin/PluginContext.js";
+import { build_runtime_clock_system_prompt } from "@executor/composer/system/default/variables/VariableReplacer.js";
 import {
   CORE_SYSTEM_PROMPT,
   TASK_SYSTEM_PROMPT,
@@ -33,16 +33,16 @@ export const DEFAULT_SHIP_PROMPTS = CORE_SYSTEM_PROMPT;
  * - 仅承载“稳定规则”块，避免把每轮变化字段放在前缀 system。
  * - task 模式下追加任务输出规则；chat 模式为空。
  */
-export function buildContextSystemPrompt(input: {
+export function build_context_system_prompt(input: {
   /**
    * 项目根目录。
    */
-  projectRoot: string;
+  project_root: string;
 
   /**
    * 当前会话 ID。
    */
-  sessionId: string;
+  session_id: string;
 
   /**
    * 当前 system 模式（默认 chat）。
@@ -52,19 +52,19 @@ export function buildContextSystemPrompt(input: {
   /**
    * 额外上下文行（可选）。
    */
-  extraContextLines?: string[];
+  extra_context_lines?: string[];
 }): string {
-  const { projectRoot, extraContextLines } = input;
+  const { project_root, extra_context_lines } = input;
   const mode = input.mode === "task" ? "task" : "chat";
   if (mode === "chat") return "";
 
   const runtimeContextLines: string[] = [
     "Task runtime context:",
-    `- Project root: ${projectRoot}`,
+    `- Project root: ${project_root}`,
   ];
 
-  if (Array.isArray(extraContextLines) && extraContextLines.length > 0) {
-    runtimeContextLines.push(...extraContextLines);
+  if (Array.isArray(extra_context_lines) && extra_context_lines.length > 0) {
+    runtimeContextLines.push(...extra_context_lines);
   }
 
   const outputRules = [
@@ -85,7 +85,7 @@ export function buildContextSystemPrompt(input: {
  * - task 执行上下文可替换默认 core prompt（`DEFAULT_SHIP_PROMPTS`）为任务专用提示词。
  * - PROFILE/SOUL 等其他静态提示保持不变。
  */
-export function resolveStaticSystemPrompts(input: {
+export function resolve_static_system_prompts(input: {
   /**
    * 当前静态 system 文本集合。
    */
@@ -94,18 +94,18 @@ export function resolveStaticSystemPrompts(input: {
   /**
    * 可选默认 core prompt 替换文本（task 场景常用）。
    */
-  replaceDefaultCorePrompt?: string;
+  replace_default_core_prompt?: string;
 }): string[] {
   const base = Array.isArray(input.systems) ? [...input.systems] : [];
-  const replacement = String(input.replaceDefaultCorePrompt || "").trim();
+  const replacement = String(input.replace_default_core_prompt || "").trim();
   if (!replacement) return base;
   return [...base.filter((item) => item !== DEFAULT_SHIP_PROMPTS), replacement];
 }
 
 type ResolvedSystemContextProfile = {
   mode: "chat" | "task";
-  replaceDefaultCorePrompt?: string;
-  disablePluginSystems: string[];
+  replace_default_core_prompt?: string;
+  disable_plugin_systems: string[];
 };
 
 /**
@@ -123,19 +123,19 @@ export type SystemProfile = "chat" | "task";
  * - chat 模式：使用默认 core prompt 与全部 plugin system。
  * - task 模式：自动替换 task core prompt，并禁用 chat plugin system。
  */
-export function resolveSystemContextProfile(
+export function resolve_system_context_profile(
   profile?: SystemProfile,
 ): ResolvedSystemContextProfile {
   if (profile !== "task") {
     return {
       mode: "chat",
-      disablePluginSystems: [...DEFAULT_DISABLED_MANAGED_PLUGIN_NAMES],
+      disable_plugin_systems: [...DEFAULT_DISABLED_MANAGED_PLUGIN_NAMES],
     };
   }
   return {
     mode: "task",
-    replaceDefaultCorePrompt: TASK_SYSTEM_PROMPT,
-    disablePluginSystems: ["chat"],
+    replace_default_core_prompt: TASK_SYSTEM_PROMPT,
+    disable_plugin_systems: ["chat"],
   };
 }
 
@@ -146,20 +146,20 @@ export function resolveSystemContextProfile(
  * - core prompt 已包含 plugin 系统总规则；这里仅收集各 plugin 自己的 system prompt。
  * - 单个加载失败走 fail-open，不阻断主链路。
  */
-export async function loadManagedPluginSystemPrompts(input: {
+export async function load_managed_plugin_system_prompts(input: {
   /**
    * 当前执行上下文。
    */
-  context: AgentContext;
+  context: PluginContext;
 
   /**
    * 当前轮禁用的 plugin 名称集合。
    */
-  disabledPluginNames: string[];
+  disabled_plugin_names: string[];
 }): Promise<string[]> {
   const out: string[] = [];
-  const disabledPluginNames = new Set(
-    input.disabledPluginNames
+  const disabled_plugin_names = new Set(
+    input.disabled_plugin_names
       .map((item) => String(item || "").trim())
       .filter(Boolean),
   );
@@ -167,7 +167,7 @@ export async function loadManagedPluginSystemPrompts(input: {
   for (const snapshot of input.context.plugins.snapshots()) {
     const plugin = input.context.plugins.get(snapshot.name);
     if (!plugin) continue;
-    if (disabledPluginNames.has(plugin.name)) continue;
+    if (disabled_plugin_names.has(plugin.name)) continue;
     if (typeof plugin.system !== "function") continue;
     try {
       if (input.context.plugins.status(plugin.name)?.status !== "ready") continue;
@@ -194,11 +194,11 @@ export async function loadManagedPluginSystemPrompts(input: {
  * - 若 plugin 显式声明 availability 且当前 unavailable，则跳过其 system 注入。
  * - 单个 plugin 加载失败走 fail-open，不阻断主链路。
  */
-export async function loadLocalPluginSystemPrompts(input: {
+export async function load_local_plugin_system_prompts(input: {
   /**
    * 当前统一执行上下文。
    */
-  context: AgentContext;
+  context: PluginContext;
 }): Promise<string[]> {
   void input;
   return [];
@@ -210,16 +210,16 @@ export async function loadLocalPluginSystemPrompts(input: {
  * 关键点（中文）
  * - context/static/plugin 的组装逻辑统一收敛在 system 域。
  */
-export async function buildSessionSystemMessages(input: {
+export async function build_session_system_messages(input: {
   /**
    * 项目根目录（用于模板变量和运行态上下文）。
    */
-  projectRoot: string;
+  project_root: string;
 
   /**
    * 当前会话 ID。
    */
-  sessionId: string;
+  session_id: string;
 
   /**
    * 本轮模式（chat/task）。
@@ -229,66 +229,66 @@ export async function buildSessionSystemMessages(input: {
   /**
    * 可选默认 core prompt 替换文本（task 场景常用）。
    */
-  replaceDefaultCorePrompt?: string;
+  replace_default_core_prompt?: string;
 
   /**
    * 静态 system 文本集合（profile/soul/user/default）。
    */
-  staticSystemPrompts: string[];
+  static_system_prompts: string[];
 
   /**
    * 受 agent 托管的 plugin system 文本集合（main plugin + managed plugins）。
    */
-  managedPluginSystemPrompts: string[];
+  managed_plugin_system_prompts: string[];
 
   /**
    * 本地 plugin system 文本集合。
    */
-  localPluginSystemPrompts: string[];
+  local_plugin_system_prompts: string[];
 }): Promise<SystemModelMessage[]> {
-  const runtimeClockText = buildRuntimeClockSystemPrompt({
-    projectPath: input.projectRoot,
-    sessionId: input.sessionId,
+  const runtimeClockText = build_runtime_clock_system_prompt({
+    projectPath: input.project_root,
+    session_id: input.session_id,
   });
   const runtimeClockMessages: SystemModelMessage[] = runtimeClockText
     ? [{ role: "system", content: runtimeClockText }]
     : [];
-  const runtimeSystemText = buildContextSystemPrompt({
-    projectRoot: input.projectRoot,
-    sessionId: input.sessionId,
+  const runtimeSystemText = build_context_system_prompt({
+    project_root: input.project_root,
+    session_id: input.session_id,
     mode: input.mode,
   });
   const runtimeRuleMessages: SystemModelMessage[] = runtimeSystemText
     ? [{ role: "system", content: runtimeSystemText }]
     : [];
 
-  const staticSystemMessages = await transformPromptsIntoSystemMessages(
-    resolveStaticSystemPrompts({
-      systems: input.staticSystemPrompts,
-      replaceDefaultCorePrompt: input.replaceDefaultCorePrompt,
+  const staticSystemMessages = await transform_prompts_into_system_messages(
+    resolve_static_system_prompts({
+      systems: input.static_system_prompts,
+      replace_default_core_prompt: input.replace_default_core_prompt,
     }),
     {
-      projectPath: input.projectRoot,
+      projectPath: input.project_root,
       variableMode: "stable",
     },
   );
 
-  const managedPluginSystemMessages = await transformPromptsIntoSystemMessages(
-    Array.isArray(input.managedPluginSystemPrompts)
-      ? input.managedPluginSystemPrompts
+  const managedPluginSystemMessages = await transform_prompts_into_system_messages(
+    Array.isArray(input.managed_plugin_system_prompts)
+      ? input.managed_plugin_system_prompts
       : [],
     {
-      projectPath: input.projectRoot,
+      projectPath: input.project_root,
       variableMode: "stable",
     },
   );
 
-  const localPluginSystemMessages = await transformPromptsIntoSystemMessages(
-    Array.isArray(input.localPluginSystemPrompts)
-      ? input.localPluginSystemPrompts
+  const localPluginSystemMessages = await transform_prompts_into_system_messages(
+    Array.isArray(input.local_plugin_system_prompts)
+      ? input.local_plugin_system_prompts
       : [],
     {
-      projectPath: input.projectRoot,
+      projectPath: input.project_root,
       variableMode: "stable",
     },
   );
@@ -305,16 +305,16 @@ export async function buildSessionSystemMessages(input: {
 /**
  * 统一解析一次 Session 运行所需的 system messages（含上下文档位判定与 plugin 收集）。
  */
-export async function resolveSessionSystemMessages(input: {
+export async function resolve_session_system_messages(input: {
   /**
    * 项目根目录。
    */
-  projectRoot: string;
+  project_root: string;
 
   /**
    * 当前会话 ID。
    */
-  sessionId: string;
+  session_id: string;
 
   /**
    * 当前 system 档位（默认 chat）。
@@ -324,26 +324,26 @@ export async function resolveSessionSystemMessages(input: {
   /**
    * 当前静态 system 文本集合。
    */
-  staticSystemPrompts: string[];
+  static_system_prompts: string[];
 
   /**
    * 当前执行上下文。
    */
-  context: AgentContext;
+  context: PluginContext;
 
 }): Promise<SystemModelMessage[]> {
-  const profile = resolveSystemContextProfile(input.profile);
-  return await buildSessionSystemMessages({
-    projectRoot: input.projectRoot,
-    sessionId: input.sessionId,
+  const profile = resolve_system_context_profile(input.profile);
+  return await build_session_system_messages({
+    project_root: input.project_root,
+    session_id: input.session_id,
     mode: profile.mode,
-    replaceDefaultCorePrompt: profile.replaceDefaultCorePrompt,
-    staticSystemPrompts: input.staticSystemPrompts,
-    managedPluginSystemPrompts: await loadManagedPluginSystemPrompts({
+    replace_default_core_prompt: profile.replace_default_core_prompt,
+    static_system_prompts: input.static_system_prompts,
+    managed_plugin_system_prompts: await load_managed_plugin_system_prompts({
       context: input.context,
-      disabledPluginNames: profile.disablePluginSystems,
+      disabled_plugin_names: profile.disable_plugin_systems,
     }),
-    localPluginSystemPrompts: await loadLocalPluginSystemPrompts({
+    local_plugin_system_prompts: await load_local_plugin_system_prompts({
       context: input.context,
     }),
   });

package/src/executor/composer/system/default/assets/core.prompt.ts

@@ -4,6 +4,6 @@
  */
 
 // Source: src/executor/composer/system/default/assets/core.prompt.ts.txt
-const TEXT_MODULE_CONTENT = "# Downcity Agent\n\nYou are a Downcity Agent running inside the Downcity Agent runtime.\n\nYour job is to help the user inspect, edit, run, debug, and operate the current project through the runtime tools and enabled plugins.\n\nYou have permission to use and modify only the project bound to the current session unless the user explicitly asks for a broader action and the runtime grants the required capability.\n\n# Harness Design\n\nDowncity Agent is a harness around an existing human-owned workspace, not a replacement platform or a detached autonomous worker.\n\n- The harness lets the Agent enter the user's existing project instead of forcing the user to migrate work into a new AI platform.\n- The project structure is the control surface. Files, directories, scripts, docs, configuration, and existing workflows define the practical business boundary.\n- The Agent inherits the workspace's knowledge topology. Read and follow the existing structure before creating new abstractions, stores, or process layers.\n- The harness keeps the human in control. The user owns intent, boundaries, approvals, and final judgment; the Agent supplies high-density execution inside those boundaries.\n- Agent state should remain observable and handoff-friendly. Prefer outputs, changes, and explanations that a human can inspect, resume, or correct through normal project artifacts.\n- Autonomy should be progressive. Execute low-risk, reversible work directly; pause for clarification or approval when the boundary, consequence, or owner is unclear.\n- Tools and plugins are harness surfaces. Use them to act precisely in the current execution context without treating any tool as a reason to ignore the user's native workflow.\n- Prefer project-native, maintainable changes over clever platform-shaped abstractions. The best result should feel like it naturally belongs in the existing workspace.\n\n# Shell Commands\n\nCommand execution tools:\n- Prefer `shell_exec` for short, one-off commands.\n- Use `shell_session` for long-running tasks, tasks that need status checks, or processes that need stdin interaction.\n- For long-running tasks, use `wait_ms` with `shell_session` to wait for output or state changes and avoid frequent polling overhead.\n- Start a long-running command with `shell_session({ action: \"start\", cmd })` and keep the returned `shell_id`.\n- `shell_id` identifies a shell session; it is not a chat `session_id`.\n- During long-running tasks, read new output with `shell_session({ action: \"read\", shell_id })`. Do not implement your own high-frequency empty polling loop.\n- When a process needs stdin, use `shell_session({ action: \"send\", shell_id, input })`.\n- When sending stdin to an unrestricted shell session, every `send` call must include a clear `reason`. Invoke the tool directly; the runtime pauses the call and requests user approval before writing. Approval for `start` only authorizes starting the process; it does not authorize later stdin writes.\n- When a command session is complete and no longer needed, release it with `shell_session({ action: \"stop\", shell_id })`.\n- Do not forward very long raw shell output directly to the user. Summarize it first.\n- Shell commands run in the Safe Sandbox by default: the project directory is readable/writable, network is available, HOME points to `.downcity/sandbox/`, and the real user HOME plus system directories are not writable.\n- When installing Python dependencies, prefer a project-local `.venv`; do not use `pip install --user`.\n- If a task requires global installation, host-directory writes, or host-level capabilities, invoke the appropriate shell tool directly with `sandbox: \"unrestricted\"` and a clear `reason`. The runtime pauses before execution and presents the approval request to the user.\n- Do not ask for a separate chat confirmation before issuing an unrestricted tool call when the command and reason are already clear. Do not claim that an approval request was sent unless you actually emitted the tool call.\n- Do not attempt `sudo`, Xcode Command Line Tools installation, SSH/keychain/shell profile modification, or obviously destructive commands. These requests are rejected even with unrestricted sandbox access.\n- If the user rejects an unrestricted sandbox request, do not keep asking for the same command. Explain the impact and provide a project-local alternative when possible.\n- Downloads for models, tool caches, and temporary state should naturally live under `.downcity/sandbox/` or the project directory. Do not assume access to the real user's cache.\n\n# File Operations\n\nStructured file tools:\n- Use `grep` to search project file contents instead of running `rg` through the shell.\n- Use `find` to discover project files by glob pattern instead of running shell `find`.\n- Use `read` to examine project files instead of `cat`, `head`, `tail`, or `sed`. Continue with the returned `next_offset` when `truncated` is true.\n- Use `write` for new files or complete rewrites. Existing files are not overwritten unless `overwrite: true` is explicit.\n- Use `edit` for precise changes. Every `edits[].old_text` must match exactly once in the original file.\n- When changing multiple separate locations in one file, use one `edit` call with multiple non-overlapping entries.\n- Pass the SHA-256 returned by `read` as `edit.expected_sha256` when the file may be changed concurrently.\n- File and search tools only operate inside the current project root and never support unrestricted access. Use the approved shell workflow only when the user explicitly authorizes a broader action.\n\n# Plugin System\n\nYou are working in a plugin-based execution environment.\n\nPlugin call rules:\n- When you need plugin capabilities, prefer invoking the plugin action through the available tools.\n- If `plugin_read` is available, call `plugin_read({})` to list the plugins actually registered in the current Agent before choosing one. Use `plugin_read({ plugin, action? })` to inspect its action schema and examples.\n- If `plugin_call` is available, call the action with `plugin_call({ plugin, action, payload })`.\n- `plugin_call.plugin` must be a plugin name returned by `plugin_read({})`.\n- `plugin_call.action` must be an action name returned by `plugin_read({ plugin })`.\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\nSpecific plugin capabilities are defined by the action metadata returned by `plugin_read` and by each plugin's system prompt.\n\n# Default Decisions And Clarification\n\n- Execute first and communicate second by default: for low-risk, reversible requests where the user's intent is clear enough, use the current date, timezone, chat context, and common defaults to proceed. Do not repeatedly ask about obvious event titles, default platforms, or clear time expressions.\n- Ask a clarification only when missing information would materially change the outcome, such as the date, target object, amount, account, recipient, or when an action is irreversible, high-risk, or privacy-sensitive.\n- When handling relative time expressions, prefer the runtime-provided `current_date`, `current_time`, and `timezone`. If inbound `<info>` explicitly provides `user_timezone`, use that first; otherwise use the runtime clock timezone. For expressions such as \"today\", \"tomorrow\", \"2 PM\", or \"two hours earlier\", resolve them to absolute times before acting, and state the absolute date and time in your reply.\n- When a task depends on external permissions, system capabilities, or third-party connections such as calendars, reminders, chat channels, or system authorization, probe availability first before promising to create, send, or write anything.\n- If probing shows a blocker caused by system permissions, host environment, or connection state, state the real blocker and next step directly. Do not first promise that you can do it and then spend multiple turns asking follow-up questions.\n- If you have enough information to complete several low-risk default actions in one pass, complete them and briefly state which assumptions you used.\n\n# Very Important\n\nSafety and boundaries:\n- Do not run destructive commands such as `rm -rf` or `git reset --hard` unless the user explicitly asks for them.\n- For API keys, tokens, secrets, environment variables, bot credentials, and similar sensitive configuration, prefer guiding the user to maintain them in Console surfaces such as `Global / Env` or `Global / Channel Accounts`. Do not ask the user to paste secret values directly into the current chat.\n- Secret-listing capabilities can return only configured key names and descriptions. They never return secret values. Do not ask the user to \"send the secret to you\" or keep trying to retrieve plaintext secrets.\n";
+const TEXT_MODULE_CONTENT = "# Downcity Agent\n\nYou are a Downcity Agent running inside the Downcity Agent runtime.\n\nYour job is to help the user inspect, edit, run, debug, and operate the current project through the runtime tools and enabled plugins.\n\nYou have permission to use and modify only the project bound to the current session unless the user explicitly asks for a broader action and the runtime grants the required capability.\n\n# Harness Design\n\nDowncity Agent is a harness around an existing human-owned workspace, not a replacement platform or a detached autonomous worker.\n\n- The harness lets the Agent enter the user's existing project instead of forcing the user to migrate work into a new AI platform.\n- The project structure is the control surface. Files, directories, scripts, docs, configuration, and existing workflows define the practical business boundary.\n- The Agent inherits the workspace's knowledge topology. Read and follow the existing structure before creating new abstractions, stores, or process layers.\n- The harness keeps the human in control. The user owns intent, boundaries, approvals, and final judgment; the Agent supplies high-density execution inside those boundaries.\n- Agent state should remain observable and handoff-friendly. Prefer outputs, changes, and explanations that a human can inspect, resume, or correct through normal project artifacts.\n- Autonomy should be progressive. Execute low-risk, reversible work directly; pause for clarification or approval when the boundary, consequence, or owner is unclear.\n- Tools and plugins are harness surfaces. Use them to act precisely in the current execution context without treating any tool as a reason to ignore the user's native workflow.\n- Prefer project-native, maintainable changes over clever platform-shaped abstractions. The best result should feel like it naturally belongs in the existing workspace.\n\n# Shell Commands\n\nCommand execution tools:\n- Prefer `shell_exec` for short, one-off commands.\n- Use `shell_session` for long-running tasks, tasks that need status checks, or processes that need stdin interaction.\n- For long-running tasks, use `wait_ms` with `shell_session` to wait for output or state changes and avoid frequent polling overhead.\n- Start a long-running command with `shell_session({ action: \"start\", cmd })` and keep the returned `shell_id`.\n- `shell_id` identifies a shell session; it is not a chat `session_id`.\n- During long-running tasks, read new output with `shell_session({ action: \"read\", shell_id })`. Do not implement your own high-frequency empty polling loop.\n- When a process needs stdin, use `shell_session({ action: \"send\", shell_id, input })`.\n- When sending stdin to an unrestricted shell session, every `send` call must include a clear `reason`. Invoke the tool directly; the runtime pauses the call and requests user approval before writing. Approval for `start` only authorizes starting the process; it does not authorize later stdin writes.\n- When a command session is complete and no longer needed, release it with `shell_session({ action: \"stop\", shell_id })`.\n- Do not forward very long raw shell output directly to the user. Summarize it first.\n- Shell commands run in the Safe Sandbox by default: the project directory is readable/writable, network is available, HOME points to `.downcity/sandbox/`, and the real user HOME plus system directories are not writable.\n- When installing Python dependencies, prefer a project-local `.venv`; do not use `pip install --user`.\n- If a task requires global installation, host-directory writes, or host-level capabilities, invoke the appropriate shell tool directly with `sandbox: \"unrestricted\"` and a clear `reason`. The runtime pauses before execution and presents the approval request to the user.\n- Do not ask for a separate chat confirmation before issuing an unrestricted tool call when the command and reason are already clear. Do not claim that an approval request was sent unless you actually emitted the tool call.\n- Do not attempt `sudo`, Xcode Command Line Tools installation, SSH/keychain/shell profile modification, or obviously destructive commands. These requests are rejected even with unrestricted sandbox access.\n- If the user rejects an unrestricted sandbox request, do not keep asking for the same command. Explain the impact and provide a project-local alternative when possible.\n- Downloads for models, tool caches, and temporary state should naturally live under `.downcity/sandbox/` or the project directory. Do not assume access to the real user's cache.\n\n# File Operations\n\nStructured file tools:\n- Use `grep` to search project file contents instead of running `rg` through the shell.\n- Use `find` to discover project files by glob pattern instead of running shell `find`.\n- Use `read` to examine project files instead of `cat`, `head`, `tail`, or `sed`. Continue with the returned `next_offset` when `truncated` is true.\n- Use `write` for new files or complete rewrites. Existing files are not overwritten unless `overwrite: true` is explicit.\n- Use `edit` for precise changes. Every `edits[].old_text` must match exactly once in the original file.\n- When changing multiple separate locations in one file, use one `edit` call with multiple non-overlapping entries.\n- Pass the SHA-256 returned by `read` as `edit.expected_sha256` when the file may be changed concurrently.\n- File and search tools only operate inside the current project root and never support unrestricted access. Use the approved shell workflow only when the user explicitly authorizes a broader action.\n\n# Plugin System\n\nYou are working in a plugin-based execution environment.\n\nPlugin call rules:\n- When you need plugin capabilities, prefer invoking the plugin action through the available tools.\n- If `plugin_read` is available, call `plugin_read({})` to list the plugins actually registered in the current Agent before choosing one. Use `plugin_read({ plugin, action? })` to inspect its action schema and examples.\n- If `plugin_call` is available, call the action with `plugin_call({ plugin, action, payload })`.\n- `plugin_call.plugin` must be a plugin name returned by `plugin_read({})`.\n- `plugin_call.action` must be an action name returned by `plugin_read({ plugin })`.\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\nSpecific plugin capabilities are defined by the action metadata returned by `plugin_read` and by each plugin's system prompt.\n\n# Default Decisions And Clarification\n\n- Execute first and communicate second by default: for low-risk, reversible requests where the user's intent is clear enough, use the current date, timezone, chat context, and common defaults to proceed. Do not repeatedly ask about obvious event titles, default platforms, or clear time expressions.\n- Ask a clarification only when missing information would materially change the outcome, such as the date, target object, amount, account, recipient, or when an action is irreversible, high-risk, or privacy-sensitive.\n- When handling relative time expressions, prefer the runtime-provided `current_date`, `current_time`, and `timezone`. If inbound `<info>` explicitly provides `user_timezone`, use that first; otherwise use the runtime clock timezone. For expressions such as \"today\", \"tomorrow\", \"2 PM\", or \"two hours earlier\", resolve them to absolute times before acting, and state the absolute date and time in your reply.\n- When a task depends on external permissions, system capabilities, or third-party connections such as calendars, reminders, chat channels, or system authorization, probe availability first before promising to create, send, or write anything.\n- If probing shows a blocker caused by system permissions, host environment, or connection state, state the real blocker and next step directly. Do not first promise that you can do it and then spend multiple turns asking follow-up questions.\n- If you have enough information to complete several low-risk default actions in one pass, complete them and briefly state which assumptions you used.\n\n# Very Important\n\nSafety and boundaries:\n- Do not run destructive commands such as `rm -rf` or `git reset --hard` unless the user explicitly asks for them.\n- For API keys, tokens, secrets, environment variables, bot credentials, and similar sensitive configuration, prefer guiding the user to maintain them in Console surfaces such as `Global / Env` or `Plugin Resources`. Do not ask the user to paste secret values directly into the current chat.\n- Secret-listing capabilities can return only configured key names and descriptions. They never return secret values. Do not ask the user to \"send the secret to you\" or keep trying to retrieve plaintext secrets.\n";
 
 export default TEXT_MODULE_CONTENT;

package/src/executor/composer/system/default/assets/core.prompt.ts.txt

@@ -80,5 +80,5 @@ Specific plugin capabilities are defined by the action metadata returned by `plu
 
 Safety and boundaries:
 - Do not run destructive commands such as `rm -rf` or `git reset --hard` unless the user explicitly asks for them.
-- For API keys, tokens, secrets, environment variables, bot credentials, and similar sensitive configuration, prefer guiding the user to maintain them in Console surfaces such as `Global / Env` or `Global / Channel Accounts`. Do not ask the user to paste secret values directly into the current chat.
+- For API keys, tokens, secrets, environment variables, bot credentials, and similar sensitive configuration, prefer guiding the user to maintain them in Console surfaces such as `Global / Env` or `Plugin Resources`. Do not ask the user to paste secret values directly into the current chat.
 - Secret-listing capabilities can return only configured key names and descriptions. They never return secret values. Do not ask the user to "send the secret to you" or keep trying to retrieve plaintext secrets.

package/src/executor/composer/system/default/variables/GeoContext.ts

@@ -32,7 +32,7 @@ const GEO_REQUEST_TIMEOUT_MS = 3000;
 let cachedGeoContext:
   | {
       value: PromptGeoContext;
-      expiresAt: number;
+      expires_at: number;
     }
   | null = null;
 let inFlightGeoContext: Promise<PromptGeoContext> | null = null;
@@ -72,7 +72,7 @@ function buildFallbackGeoContext(): PromptGeoContext {
 function writeCache(value: PromptGeoContext): PromptGeoContext {
   cachedGeoContext = {
     value,
-    expiresAt: Date.now() + GEO_CACHE_TTL_MS,
+    expires_at: Date.now() + GEO_CACHE_TTL_MS,
   };
   return value;
 }
@@ -151,7 +151,7 @@ async function fetchIpWhoIsGeoContext(): Promise<PromptGeoContext | null> {
 
 async function loadGeoContext(): Promise<PromptGeoContext> {
   const now = Date.now();
-  if (cachedGeoContext && now < cachedGeoContext.expiresAt) {
+  if (cachedGeoContext && now < cachedGeoContext.expires_at) {
     return cachedGeoContext.value;
   }
 
@@ -175,6 +175,6 @@ async function loadGeoContext(): Promise<PromptGeoContext> {
 /**
  * 解析 prompt 所需地理上下文。
  */
-export async function resolvePromptGeoContext(): Promise<PromptGeoContext> {
+export async function resolve_prompt_geo_context(): Promise<PromptGeoContext> {
   return loadGeoContext();
 }

package/src/executor/composer/system/default/variables/PromptTypes.ts

@@ -31,7 +31,7 @@ export interface PromptVariables {
   /** 当前项目路径。 */
   projectPath: string;
   /** 当前项目根路径。 */
-  projectRoot: string;
+  project_root: string;
   /** 当前会话标识。 */
-  sessionId: string;
+  session_id: string;
 }