c0de-agent 1.5.0 → 1.6.0

package/dist/core/agent.js

@@ -2,6 +2,7 @@ import { appendMessage, getMessages } from '../session/message.js';
 import { getLLMSegments } from '../session/session.js';
 import { generateId } from '../shared/index.js';
 import { listTools } from '../tools/registry.js';
+import { getLatestTodoPhasesFromMessages } from '../tools/builtin/todo.js';
 import { estimateBudget } from './context.js';
 import { createTokenBudget } from './context.js';
 import { agentLoop } from './loop.js';
@@ -39,6 +40,9 @@ async function createAgent(session, config, deps) {
         segments,
         tokenBudget: { ...tokenBudget, used },
         calibrationFactor: 1.0,
+        // 从历史 tool result 恢复 todo 状态（跨 session resume / compaction 后重建）。
+        // 遍历所有消息找最后一条带 phases metadata 的 todo result。
+        todoPhases: getLatestTodoPhasesFromMessages(messages),
         // 压缩模型覆盖：从全局配置映射到 agent state，compactContext 读取后用于
         // 创建 summarizer。未配置时为 undefined → 回退到会话主模型。
         ...(deps.config.compaction.compactionModel

package/dist/core/config.js

@@ -16,7 +16,7 @@ const DEFAULT_CONFIG = {
         keepRecentTokens: 4000,
         midTurnEnabled: false,
     },
-    tools: { enabled: ['read', 'write', 'edit', 'glob', 'grep', 'bash', 'websearch'], disabled: [] },
+    tools: { enabled: ['read', 'write', 'edit', 'glob', 'grep', 'bash', 'todo', 'websearch'], disabled: [] },
     plugins: { enabled: [] },
     mcpServers: [],
     slashCommands: { enabled: ['/compact', '/model', '/clear', '/help', '/fork', '/config'] },

package/dist/core/index.d.ts

@@ -10,7 +10,7 @@ export { builtinCommands, createSlashRegistry, parseSlashInput } from './slash.j
 export { clearSteering, drainSteering, injectSteering } from './steering.js';
 export type { CollectedToolCall, ToolCallResult } from './tool-exec.js';
 export { executeToolCall, executeToolCalls, partitionByConflict } from './tool-exec.js';
-export type { AgentConfig, AgentDependencies, AgentError, AgentEvent, AgentState, AgentStatus, CommandContext, CommandResult, LLMSegment, PendingToolCall, ProjectInfo, PromptContext, SlashCommand, TokenBudget, } from './types.js';
+export type { AgentConfig, AgentDependencies, AgentError, AgentEvent, AgentState, AgentStatus, CommandContext, CommandResult, LLMSegment, PendingToolCall, ProjectInfo, PromptContext, SlashCommand, SubcommandDef, TokenBudget, } from './types.js';
 export { buildWorkflowNotice, containsWorkflow, WORKFLOW_NOTICE } from './workflow.js';
 export type { SaveResult, SaveTarget, WorkflowAgentResult, WorkflowContext, WorkflowEntry, WorkflowMeta, WorkflowRegistry, WorkflowResult, WorkflowUtils, } from './workflows/index.js';
 export { BUILTIN_WORKFLOWS, buildWorkflowContext, createAndPopulateRegistry, createBuiltinWorkflows, createWorkflowRegistry, discoverWorkflows, executeWorkflow, reloadRegistry, saveWorkflow, } from './workflows/index.js';

package/dist/core/loop.js

@@ -598,6 +598,15 @@ async function* persistAssistantAndTools(state, deps, collectedText, validCalls)
             ...(deps.debugSpawn ? { debugSpawn: deps.debugSpawn } : {}),
             runSubAgent: (req) => runSubAgent({ ...deps, _subagentEventSink: eventSink }, state, req),
             ...(deps._subagentYieldCollector ? { collectYield: deps._subagentYieldCollector } : {}),
+            // todo 工具状态通过 dependency-reversal hook 注入：get/set 直接读写
+            // state.todoPhases（in-memory），tool result 的 metadata.phases 充当
+            // 持久化层——createAgent 时从历史消息恢复。
+            todoState: {
+                get: () => state.todoPhases,
+                set: (phases) => {
+                    state.todoPhases = phases;
+                },
+            },
         }, validCalls, deps.hookRunner);
         const toolLatency = Date.now() - toolExecStart;
         const metricsEnabled = deps.config.toolMetrics.enabled;

package/dist/core/prompt-registry.d.ts

@@ -3,14 +3,14 @@ declare const ROLE_DESCRIPTION = "You are c0de-agent, an open-source AI coding a
 declare const ENGINEERING_PRINCIPLES = "# Engineering Principles\n- Optimize for correctness first, then for the next maintainer six months out.\n- You have agency and taste: delete code that isn't pulling its weight, refuse unnecessary abstractions, prefer boring when it's called for.\n- Consider what code compiles to. Never allocate avoidably; no needless copies or computation.\n- You are not alone in this repo. Treat unexpected changes as the user's work and adapt \u2014 never revert edits you did not make unless explicitly asked.";
 declare const TOOL_USAGE = "# Tool Usage\nYou have dedicated tools \u2014 prefer them over shell commands for file operations:\n- Reading a file or listing a directory \u2192 `read` (NOT `cat`, `head`, `tail`).\n- Finding files by name or pattern \u2192 `glob` (NOT `find`, `ls -R`).\n- Searching file contents \u2192 `grep` (NOT shell `grep`/`rg`/`ack`, NOT `awk`/`sed`).\n- Modifying files \u2192 `edit`/`write` (NOT `sed`, `echo >`, heredocs).\n\nReserve `bash` for genuine command execution: builds, tests, git, or short pipelines that compute a fact (`wc -l`, `git status`, `diff`, a checksum). Never explore a codebase with `find`/`ls`/`cat` when `read`/`glob`/`grep` can.\n\nBatch independent tool calls in a single response \u2014 parallelize file reads and independent lookups. Only sequence when one call's result informs the next.\n\nWhen referencing code, use the `file_path:line_number` pattern so the user can navigate directly.";
 declare const CODEBASE = "# Working with the Codebase\nBefore changing files, understand the existing conventions. Mimic code style, reuse existing utilities, and follow established patterns.\n- NEVER assume a library is available, even if well known. Check package.json (or equivalent) and neighboring files first.\n- When creating a new component, look at existing ones first for naming, typing, and framework conventions.\n- When editing, read the surrounding context (especially imports) to make the change idiomatic. Never introduce code that exposes or logs secrets.";
-declare const EXECUTION_WORKFLOW = "# Execution Workflow\n1. Scope \u2014 plan before touching files; research existing code and conventions.\n2. Research \u2014 read sections, not snippets. Reuse existing patterns; a second convention beside an existing one is prohibited.\n3. Decompose \u2014 break multi-step work into steps and track them; skip for trivial requests. Plan only what makes the request work.\n4. Implement \u2014 fix problems at the source. Remove obsolete code \u2014 no leftover comments, aliases, or re-exports. Prefer editing existing files over new ones.\n5. Verify \u2014 never yield non-trivial work without proof: run the relevant tests. Prefer testing behavior, not plumbing. Don't test defaults.\n6. Cleanup \u2014 changelog, tests, docs, and removing scaffolding are the LAST phase, gated on the request demonstrably working. Never pre-plan cleanup before the request works.";
+declare const EXECUTION_WORKFLOW = "# Execution Workflow\n1. Scope \u2014 plan before touching files; research existing code and conventions.\n2. Research \u2014 read sections, not snippets. Reuse existing patterns; a second convention beside an existing one is prohibited.\n3. Decompose \u2014 break multi-step work into steps and track them with the `todo` tool; skip for trivial requests. Plan only what makes the request work.\n4. Implement \u2014 fix problems at the source. Remove obsolete code \u2014 no leftover comments, aliases, or re-exports. Prefer editing existing files over new ones.\n5. Verify \u2014 never yield non-trivial work without proof: run the relevant tests. Prefer testing behavior, not plumbing. Don't test defaults.\n6. Cleanup \u2014 changelog, tests, docs, and removing scaffolding are the LAST phase, gated on the request demonstrably working. Never pre-plan cleanup before the request works.";
 declare const VERIFICATION = "# Verification & Evidence\n- Never yield non-trivial work without proof: tests, builds, or QA.\n- Run lint and typecheck after changes if the project provides them.\n- Every claim about code, tools, or tests must be grounded. Mark anything not directly observed as [INFERENCE].\n- Verification claims must match what was actually exercised. A passing typecheck does not prove an integration.";
 declare const DELIVERY_CONTRACT = "# Delivery Contract\n- \"Done\" means the deliverable behaves as specified end-to-end \u2014 not that a scaffold compiles.\n- Never yield unless complete. A phase boundary is never a yield point.\n- Never suppress tests to make code pass. Never fabricate outputs.\n- Never substitute an easier problem: don't infer extra scope, don't treat the symptom unless asked.\n- Never ship stubs, placeholders, mocks, no-ops, or fake fallbacks as finished work.\n- Default to clean cutover: migrate every caller; leave no shims or aliases.";
 declare const GIT_SAFETY = "# Git & Safety\n- NEVER commit unless the user explicitly asks. Committing is too proactive.\n- NEVER use `git reset --hard` or `git checkout --` unless explicitly approved.\n- Do not amend a commit unless asked.\n- You may be in a dirty worktree. NEVER revert changes you did not make; if unrelated changes conflict with your task, stop and ask.";
 declare const TONE = "# Tone & Output\n- Be concise and direct. Lead with the conclusion, then the evidence.\n- No preamble or postamble (\"The answer is\u2026\", \"Here is what I'll do next\u2026\").\n- Use GitHub-flavored markdown. Only use emojis if explicitly asked.\n- Don't hide uncertainty: state it at the specific claim, name the tradeoff.\n- For a simple question, a one-liner is best.";
 export { CODEBASE, DELIVERY_CONTRACT, ENGINEERING_PRINCIPLES, EXECUTION_WORKFLOW, GIT_SAFETY, ROLE_DESCRIPTION, TONE, TOOL_USAGE, VERIFICATION, };
 /** Built-in section ids in priority order. */
-export declare const BUILTIN_SECTION_IDS: readonly ["role", "systemPrompt", "engineering", "tool-usage", "codebase", "constraints", "execution-workflow", "verification", "delivery-contract", "git-safety", "tone", "project", "skills", "agents", "slash-commands"];
+export declare const BUILTIN_SECTION_IDS: readonly ["role", "systemPrompt", "engineering", "tool-usage", "codebase", "constraints", "execution-workflow", "verification", "delivery-contract", "git-safety", "tone", "project", "skills", "agents", "slash-commands", "workflow-format"];
 /** Create a registry pre-loaded with the built-in sections. */
 declare function createPromptRegistry(): PromptRegistry;
 /** Register a section. A later registration with the same id overrides the earlier

package/dist/core/prompt-registry.js

@@ -37,7 +37,7 @@ This project follows a strict data + functions paradigm:
 const EXECUTION_WORKFLOW = `# Execution Workflow
 1. Scope — plan before touching files; research existing code and conventions.
 2. Research — read sections, not snippets. Reuse existing patterns; a second convention beside an existing one is prohibited.
-3. Decompose — break multi-step work into steps and track them; skip for trivial requests. Plan only what makes the request work.
+3. Decompose — break multi-step work into steps and track them with the \`todo\` tool; skip for trivial requests. Plan only what makes the request work.
 4. Implement — fix problems at the source. Remove obsolete code — no leftover comments, aliases, or re-exports. Prefer editing existing files over new ones.
 5. Verify — never yield non-trivial work without proof: run the relevant tests. Prefer testing behavior, not plumbing. Don't test defaults.
 6. Cleanup — changelog, tests, docs, and removing scaffolding are the LAST phase, gated on the request demonstrably working. Never pre-plan cleanup before the request works.`;
@@ -83,6 +83,7 @@ export const BUILTIN_SECTION_IDS = [
     'skills',
     'agents',
     'slash-commands',
+    'workflow-format',
 ];
 /** Built-in sections. Dynamic bodies (tool list, project info, skills) use `render`. */
 function builtinSections() {
@@ -164,8 +165,46 @@ function builtinSections() {
             priority: 120,
             render: () => {
                 const lines = ['## Slash Commands'];
-                for (const cmd of builtinCommands)
-                    lines.push(`- /${cmd.name}: ${cmd.description}`);
+                for (const cmd of builtinCommands) {
+                    let line = `- /${cmd.name}: ${cmd.description}`;
+                    if (cmd.subcommands) {
+                        const subs = cmd.subcommands.map((s) => s.name).join('|');
+                        line += ` (${subs})`;
+                    }
+                    lines.push(line);
+                }
+                return lines.join('\n');
+            },
+        },
+        // 工作流脚本格式提示：让模型知道工作流脚本是 JS 格式，放在 .c0de/workflows/。
+        {
+            id: 'workflow-format',
+            content: '',
+            priority: 121,
+            render: () => {
+                const lines = [
+                    '## Dynamic Workflows',
+                    'When the user asks to create/save a workflow (e.g. "workflowz 创建工作流"), you MUST generate a **JavaScript** file (NOT bash/shell/python) with this structure:',
+                    '```js',
+                    '// File: .c0de/workflows/<name>.js',
+                    'export const meta = {',
+                    "  name: '<name>',           // lowercase, kebab-case",
+                    "  description: '<description>',",
+                    "  phases: ['phase1', 'phase2'],",
+                    '}',
+                    '',
+                    'export default async function workflow(ctx) {',
+                    '  const { runSubagents, runSubagent, utils, progress, project, args } = ctx',
+                    '  // runSubagents(type, tasks[]) → parallel fan-out',
+                    '  // runSubagent(type, { assignment, description? }) → single dispatch',
+                    '  // utils: { glob, grep, read, splitByDirectory }',
+                    '  // progress(message, { phase? }) → SSE progress',
+                    "  return { output: 'summary', data: {} }",
+                    '}',
+                    '```',
+                    'Save to `<project>/.c0de/workflows/<name>.js`. Available subagent types: general, coder, researcher, reviewer.',
+                    'Run with `/workflow run <name>` or POST /api/workflows/:name/run. NEVER create bash/shell scripts for workflows.',
+                ];
                 return lines.join('\n');
             },
         },

package/dist/core/slash.js

@@ -1,6 +1,6 @@
 import { createSession } from '../session/session.js';
 import { createAgent } from './agent.js';
-import { BUILTIN_WORKFLOWS, createWorkflowRegistry, executeWorkflow, reloadRegistry, saveWorkflow, } from './workflows/index.js';
+import { BUILTIN_WORKFLOWS, createWorkflowRegistry, discoverWorkflows, executeWorkflow, reloadRegistry, saveWorkflow, } from './workflows/index.js';
 function parseSlashInput(input) {
     const trimmed = input.trim();
     if (!trimmed.startsWith('/'))
@@ -110,6 +110,13 @@ const workflowCommand = {
     name: 'workflow',
     description: 'Manage and run workflows',
     argsHint: '[list|run|show|create|edit] [name] [args]',
+    subcommands: [
+        { name: 'list', description: 'List available workflows' },
+        { name: 'run', description: 'Run a workflow', usage: '<name> [args]' },
+        { name: 'show', description: 'Show workflow source', usage: '<name>' },
+        { name: 'create', description: 'Create a workflow from file', usage: '<name> --file <path>' },
+        { name: 'edit', description: 'Edit workflow source', usage: '<name>' },
+    ],
     execute: async (args, ctx) => {
         const parts = args.split(/\s+/).filter(Boolean);
         const subcommand = parts[0] ?? 'list';
@@ -121,8 +128,17 @@ const workflowCommand = {
                 registry.register(wf);
             }
         }
+        // 项目级工作流：从 agent cwd（= project worktree）动态发现。
+        // registry 是 server 单例（含 builtin + global + server-cwd），不含其他项目的工作流。
+        const projectWorkflows = await discoverWorkflows(ctx.cwd);
+        const projectByName = new Map(projectWorkflows.map((w) => [w.meta.name, w]));
+        const resolveEntry = (name) => registry.get(name) ?? projectByName.get(name);
         if (subcommand === 'list') {
-            const workflows = registry.list();
+            // 合并 registry + 项目级（去重：同名项目级覆盖）
+            const byName = new Map(registry.list().map((w) => [w.meta.name, w]));
+            for (const wf of projectWorkflows)
+                byName.set(wf.meta.name, wf);
+            const workflows = Array.from(byName.values());
             const lines = ['Available workflows:'];
             for (const wf of workflows) {
                 const phases = wf.meta.phases ? ` [${wf.meta.phases.join('→')}]` : '';
@@ -140,7 +156,7 @@ const workflowCommand = {
             const name = parts[1];
             if (!name)
                 return { _tag: 'error', message: 'Usage: /workflow show <name>' };
-            const wf = registry.get(name);
+            const wf = resolveEntry(name);
             if (!wf) {
                 return { _tag: 'error', message: `Unknown workflow: ${name}` };
             }
@@ -157,7 +173,10 @@ const workflowCommand = {
             // 解析 --file <path> 参数
             const fileIdx = parts.indexOf('--file');
             if (fileIdx === -1 || !parts[fileIdx + 1]) {
-                return { _tag: 'error', message: 'Usage: /workflow create <name> --file <path>\nTip: 也可通过 REST API POST /api/workflows { name, source } 创建' };
+                return {
+                    _tag: 'error',
+                    message: 'Usage: /workflow create <name> --file <path>\nTip: 也可通过 REST API POST /api/workflows { name, source } 创建',
+                };
             }
             const filePath = parts[fileIdx + 1] ?? '';
             let source;
@@ -184,12 +203,15 @@ const workflowCommand = {
             const name = parts[1];
             if (!name)
                 return { _tag: 'error', message: 'Usage: /workflow edit <name>' };
-            const wf = registry.get(name);
+            const wf = resolveEntry(name);
             if (!wf) {
                 return { _tag: 'error', message: `Unknown workflow: ${name}` };
             }
             if (wf.source === 'builtin') {
-                return { _tag: 'error', message: 'Cannot edit builtin workflow. Fork it first: /workflow create <new-name> --file <path>' };
+                return {
+                    _tag: 'error',
+                    message: 'Cannot edit builtin workflow. Fork it first: /workflow create <new-name> --file <path>',
+                };
             }
             if (!wf.filePath) {
                 return { _tag: 'error', message: `Workflow file path not available for "${name}"` };
@@ -213,6 +235,17 @@ const workflowCommand = {
             if (!name)
                 return { _tag: 'error', message: 'Usage: /workflow run <name> [args]' };
             const wfArgs = parts.slice(2).join(' ');
+            const entry = resolveEntry(name);
+            if (!entry) {
+                const available = [
+                    ...registry.list().map((e) => e.meta.name),
+                    ...projectWorkflows.map((e) => e.meta.name),
+                ].join(', ');
+                return {
+                    _tag: 'error',
+                    message: `Unknown workflow: "${name}". Available: ${available || '(none)'}`,
+                };
+            }
             const agentConfig = {
                 provider: ctx.config.defaultProvider,
                 model: ctx.config.defaultModel,
@@ -225,6 +258,7 @@ const workflowCommand = {
             return executeWorkflow({
                 registry,
                 name,
+                entry,
                 args: wfArgs,
                 deps: ctx.deps,
                 parent,

package/dist/core/types.d.ts

@@ -89,10 +89,19 @@ type CommandContext = {
     deps: AgentDependencies;
     workflowRegistry?: import('./workflows/registry.js').WorkflowRegistry;
 };
+/** Declarative subcommand definition for commands like /workflow. */
+type SubcommandDef = {
+    name: string;
+    description: string;
+    /** Usage hint shown in popover, e.g. "<name> [args]". */
+    usage?: string;
+};
 type SlashCommand = {
     name: string;
     description: string;
     argsHint?: string;
+    /** Subcommands for dropdown completion (e.g. /workflow list, /workflow run). */
+    subcommands?: SubcommandDef[];
     execute: (args: string, ctx: CommandContext) => Promise<CommandResult>;
 };
-export type { AgentConfig, AgentDependencies, AgentError, AgentEvent, AgentState, AgentStatus, ChatTool, CommandContext, CommandResult, HookRunner, LLMSegment, PendingToolCall, ProjectInfo, PromptBuildContext, PromptContext, PromptRegistry, PromptSection, SlashCommand, TokenBudget, };
+export type { AgentConfig, AgentDependencies, AgentError, AgentEvent, AgentState, AgentStatus, ChatTool, CommandContext, CommandResult, HookRunner, LLMSegment, PendingToolCall, ProjectInfo, PromptBuildContext, PromptContext, PromptRegistry, PromptSection, SlashCommand, SubcommandDef, TokenBudget, };

package/dist/core/workflow.d.ts

@@ -25,7 +25,7 @@ export declare function containsWorkflow(text: string): boolean;
  *
  * 适配 c0de-agent 的 task 工具 schema（subagent_type + context + tasks[]）。
  */
-export declare const WORKFLOW_NOTICE = "<workflow-notice>\nThe user's message contains the **workflowz** keyword: you MUST drive this task as a deterministic multi-subagent workflow using the `task` tool for batched fan-out. This is not optional \u2014 the keyword signals the user explicitly wants parallel sub-agent decomposition, not inline work. This overrides any default tendency to do the whole task inline.\n\n<when>\nThe user typed workflowz intentionally \u2014 they want fan-out. You may do a brief inline scout (1-2 tool calls to list files/scope the work), but your NEXT action after scouting MUST be a `task` tool call to fan out. Do NOT spend the entire turn reading files inline \u2014 that defeats the purpose. Common shapes:\n- **Understand** \u2014 parallel readers over subsystems \u2192 structured map.\n- **Design** \u2014 independent approaches \u2192 scored synthesis.\n- **Review** \u2014 split dimensions \u2192 find per dimension \u2192 adversarially verify each finding.\n- **Research** \u2014 multi-modal sweep \u2192 deep-read the hits \u2192 synthesize.\n- **Migrate** \u2014 discover sites \u2192 transform each \u2192 verify.\n</when>\n\n<task-contract>\nCall `task` once per independent fan-out batch using the batch form:\n\n    task({\n      subagent_type: \"coder\",\n      context: \"shared background all subagents need\",\n      tasks: [\n        { role: \"coder\", assignment: \"specific assignment for agent 1\", description: \"short label\" },\n        { role: \"reviewer\", assignment: \"specific assignment for agent 2\", description: \"short label\" },\n      ]\n    })\n\nAvailable subagent types: `general` (full tools, recursive), `coder` (implementation), `researcher` (read-only scout), `reviewer` (code review). Pick the type that matches each task's intent.\n\n`context` carries shared background prepended to every subagent's prompt \u2014 put the shared contract, conventions, and coordination rules here.\n\nEach task in `tasks[]` must be self-contained:\n- `role`: specialist type for this sub-task (e.g. coder, reviewer, researcher)\n- `assignment`: exact target (files, symbols, subsystem) + what to do + acceptance criteria\n- `description`: short label for the UI\n\nEach subagent runs in an isolated session and returns its result via the `yield` tool. Subagents skip formatters, linters, and project-wide tests \u2014 the parent runs shared proof once after all results return.\n</task-contract>\n\n<structure>\nDecompose first, then batch the independent leaves:\n\n    task({\n      subagent_type: \"coder\",\n      context: \"# Goal\nImplement feature X across the codebase\n# Constraints\nFollow existing patterns...\n# Contract\nReturn findings as structured data...\",\n      tasks: [\n        { role: \"coder\", assignment: \"# Target\nsrc/auth/login.ts\n# Change\nAdd rate limiting to login endpoint\n# Acceptance\nRate limiter works, tests pass\", description: \"Login rate limiting\" },\n        { role: \"coder\", assignment: \"# Target\nsrc/auth/signup.ts\n# Change\nAdd input validation\n# Acceptance\nValidation blocks invalid emails\", description: \"Signup validation\" },\n      ]\n    })\n\nPrefer one wide batch over serial calls when work items do not share files. If tasks overlap, have agents coordinate before editing.\n</structure>\n\n<patterns>\n- **Adversarial verify** \u2014 dispatch skeptical reviewers with distinct targets, then keep only findings you can verify against source.\n- **Perspective-diverse review** \u2014 use separate correctness, security, performance roles instead of identical reviewers.\n- **Completeness critic** \u2014 after the first batch, dispatch one read-only critic that asks what was missed.\n- **No silent caps** \u2014 if you bound coverage (top-N, sampling), state what was dropped and why.\n- **Parent owns closure** \u2014 subagents return evidence; the parent reads it, resolves contradictions, runs proof, and makes the final decision.\n- **Save reusable workflows** \u2014 if the fan-out pattern is reusable, save it as a `/workflow create <name>` command. Generate a JS file with `export const meta = { name, description, phases }` and a default async function that orchestrates via `ctx.runSubagents`. Use the REST API `POST /api/workflows` with body `{ name, source }` to save it, or write the file directly to `.c0de/workflows/<name>.js`. Saved workflows become slash commands (`/<name>`) that can be re-run anytime.\n</patterns>\n\n<execution>\n- **You MUST call the `task` tool** \u2014 this is the defining action of a workflowz request. A response that only does inline read/glob/edit without dispatching sub-agents is a failure.\n- Capture multi-phase workflow state in the visible todo system when available.\n- Batch independent subagents in one `task` call.\n- Give every subagent a narrow target, explicit non-goals, and a concrete return packet.\n- After fan-out returns, read the results, patch or decide, and run the shared gate.\n- Keep going until the task is closed \u2014 returned fan-out is a step, not a stopping point.\n</execution>\n</workflow-notice>";
+export declare const WORKFLOW_NOTICE = "<workflow-notice>\nThe user's message contains the **workflowz** keyword. This triggers the Dynamic Workflow system. You MUST first determine the user's intent:\n\n<intent-detection>\n- **Create/save a workflow** \u2014 the user says \"workflowz \u521B\u5EFA/\u5EFA/save/make a workflow\" \u2014 they want you to GENERATE a reusable JavaScript workflow script and save it. Jump to <create-workflow> below.\n- **Execute a workflow** \u2014 the user says \"workflowz \u626B\u63CF/\u5BA1\u67E5/\u91CD\u6784/\u6D4B\u8BD5...\" \u2014 they want you to drive a deterministic multi-subagent fan-out using the `task` tool. Jump to <task-contract> below.\n- **Both** \u2014 \"workflowz \u521B\u5EFA\u4E00\u4E2A\u626B\u63CF\u5DE5\u4F5C\u6D41\" means create the workflow script first, then optionally run it.\n</intent-detection>\n\n<create-workflow>\nWhen the intent is to CREATE a workflow, you MUST generate a **JavaScript** file (NOT bash/shell/python) with this exact structure:\n\n```js\n// File: .c0de/workflows/<name>.js\nexport const meta = {\n  name: '<name>',           // lowercase, kebab-case, matches filename\n  description: '<description>',\n  argsHint: '[optional args]',\n  phases: ['phase1', 'phase2', ...],\n  timeout: 300,            // optional, seconds\n}\n\nexport default async function workflow(ctx) {\n  const { runSubagents, runSubagent, utils, progress, project, args } = ctx\n\n  // Phase 1: progress('starting...', { phase: 'phase1' })\n  // Call runSubagents for parallel fan-out:\n  const results = await runSubagents('researcher', [\n    { assignment: '...', description: 'task 1' },\n    { assignment: '...', description: 'task 2' },\n  ])\n  // results: [{ ok: true, output: '...' }, { ok: false, error: '...' }]\n\n  // Phase 2: verify / cross-check results\n  // Phase 3: return summary\n  return { output: 'summary text', data: { ... } }\n}\n```\n\n**Rules:**\n1. The file MUST be `.js` with ES module exports (`export const meta` + `export default async function`).\n2. Save to `<project_root>/.c0de/workflows/<name>.js` \u2014 use the `write` tool.\n3. Use `ctx.runSubagents(type, tasks[])` for parallel dispatch, `ctx.runSubagent(type, params)` for single dispatch.\n4. Available subagent types: `general`, `coder`, `researcher`, `reviewer`.\n5. Use `ctx.utils` for file ops: `glob(pattern)`, `grep(pattern, path?)`, `read(path, range?)`, `splitByDirectory(dir, {depth, ignore})`.\n6. Use `ctx.progress(message, { phase })` to report progress.\n7. Parse subagent output with `JSON.parse(r.output)` \u2014 subagents return text.\n8. Return `{ output: 'summary', data: {...} }` as the final result.\n9. NEVER generate bash/shell scripts, python scripts, or any non-JS format for workflows.\n10. After writing the file, tell the user they can run it with `/workflow run <name>` or via POST /api/workflows/:name/run.\n</create-workflow>\n\n<when>\nWhen the intent is to EXECUTE a workflow (not create), you may do a brief inline scout (1-2 tool calls to list files/scope the work), but your NEXT action after scouting MUST be a `task` tool call to fan out. Do NOT spend the entire turn reading files inline \u2014 that defeats the purpose. Common shapes:\n- **Understand** \u2014 parallel readers over subsystems \u2192 structured map.\n- **Design** \u2014 independent approaches \u2192 scored synthesis.\n- **Review** \u2014 split dimensions \u2192 find per dimension \u2192 adversarially verify each finding.\n- **Research** \u2014 multi-modal sweep \u2192 deep-read the hits \u2192 synthesize.\n- **Migrate** \u2014 discover sites \u2192 transform each \u2192 verify.\n</when>\n\n<task-contract>\nCall `task` once per independent fan-out batch using the batch form:\n\n    task({\n      subagent_type: \"coder\",\n      context: \"shared background all subagents need\",\n      tasks: [\n        { role: \"coder\", assignment: \"specific assignment for agent 1\", description: \"short label\" },\n        { role: \"reviewer\", assignment: \"specific assignment for agent 2\", description: \"short label\" },\n      ]\n    })\n\nAvailable subagent types: `general` (full tools, recursive), `coder` (implementation), `researcher` (read-only scout), `reviewer` (code review). Pick the type that matches each task's intent.\n\n`context` carries shared background prepended to every subagent's prompt \u2014 put the shared contract, conventions, and coordination rules here.\n\nEach task in `tasks[]` must be self-contained:\n- `role`: specialist type for this sub-task (e.g. coder, reviewer, researcher)\n- `assignment`: exact target (files, symbols, subsystem) + what to do + acceptance criteria\n- `description`: short label for the UI\n\nEach subagent runs in an isolated session and returns its result via the `yield` tool. Subagents skip formatters, linters, and project-wide tests \u2014 the parent runs shared proof once after all results return.\n</task-contract>\n\n<structure>\nDecompose first, then batch the independent leaves:\n\n    task({\n      subagent_type: \"coder\",\n      context: \"# Goal\nImplement feature X across the codebase\n# Constraints\nFollow existing patterns...\n# Contract\nReturn findings as structured data...\",\n      tasks: [\n        { role: \"coder\", assignment: \"# Target\nsrc/auth/login.ts\n# Change\nAdd rate limiting to login endpoint\n# Acceptance\nRate limiter works, tests pass\", description: \"Login rate limiting\" },\n        { role: \"coder\", assignment: \"# Target\nsrc/auth/signup.ts\n# Change\nAdd input validation\n# Acceptance\nValidation blocks invalid emails\", description: \"Signup validation\" },\n      ]\n    })\n\nPrefer one wide batch over serial calls when work items do not share files. If tasks overlap, have agents coordinate before editing.\n</structure>\n\n<patterns>\n- **Adversarial verify** \u2014 dispatch skeptical reviewers with distinct targets, then keep only findings you can verify against source.\n- **Perspective-diverse review** \u2014 use separate correctness, security, performance roles instead of identical reviewers.\n- **Completeness critic** \u2014 after the first batch, dispatch one read-only critic that asks what was missed.\n- **No silent caps** \u2014 if you bound coverage (top-N, sampling), state what was dropped and why.\n- **Parent owns closure** \u2014 subagents return evidence; the parent reads it, resolves contradictions, runs proof, and makes the final decision.\n</patterns>\n\n<execution>\n- **You MUST call the `task` tool** \u2014 this is the defining action of a workflowz request. A response that only does inline read/glob/edit without dispatching sub-agents is a failure.\n- Capture multi-phase workflow state in the visible todo system when available.\n- Batch independent subagents in one `task` call.\n- Give every subagent a narrow target, explicit non-goals, and a concrete return packet.\n- After fan-out returns, read the results, patch or decide, and run the shared gate.\n- Keep going until the task is closed \u2014 returned fan-out is a step, not a stopping point.\n</execution>\n</workflow-notice>";
 /**
  * 构建工作流 steering 通知：基础通知 + 可选的已注册工作流列表。
  * 无工作流时退化为纯基础通知（向后兼容）。

package/dist/core/workflow.js

@@ -37,10 +37,59 @@ export function containsWorkflow(text) {
  * 适配 c0de-agent 的 task 工具 schema（subagent_type + context + tasks[]）。
  */
 export const WORKFLOW_NOTICE = `<workflow-notice>
-The user's message contains the **workflowz** keyword: you MUST drive this task as a deterministic multi-subagent workflow using the \`task\` tool for batched fan-out. This is not optional — the keyword signals the user explicitly wants parallel sub-agent decomposition, not inline work. This overrides any default tendency to do the whole task inline.
+The user's message contains the **workflowz** keyword. This triggers the Dynamic Workflow system. You MUST first determine the user's intent:
+
+<intent-detection>
+- **Create/save a workflow** — the user says "workflowz 创建/建/save/make a workflow" — they want you to GENERATE a reusable JavaScript workflow script and save it. Jump to <create-workflow> below.
+- **Execute a workflow** — the user says "workflowz 扫描/审查/重构/测试..." — they want you to drive a deterministic multi-subagent fan-out using the \`task\` tool. Jump to <task-contract> below.
+- **Both** — "workflowz 创建一个扫描工作流" means create the workflow script first, then optionally run it.
+</intent-detection>
+
+<create-workflow>
+When the intent is to CREATE a workflow, you MUST generate a **JavaScript** file (NOT bash/shell/python) with this exact structure:
+
+\`\`\`js
+// File: .c0de/workflows/<name>.js
+export const meta = {
+  name: '<name>',           // lowercase, kebab-case, matches filename
+  description: '<description>',
+  argsHint: '[optional args]',
+  phases: ['phase1', 'phase2', ...],
+  timeout: 300,            // optional, seconds
+}
+
+export default async function workflow(ctx) {
+  const { runSubagents, runSubagent, utils, progress, project, args } = ctx
+
+  // Phase 1: progress('starting...', { phase: 'phase1' })
+  // Call runSubagents for parallel fan-out:
+  const results = await runSubagents('researcher', [
+    { assignment: '...', description: 'task 1' },
+    { assignment: '...', description: 'task 2' },
+  ])
+  // results: [{ ok: true, output: '...' }, { ok: false, error: '...' }]
+
+  // Phase 2: verify / cross-check results
+  // Phase 3: return summary
+  return { output: 'summary text', data: { ... } }
+}
+\`\`\`
+
+**Rules:**
+1. The file MUST be \`.js\` with ES module exports (\`export const meta\` + \`export default async function\`).
+2. Save to \`<project_root>/.c0de/workflows/<name>.js\` — use the \`write\` tool.
+3. Use \`ctx.runSubagents(type, tasks[])\` for parallel dispatch, \`ctx.runSubagent(type, params)\` for single dispatch.
+4. Available subagent types: \`general\`, \`coder\`, \`researcher\`, \`reviewer\`.
+5. Use \`ctx.utils\` for file ops: \`glob(pattern)\`, \`grep(pattern, path?)\`, \`read(path, range?)\`, \`splitByDirectory(dir, {depth, ignore})\`.
+6. Use \`ctx.progress(message, { phase })\` to report progress.
+7. Parse subagent output with \`JSON.parse(r.output)\` — subagents return text.
+8. Return \`{ output: 'summary', data: {...} }\` as the final result.
+9. NEVER generate bash/shell scripts, python scripts, or any non-JS format for workflows.
+10. After writing the file, tell the user they can run it with \`/workflow run <name>\` or via POST /api/workflows/:name/run.
+</create-workflow>
 
 <when>
-The user typed workflowz intentionally — they want fan-out. You may do a brief inline scout (1-2 tool calls to list files/scope the work), but your NEXT action after scouting MUST be a \`task\` tool call to fan out. Do NOT spend the entire turn reading files inline — that defeats the purpose. Common shapes:
+When the intent is to EXECUTE a workflow (not create), you may do a brief inline scout (1-2 tool calls to list files/scope the work), but your NEXT action after scouting MUST be a \`task\` tool call to fan out. Do NOT spend the entire turn reading files inline — that defeats the purpose. Common shapes:
 - **Understand** — parallel readers over subsystems → structured map.
 - **Design** — independent approaches → scored synthesis.
 - **Review** — split dimensions → find per dimension → adversarially verify each finding.
@@ -93,7 +142,6 @@ Prefer one wide batch over serial calls when work items do not share files. If t
 - **Completeness critic** — after the first batch, dispatch one read-only critic that asks what was missed.
 - **No silent caps** — if you bound coverage (top-N, sampling), state what was dropped and why.
 - **Parent owns closure** — subagents return evidence; the parent reads it, resolves contradictions, runs proof, and makes the final decision.
-- **Save reusable workflows** — if the fan-out pattern is reusable, save it as a \`/workflow create <name>\` command. Generate a JS file with \`export const meta = { name, description, phases }\` and a default async function that orchestrates via \`ctx.runSubagents\`. Use the REST API \`POST /api/workflows\` with body \`{ name, source }\` to save it, or write the file directly to \`.c0de/workflows/<name>.js\`. Saved workflows become slash commands (\`/<name>\`) that can be re-run anytime.
 </patterns>
 
 <execution>
@@ -112,12 +160,12 @@ Prefer one wide batch over serial calls when work items do not share files. If t
 export function buildWorkflowNotice(workflows) {
     const registeredSection = workflows && workflows.length > 0
         ? `\n<registered-workflows>
-Available workflow templates you can invoke with the task tool's workflow parameter:
+Available saved workflow scripts (run with /workflow run <name> or POST /api/workflows/:name/run):
 ${workflows.map((w) => `- ${w.name}: ${w.description}`).join('\n')}
-If none fit, orchestrate inline using runSubagent fan-out as described below, then save your workflow with POST /api/workflows { name, source } for reuse.
+To create a new workflow, generate a .js file with export const meta + export default async function(ctx) and save it to .c0de/workflows/<name>.js.
 </registered-workflows>`
         : `\n<registered-workflows>
-No saved workflows yet. After orchestrating a successful fan-out, save it with POST /api/workflows { name, source } for reuse.
+No saved workflow scripts yet. When the user asks to create a workflow, generate a .js file (export const meta + export default async function) and save it to .c0de/workflows/<name>.js.
 </registered-workflows>`;
     return WORKFLOW_NOTICE + registeredSection;
 }

package/dist/core/workflows/runtime.d.ts

@@ -1,5 +1,6 @@
 import type { AgentDependencies, AgentState, CommandResult } from '../types.js';
 import type { WorkflowRegistry } from './registry.js';
+import type { WorkflowEntry } from './types.js';
 /** executeWorkflow 的参数。 */
 type ExecuteWorkflowOpts = {
     registry: WorkflowRegistry;
@@ -7,6 +8,8 @@ type ExecuteWorkflowOpts = {
     args: string;
     deps: AgentDependencies;
     parent: AgentState;
+    /** 已解析的 entry（如项目级工作流），优先于 registry.get(name)。 */
+    entry?: WorkflowEntry;
     onProgress?: (message: string, detail?: unknown) => void;
 };
 /**

package/dist/core/workflows/runtime.js

@@ -20,8 +20,8 @@ function createTimeoutPromise(timeoutMs, timeoutSeconds) {
  * 工作流 return 的 output 作为 text 返回；异常捕获为 error。
  */
 async function executeWorkflow(opts) {
-    const { registry, name, args, deps, parent, onProgress } = opts;
-    const entry = registry.get(name);
+    const { registry, name, args, deps, parent, onProgress, entry: resolvedEntry } = opts;
+    const entry = resolvedEntry ?? registry.get(name);
     if (!entry) {
         const available = registry
             .list()

package/dist/project/resolve.d.ts

@@ -5,4 +5,79 @@ export type ResolvedProject = {
     gitRemote: string | null;
     gitBranch: string | null;
 };
+/** 文件 git 状态分类（用于文件树高亮）。按「最值得注意」优先级排列。 */
+export type GitStatusCode = 'modified' | 'staged' | 'untracked' | 'conflict' | 'deleted' | 'ignored';
+/** 目录聚合时的优先级（越大越优先展示）。ignored 最低：被忽略目录下若有真实变更仍显示变更态。 */
+export declare const GIT_STATUS_PRIORITY: Record<GitStatusCode, number>;
+export declare function getGitStatus(cwd: string): Record<string, GitStatusCode> | null;
+/** 检查给定路径中哪些被 gitignore 规则覆盖。
+ *
+ * 用 git check-ignore 只查询传入的路径（不递归），返回被忽略路径的集合。
+ * 只检查当前展开目录的直接子项（通常 10-50 个），不递归进 node_modules 等。
+ * 非 git 仓库或无忽略文件时返回空集。
+ *
+ * 注意：git check-ignore 在「无路径被忽略」或「非 git 仓库」时退出码为 1，
+ * 这两种情况都返回空集。 */
+export declare function checkIgnored(cwd: string, paths: string[]): Set<string>;
+/** 追加条目到 .gitignore（去重，文件不存在则创建）。 */
+export declare function appendToGitignore(cwd: string, patterns: string[]): void;
+/**
+ * 取当前分支名（非 git 仓库返回 null）。
+ */
+export declare function getGitBranch(cwd: string): string | null;
+/** 最后一次提交摘要（供分支名 hover tooltip）。 */
+export interface GitLastCommit {
+    subject: string;
+    hash: string;
+    author: string;
+    date: string;
+}
+/**
+ * 取最后一次提交信息（subject/hash/author/相对时间）。
+ * 非 git 仓库或无提交（如全新仓库）返回 null。
+ */
+export declare function getGitLastCommit(cwd: string): GitLastCommit | null;
+/**
+ * 取工作区变更摘要（供 LLM 生成 commit message）。
+ * 包含 staged + unstaged diff（相对 HEAD）和 untracked 文件名列表。
+ * 非 git 仓库或无变更返回 null。
+ */
+export declare function getGitDiffSummary(cwd: string): {
+    diff: string;
+    fileCount: number;
+} | null;
+/**
+ * 执行 git add -A + git commit。成功返回 commit 短 hash，失败返回 error 信息。
+ */
+export declare function performGitCommit(cwd: string, message: string): {
+    hash: string;
+} | {
+    error: string;
+};
+/** 分支信息。 */
+export interface GitBranchInfo {
+    name: string;
+    current: boolean;
+    lastSubject: string | null;
+}
+/**
+ * 列出本地分支及当前分支标记（非 git 仓库返回 null）。
+ */
+export declare function listGitBranches(cwd: string): GitBranchInfo[] | null;
+/**
+ * 切换到指定分支（git checkout）。成功返回分支名，失败返回 error。
+ */
+export declare function checkoutGitBranch(cwd: string, branch: string): {
+    branch: string;
+} | {
+    error: string;
+};
+/**
+ * 创建并切换到新分支。成功返回分支名，失败返回 error。
+ */
+export declare function createGitBranch(cwd: string, name: string): {
+    branch: string;
+} | {
+    error: string;
+};
 export declare function resolveProject(directory: string): ResolvedProject;