u1s1-cli 0.16.5 → 0.17.0

package/dist/agent-setup.d.ts

@@ -58,6 +58,11 @@ export declare function toProviderModels(models: ModelDef[]): {
  * 这是 pi 自带 llama provider 的同款兜底,本地服务会忽略 Authorization 头。
  */
 export declare function endpointProviderEntry(ep: CustomEndpoint): Record<string, unknown>;
+/**
+ * 生成 /workflow 提示词模板到 <agentDir>/prompts/workflow.md:引导主 agent
+ * 拆解任务 → 生成沙箱脚本 → 调 run_workflow 执行。每次启动重写,便于随版迭代文案。
+ */
+export declare function ensureWorkflowPromptTemplate(): void;
 export declare function scrubForeignProviderEnv(): void;
 /** 把各端点密钥放进环境(TUI 直接 process.env;web 传给子进程)。 */
 export declare function endpointKeyEnv(): Record<string, string>;

package/dist/agent-setup.js

@@ -139,6 +139,19 @@ export function writeWebToolsExtension(cfg, features) {
     const imageLine = features.imageGen
         ? `  pi.registerTool(tools.createImageTool({ baseUrl: ${JSON.stringify(cfg.baseUrl)}, apiKey: process.env.U1S1_API_KEY }));\n`
         : "";
+    // spawn_subagent / run_workflow 只给主会话注册;子 agent 环境里跳过,杜绝孙 agent 递归 spawn
+    const subagentBlock = `  if (process.env.U1S1_IN_SUBAGENT !== "1") {\n` +
+        `    let getParentModel = () => undefined;\n` +
+        `    pi.on("session_start", (_event, ctx) => {\n` +
+        `      const m = ctx.model;\n` +
+        `      if (m && typeof m.provider === "string" && typeof m.id === "string") {\n` +
+        `        getParentModel = () => ({ provider: m.provider, id: m.id });\n` +
+        `      }\n` +
+        `    });\n` +
+        `    pi.registerTool(tools.createSubagentTool(getParentModel));\n` +
+        `    const workflow = await import(${JSON.stringify(new URL("./workflow/tool.js", import.meta.url).href)});\n` +
+        `    pi.registerTool(workflow.createRunWorkflowTool(getParentModel));\n` +
+        `  }\n`;
     writeFileSync(join(dir, "u1s1-tools.js"), `// 由 u1s1 每次启动自动生成,请勿手改\n` +
         `export default async function (pi) {\n` +
         `  if (process.env.U1S1_TOOLS_VIA_EXTENSION !== "1") return;\n` +
@@ -146,6 +159,7 @@ export function writeWebToolsExtension(cfg, features) {
         searchLine +
         `  pi.registerTool(tools.createFetchTool({ baseUrl: ${JSON.stringify(cfg.baseUrl)}, apiKey: process.env.U1S1_API_KEY, renderFallback: ${features.webFetchRender} }));\n` +
         imageLine +
+        subagentBlock +
         `}\n`);
 }
 /**
@@ -297,6 +311,39 @@ export function endpointProviderEntry(ep) {
         models: toProviderModels(ep.models),
     };
 }
+/**
+ * 生成 /workflow 提示词模板到 <agentDir>/prompts/workflow.md:引导主 agent
+ * 拆解任务 → 生成沙箱脚本 → 调 run_workflow 执行。每次启动重写,便于随版迭代文案。
+ */
+export function ensureWorkflowPromptTemplate() {
+    const dir = join(agentDir, "prompts");
+    mkdirSync(dir, { recursive: true });
+    const content = `---
+description: Orchestrate many sub-agents for a large parallelizable task via run_workflow
+argument-hint: "<task description>"
+---
+# Workflow: $ARGUMENTS
+
+First decide whether this task really needs a workflow. Good fit: many independent pieces (e.g. translating each locale file, renaming across hundreds of files, reviewing many modules). Bad fit: a few small edits — just do them directly with your own tools.
+
+If it is a fit:
+
+1. Decompose the task, then write a JavaScript orchestration script. Top-level await and return are allowed. The script runs in a sandbox where ONLY these are available:
+   - \`subagent(task)\` or \`subagent({ task, model })\` — runs one sub-agent, resolves to its final output text
+   - \`parallel([() => ..., ...])\` — concurrent fan-out; each thunk's error becomes \`null\`; barrier semantics
+   - \`pipeline(items, [stage1, stage2, ...])\` — each item flows through all stages independently (prefer over parallel)
+   - \`log(...)\`, \`setTimeout/clearTimeout\`, standard JS builtins (Promise/JSON/Math/...)
+   - NO require/import/process/fetch/fs access — the static validator rejects scripts that try
+2. Every task string must be fully self-contained: which files to read/write, what "done" means, how to self-verify.
+3. Call the \`run_workflow\` tool with the full source as \`script\`. Read its report carefully; on failures fix the script, or rerun with \`script_path\` + \`resume: true\` to continue from saved progress.
+
+Keep scripts deterministic (same order of subagent calls every run) so resume works. Summarize the outcome to the user afterwards in their language.
+`;
+    const p = join(dir, "workflow.md");
+    if (!existsSync(p) || readFileSync(p, "utf8") !== content) {
+        writeFileSync(p, content);
+    }
+}
 /**
  * pi 会把环境里的厂商密钥(ANTHROPIC_API_KEY 等)当作「已配置的 provider」,
  * /model 里冒出一大串没在用的模型(u1s1 又拦了 /login,配了也没法管理)。

package/dist/api.d.ts

@@ -43,6 +43,11 @@ export interface ApiModel {
         cache_read: number | null;
     };
 }
+/** 启动横幅公告(后台「全局设置」下发);url 可选。老网关没有该字段,undefined = 不显示。 */
+export interface ApiAnnouncement {
+    text: string;
+    url?: string;
+}
 /** 服务端能力开关;字段缺失(老网关)时按开启处理,保持现状。 */
 export interface ApiFeatures {
     web_search?: boolean;
@@ -54,6 +59,7 @@ export interface ApiFeatures {
 export interface ModelsResponse {
     models: ApiModel[];
     features: ApiFeatures;
+    announcement?: ApiAnnouncement | null;
 }
 export declare function fetchModels(cfg: CliConfig): Promise<ModelsResponse>;
 export interface ApiEndpoint {

package/dist/api.js

@@ -18,7 +18,7 @@ export async function fetchModels(cfg) {
     if (!resp.ok)
         throw new Error(`服务端返回 ${resp.status},稍后再试`);
     const body = (await resp.json());
-    return { models: body.data, features: body.features ?? {} };
+    return { models: body.data, features: body.features ?? {}, announcement: body.announcement };
 }
 /**
  * 拉取用户在云端配置的自定义模型端点(dashboard「自定义模型端点」卡片)。