dsh-taskforce

Configuration (worker personas, models, limits)

The orchestrator writes per-task personas itself: each task in a plan may carry a persona field — a role definition A tailors to that task ("你是数据库 迁移专家，只改 SQL 文件"). It becomes the worker's primary system prompt, layered above the profile's discipline (non-negotiable constraints that A cannot override: researchers don't write, reviewers don't fix, …). model and reasoning_effort are likewise per-task fields A sets at plan time.

Two more ways to tune what each worker role is like — both take effect after restarting the dsh process:

1. Edit src/profiles.js directly. Each role has role (identity line), discipline (permanent constraints), effort (off|low|high|max), and toolDenyPatterns — regexes matched (case-insensitively) against the host's global tool names to hard-restrict that role's tools.

2. Config overrides (no code edit). Add a config: block to the plugin entry in the profile's cordis.patch.yml (e.g. ~/.dsh/profiles/web/cordis.patch.yml):

   - id: dsh-taskforce
     name: dsh-taskforce
     config:
       taskTimeoutMs: 1200000
       maxConcurrentWorkers: 6
       profiles:
         researcher:
           role: |
             你是资深代码考古学家……
           discipline: |
             只读，不修改任何文件。
           effort: off
           toolDenyPatterns: ["write", "bash"]
         coder:
           model: deepseek-chat
   

   Config role/discipline/model/effort replace the builtin values; toolDenyPatterns are concatenated with the builtin ones. Engine knobs: provider (default spawn), maxConcurrentWorkers (4), maxAttempts (3), maxReviewRounds (3), taskTimeoutMs (600000).