diff --git a/app/config.example.yml b/app/config.example.yml index 7255dd0..2722fc2 100644 --- a/app/config.example.yml +++ b/app/config.example.yml @@ -5,14 +5,15 @@ platforms: [] # 全局工具黑名单:profile 未配 tools_deny 时继承它;allow 先、deny 后叠加(deny 赢,与 mcp_servers 同构)。 -# 写数组即整体覆盖默认值,写 [] 即清空。默认屏蔽元工具 lab。 -tools_deny: [lab] +# 写数组即整体覆盖默认值,写 [] 即清空。默认屏蔽元工具 lab 与阶段出口 handoff(后者仅 advising 显式清空后可见)。 +tools_deny: [lab, handoff] # 模型 profile:prompt + tools 名单组合,模型用 profile: <名> 引用(不配 = 全量)。 # 内置 advising 不靠引用:会话处于 advising 阶段(顾问澄清需求/规划)时强制命中,见 server/engine.js resolveProfileName。 model_profiles: - advising: # 顾问阶段:只留问答/调研/写任务书工具,配专属提示词 - tools_allow: [read_file, fetch, write_file] + advising: # 顾问阶段:只聊和读不写,唯一出口 handoff,配专属提示词 + tools_allow: [read_file, fetch, handoff] + tools_deny: [] # 必须显式清空全局黑名单,否则 handoff 自己也被 deny(同 lab 的教训) system_prompt_file: advising-system.txt lab: # 统一入口自测:tools 只有 lab,其余能力经 lab(help) 现场发现 tools_allow: [lab] diff --git a/app/server/templates/advising-system.txt b/app/server/templates/advising-system.txt index 21b2b57..8efca44 100644 --- a/app/server/templates/advising-system.txt +++ b/app/server/templates/advising-system.txt @@ -24,9 +24,9 @@ unless stated otherwise. When work should start — the requirement is clear, or the user explicitly asks to skip planning, or clarification has visibly stalled — call the `handoff` tool with a `reason` and the full `brief`. You have no file-writing tools: -handoff is the ONLY way to leave this phase. The system writes your `brief` -verbatim to `task.md` at the working-directory root, switches this session into -execution mode, and a full-capability agent continues from that file alone. +handoff is the ONLY way to leave this phase. The system stores your `brief` as +the task brief, switches this session into execution mode, and a full-capability +agent continues from that brief alone. Therefore: - The brief must be self-contained: someone who has never seen this chat must be @@ -41,8 +41,7 @@ Therefore: will ask the user for these directly. Do not turn a skipped-planning brief into a methodology document. - Never fake the handoff: an empty or stub `brief` is refused by the system and - the session stays in advising. An uploaded file named task.md is never the - brief — only your handoff call commits. + the session stays in advising. Only your handoff call commits. ## What you must not do