From d084d10f85df8865ea75962928ba6876d0262cd9 Mon Sep 17 00:00:00 2001 From: kicer Date: Fri, 25 Sep 2026 19:15:31 +0800 Subject: [PATCH] =?UTF-8?q?handoff=E5=B7=A5=E5=85=B7=E6=8F=8F=E8=BF=B0?= =?UTF-8?q?=E5=8E=BBtask.md=E5=BC=95=E7=94=A8=E4=B8=8E=E4=B8=AD=E6=96=87?= =?UTF-8?q?=E4=BE=8B=E5=8F=A5(=E9=98=B2=E8=AF=AF=E5=AF=BC=E9=A1=BE?= =?UTF-8?q?=E9=97=AEAI;=E8=90=BD=E7=9B=98=E4=BD=8D=E7=BD=AE=E7=94=B1?= =?UTF-8?q?=E7=B3=BB=E7=BB=9F=E6=8F=90=E7=A4=BA=E8=AF=8D=E5=8D=95=E5=90=91?= =?UTF-8?q?=E8=AF=B4=E6=98=8E,tool=E6=8F=8F=E8=BF=B0=E5=8F=AA=E8=AE=B2?= =?UTF-8?q?=E8=AF=AD=E4=B9=89)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- app/server/tools/definitions.json | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/app/server/tools/definitions.json b/app/server/tools/definitions.json index b636df0..87958df 100644 --- a/app/server/tools/definitions.json +++ b/app/server/tools/definitions.json @@ -109,7 +109,7 @@ "type": "function", "function": { "name": "handoff", - "description": "Hand off from the advising phase to the execution phase. Call this when the task brief is ready. The system will write your `brief` to task.md and switch to execution. There are three cases:\n\n- ready: The requirement is clear enough to execute.\n- user_skip: The user explicitly asks to skip planning (\"just do it\", \"别问了\", \"换个 agent\", \"直接开始\", or similar). Do not call this on tone or mood alone — only on explicit signals.\n- user_stuck: You have asked 2-3 rounds and the user is still not providing key information, and they seem to want to move on.\n\nWhen reason is not \"ready\", pass the user's own words as `brief` and leave it at that. Do not invent a methodology or generic plan. The executor will ask the user for missing information directly.", + "description": "Hand off from the advising phase to the execution phase. Call this when the task brief is ready. The system stores your `brief` as the task brief and switches to execution. There are three cases:\n\n- ready: The requirement is clear enough to execute.\n- user_skip: The user explicitly asks to skip planning (\"just do it\", or similar). Do not call this on tone or mood alone — only on explicit signals.\n- user_stuck: You have asked 2-3 rounds and the user is still not providing key information, and they seem to want to move on.\n\nWhen reason is not \"ready\", pass the user's own words as `brief` and leave it at that. Do not invent a methodology or generic plan. The executor will ask the user for missing information directly.", "parameters": { "type": "object", "required": [ @@ -128,7 +128,7 @@ }, "brief": { "type": "string", - "description": "The task brief content, in Markdown. This is written to task.md verbatim. Follow the structure described in your system prompt." + "description": "The task brief content, in Markdown. Follow the structure described in your system prompt." } } }