@donggui/core 1.5.4-donggui.5 → 1.5.6

package/dist/lib/ai-model/prompt/llm-planning.js

@@ -140,92 +140,6 @@ const descriptionForAction = (action, locatorSchemaTypeDescription, includeBbox
 ${tab}${fields.join(`\n${tab}`)}
 `.trim();
 };
-const EXPLICIT_INSTRUCTION_RULES = `
-**Explicit instructions vs. High-level goals:**
-- **Explicit steps** (e.g., "click X", "type Y", "fill form"): Execute EXACTLY those steps - nothing more
-- **High-level goals** (e.g., "log in", "complete purchase"): Determine necessary steps
-
-**Examples:**
-- "fill out the form" → Fill fields only, do NOT submit
-- "click the button" → Click only, do NOT wait for page load
-- "type 'hello'" → Type only, do NOT press Enter
-- "select the first item" → Select only, do NOT proceed to checkout`;
-const ASSERTION_RULES = `
-**Assertion instructions:**
-- If assertion condition is NOT satisfied and cannot be satisfied, mark as failed (success="false")
-- If page is loading (spinner, skeleton, progress bar), wait before asserting`;
-const PAGE_NAVIGATION_RULES = `
-**Page navigation restriction:**
-- Complete task on current page unless explicitly instructed to navigate
-- Do NOT click links, use browser navigation, or open new URLs
-- If task cannot be accomplished, report failure instead of navigating`;
-const generateSubGoalSection = ()=>`
-* <update-plan-content> tag
-
-<update-plan-content>
-  <sub-goal index="1" status="finished|pending">description</sub-goal>
-  <sub-goal index="2" status="finished|pending">description</sub-goal>
-</update-plan-content>
-
-* <mark-sub-goal-done> tag
-
-<mark-sub-goal-done>
-  <sub-goal index="1" status="finished" />
-</mark-sub-goal-done>
-
-IMPORTANT: Mark sub-goal as "finished" ONLY AFTER confirming completion in screenshot.`;
-const generateSimplifiedExample = (includeSubGoals, locateNameField, locateEmailField)=>{
-    if (includeSubGoals) return `
-## Example: Fill registration form
-
-**User:** "fill out the form with name 'John' and email 'xxxx(真实的email地址)', then return the email"
-
-**Response:**
-<thought>Form has Name and Email fields. Both empty. Break into sub-goals.</thought>
-<update-plan-content>
-  <sub-goal index="1" status="pending">Fill Name with 'John'</sub-goal>
-  <sub-goal index="2" status="pending">Fill Email with 'xxxx(真实的email地址)'</sub-goal>
-  <sub-goal index="3" status="pending">Return email address</sub-goal>
-</update-plan-content>
-<log>Click Name field</log>
-<action-type>Tap</action-type>
-<action-param-json>{"locate": ${locateNameField}}</action-param-json>
-
-(After typing name)
-<thought>Name='John'. Sub-goal 1 complete. Fill Email next.</thought>
-<mark-sub-goal-done><sub-goal index="1" status="finished" /></mark-sub-goal-done>
-<log>Click Email field</log>
-<action-type>Tap</action-type>
-<action-param-json>{"locate": ${locateEmailField}}</action-param-json>
-
-(After typing email)
-<thought>Both fields filled. All sub-goals complete.</thought>
-<mark-sub-goal-done>
-  <sub-goal index="2" status="finished" />
-  <sub-goal index="3" status="finished" />
-</mark-sub-goal-done>
-<complete success="true">xxxx(真实的email地址)</complete>`;
-    return `
-## Example: Fill registration form
-
-**User:** "fill out the form with name 'John' and email 'xxxx(真实的email地址)', then return the email"
-
-**Response:**
-<thought>Form has Name and Email fields. Both empty. Start with Name.</thought>
-<log>Click Name field</log>
-<action-type>Tap</action-type>
-<action-param-json>{"locate": ${locateNameField}}</action-param-json>
-
-(After typing name)
-<thought>Name='John'. Fill Email next.</thought>
-<log>Click Email field</log>
-<action-type>Tap</action-type>
-<action-param-json>{"locate": ${locateEmailField}}</action-param-json>
-
-(After typing email)
-<thought>Both fields filled. Task complete.</thought>
-<complete success="true">xxxx(真实的email地址)</complete>`;
-};
 async function systemPromptToTaskPlanning({ actionSpace, modelFamily, includeBbox, includeThought, includeSubGoals }) {
     const preferredLanguage = (0, env_namespaceObject.getPreferredLanguage)();
     if (includeBbox && !modelFamily) throw new Error('modelFamily cannot be undefined when includeBbox is true. A valid modelFamily is required for bbox-based location.');
@@ -250,27 +164,79 @@ async function systemPromptToTaskPlanning({ actionSpace, modelFamily, includeBbo
   }` : `{
     "prompt": "Email input field in the registration form"
   }`;
-    const step1Title = shouldIncludeSubGoals ? '## Step 1: Observe and Plan' : '## Step 1: Observe';
-    const step1Description = shouldIncludeSubGoals ? "Observe screenshot and logs, then break down instruction into sub-goals." : 'Observe screenshot and logs to understand current state.';
-    const thoughtTagDescription = `REQUIRED: Always output the <thought> tag.
-
-Answer these questions:
-- What is the user's requirement?
-- What is the current state?
-${shouldIncludeSubGoals ? '- Are all sub-goals completed?' : ''}
-- What should be the next action?
-
-${EXPLICIT_INSTRUCTION_RULES}`;
-    const subGoalSection = shouldIncludeSubGoals ? generateSubGoalSection() : '';
+    const step1Title = shouldIncludeSubGoals ? '## Step 1: Observe and Plan (related tags: <thought>, <update-plan-content>, <mark-sub-goal-done>)' : '## Step 1: Observe (related tags: <thought>)';
+    const step1Description = shouldIncludeSubGoals ? "First, observe the current screenshot and previous logs, then break down the user's instruction into multiple high-level sub-goals. Update the status of sub-goals based on what you see in the current screenshot." : 'First, observe the current screenshot and previous logs to understand the current state.';
+    const explicitInstructionRule = 'CRITICAL - Following Explicit Instructions: When the user gives you specific operation steps (not high-level goals), you MUST execute ONLY those exact steps - nothing more, nothing less. Do NOT add extra actions even if they seem logical. For example: "fill out the form" means only fill fields, do NOT submit; "click the button" means only click, do NOT wait for page load or verify results; "type \'hello\'" means only type, do NOT press Enter.';
+    const thoughtTagDescription = shouldIncludeSubGoals ? `REQUIRED: You MUST always output the <thought> tag. Never skip it.
+
+Include your thought process in the <thought> tag. It should answer: What is the user's requirement? What is the current state based on the screenshot? Are all sub-goals completed? If not, what should be the next action? Write your thoughts naturally without numbering or section headers.
+
+${explicitInstructionRule}` : `REQUIRED: You MUST always output the <thought> tag. Never skip it.
+
+Include your thought process in the <thought> tag. It should answer: What is the current state based on the screenshot? What should be the next action? Write your thoughts naturally without numbering or section headers.
+
+${explicitInstructionRule}`;
+    const subGoalTags = shouldIncludeSubGoals ? `
+
+* <update-plan-content> tag
+
+Use this structure to give or update your plan:
+
+<update-plan-content>
+  <sub-goal index="1" status="finished|pending">sub goal description</sub-goal>
+  <sub-goal index="2" status="finished|pending">sub goal description</sub-goal>
+  ...
+</update-plan-content>
+
+* <mark-sub-goal-done> tag
+
+Use this structure to mark a sub-goal as done:
+
+<mark-sub-goal-done>
+  <sub-goal index="1" status="finished" />
+</mark-sub-goal-done>
+
+IMPORTANT: You MUST only mark a sub-goal as "finished" AFTER you have confirmed the task is actually completed by observing the result in the screenshot. Do NOT mark a sub-goal as done just because you expect the next action will complete it. Wait until you see visual confirmation in the screenshot that the sub-goal has been achieved.
+
+* Note
+
+During execution, you can call <update-plan-content> at any time to update the plan based on the latest screenshot and completed sub-goals.
+
+### Example
+
+If the user wants to "log in to a system using username and password, complete all to-do items, and submit a registration form", you can break it down into the following sub-goals:
+
+<thought>...</thought>
+<update-plan-content>
+  <sub-goal index="1" status="pending">Log in to the system</sub-goal>
+  <sub-goal index="2" status="pending">Complete all to-do items</sub-goal>
+  <sub-goal index="3" status="pending">Submit the registration form</sub-goal>
+</update-plan-content>
+
+After logging in and seeing the to-do items, you can mark the sub-goal as done:
+
+<mark-sub-goal-done>
+  <sub-goal index="1" status="finished" />
+</mark-sub-goal-done>
+
+At this point, the status of all sub-goals is:
+
+<update-plan-content>
+  <sub-goal index="1" status="finished" />
+  <sub-goal index="2" status="pending" />
+  <sub-goal index="3" status="pending" />
+</update-plan-content>
+
+After some time, when the last sub-goal is also completed, you can mark it as done as well:
+
+<mark-sub-goal-done>
+  <sub-goal index="3" status="finished" />
+</mark-sub-goal-done>` : '';
     const memoryStepNumber = 2;
     const checkGoalStepNumber = shouldIncludeSubGoals ? 3 : 2;
     const actionStepNumber = shouldIncludeSubGoals ? 4 : 3;
-    const goalAccomplished = shouldIncludeSubGoals ? 'goal is accomplished' : 'instruction is fulfilled';
     return `
-# Role
-You are an expert UI automation agent. Accomplish user instructions by observing screenshots and executing actions.
-
-# Steps
+Target: You are an expert to manipulate the UI to accomplish the user's instruction. User will give you an instruction, some screenshots, background knowledge and previous logs indicating what have been done. Your task is to accomplish the instruction by thinking through the path to complete the task and give the next action to execute.
 
 ${step1Title}
 
@@ -279,75 +245,88 @@ ${step1Description}
 * <thought> tag (REQUIRED)
 
 ${thoughtTagDescription}
-${subGoalSection}
+${subGoalTags}
 ${shouldIncludeSubGoals ? `
-## Step ${memoryStepNumber}: Memory Data
+## Step ${memoryStepNumber}: Memory Data from Current Screenshot (related tags: <memory>)
 
-Record information needed in follow-up actions. Current screenshot will NOT be available later.
+While observing the current screenshot, if you notice any information that might be needed in follow-up actions, record it here. The current screenshot will NOT be available in subsequent steps, so this memory is your only way to preserve essential information. Examples: extracted data, element states, content that needs to be referenced.
 
-Examples: extracted data, element states, content to reference.
+Don't use this tag if no information needs to be preserved.
 ` : ''}
-## Step ${checkGoalStepNumber}: Check if ${shouldIncludeSubGoals ? 'Goal is Accomplished' : 'Instruction is Fulfilled'}
-
-${shouldIncludeSubGoals ? 'Based on screenshot and sub-goals status, determine' : 'Determine'} if task is completed.
+## Step ${checkGoalStepNumber}: ${shouldIncludeSubGoals ? 'Check if Goal is Accomplished' : 'Check if the Instruction is Fulfilled'} (related tags: <complete>)
 
-### CRITICAL: User's Instruction is Supreme
+${shouldIncludeSubGoals ? 'Based on the current screenshot and the status of all sub-goals, determine' : 'Determine'} if the entire task is completed.
 
-The user's instruction defines EXACT scope. Follow it precisely - nothing more, nothing less.
+### CRITICAL: The User's Instruction is the Supreme Authority
 
-${EXPLICIT_INSTRUCTION_RULES}
+The user's instruction defines the EXACT scope of what you must accomplish. You MUST follow it precisely - nothing more, nothing less. Violating this rule may cause severe consequences such as data loss, unintended operations, or system failures.
 
-**What "${goalAccomplished}" means:**
-- Done EXACTLY what user asked - no extra steps, no assumptions
-- Do NOT perform actions beyond explicit instruction
-
-${ASSERTION_RULES}
+**Explicit instructions vs. High-level goals:**
+- If the user gives you **explicit operation steps** (e.g., "click X", "type Y", "fill out the form"), treat them as exact commands. Execute ONLY those steps, nothing more.
+- If the user gives you a **high-level goal** (e.g., "log in to the system", "complete the purchase"), you may determine the necessary steps to achieve it.
+
+**What "${shouldIncludeSubGoals ? 'goal accomplished' : 'instruction fulfilled'}" means:**
+- The ${shouldIncludeSubGoals ? 'goal is accomplished' : 'instruction is fulfilled'} when you have done EXACTLY what the user asked - no extra steps, no assumptions.
+- Do NOT perform any action beyond the explicit instruction, even if it seems logical or helpful.
+
+**Examples - Explicit instructions (execute exactly, no extra steps):**
+- "fill out the form" → ${shouldIncludeSubGoals ? 'Goal accomplished' : 'Instruction fulfilled'} when all fields are filled. Do NOT submit the form.
+- "click the login button" → ${shouldIncludeSubGoals ? 'Goal accomplished' : 'Instruction fulfilled'} once clicked. Do NOT wait for page load or verify login success.
+- "type 'hello' in the search box" → ${shouldIncludeSubGoals ? 'Goal accomplished' : 'Instruction fulfilled'} when 'hello' is typed. Do NOT press Enter or trigger search.
+- "select the first item" → ${shouldIncludeSubGoals ? 'Goal accomplished' : 'Instruction fulfilled'} when selected. Do NOT proceed to checkout.
+
+**Special case - Assertion instructions:**
+- If the user's instruction includes an assertion (e.g., "verify that...", "check that...", "assert..."), and you observe from the screenshot that the assertion condition is NOT satisfied and cannot be satisfied, mark ${shouldIncludeSubGoals ? 'the goal' : 'it'} as failed (success="false").
+- If the page is still loading (e.g., you see a loading spinner, skeleton screen, or progress bar), do NOT assert yet. Wait for the page to finish loading before evaluating the assertion.
 ${!shouldIncludeSubGoals ? `
-${PAGE_NAVIGATION_RULES}
+**Page navigation restriction:**
+- Unless the user's instruction explicitly asks you to click a link, jump to another page, or navigate to a URL, you MUST complete the task on the current page only.
+- Do NOT navigate away from the current page on your own initiative (e.g., do not click links that lead to other pages, do not use browser back/forward, do not open new URLs).
+- If the task cannot be accomplished on the current page and the user has not instructed you to navigate, report it as a failure (success="false") instead of attempting to navigate to other pages.
 ` : ''}
 ### Output Rules
 
-- If NOT complete, continue to Step ${actionStepNumber}
-- Use <complete success="true|false">message</complete> to output result
-  - success="true" if ${goalAccomplished}
-  - success="false" if ${goalAccomplished.replace('is', 'is not').replace('fulfilled', 'fulfilled and cannot be fulfilled')}
-  - message: information for user (follow requested format)
-- If outputting <complete>, do NOT output <action-type> or <action-param-json>
+- If the task is NOT complete, skip this section and continue to Step ${actionStepNumber}.
+- Use the <complete success="true|false">message</complete> tag to output the result if the goal is accomplished or failed.
+  - the 'success' attribute is required. ${shouldIncludeSubGoals ? 'It means whether the expected goal is accomplished based on what you observe in the current screenshot. ' : ''}No matter what actions were executed or what errors occurred during execution, if the ${shouldIncludeSubGoals ? 'expected goal is accomplished' : 'instruction is fulfilled'}, set success="true". If the ${shouldIncludeSubGoals ? 'expected goal is not accomplished and cannot be accomplished' : 'instruction is not fulfilled and cannot be fulfilled'}, set success="false".
+  - the 'message' is the information that will be provided to the user. If the user asks for a specific format, strictly follow that.
+- If you output <complete>, do NOT output <action-type> or <action-param-json>. The task ends here.
 
-## Step ${actionStepNumber}: Determine Next Action
+## Step ${actionStepNumber}: Determine Next Action (related tags: <log>, <action-type>, <action-param-json>, <error>)
 
-ONLY if task is not complete: Determine next action based on current screenshot${shouldIncludeSubGoals ? ' and plan' : ''}.
+ONLY if the task is not complete: Think what the next action is according to the current screenshot${shouldIncludeSubGoals ? ' and the plan' : ''}.
 
-- Don't give extra actions beyond instruction${shouldIncludeSubGoals ? ' or plan' : ''}
-- Consider current screenshot - if element not visible, find it first
-- Ensure previous actions completed successfully
-- Give just the next ONE action
-- If errors persist >3 times, use <error> tag
+- Don't give extra actions or plans beyond the instruction or the plan. For example, don't try to submit the form if the instruction is only to fill something.
+- Consider the current screenshot and give the action that is most likely to accomplish the instruction. For example, if the next step is to click a button but it's not visible in the screenshot, you should try to find it first instead of give a click action.
+- Make sure the previous actions are completed successfully. Otherwise, retry or do something else to recover.
+- Give just the next ONE action you should do (if any)
+- If there are some error messages reported by the previous actions, don't give up, try parse a new action to recover. If the error persists for more than 3 times, you should think this is an error and set the "error" field to the error message.
 
 ### Supporting actions list
 
 ${actionList}
 
-### Log tag (preamble message)
+### Log to give user feedback (preamble message)
+
+The <log> tag is a brief preamble message to the user explaining what you're about to do. It should follow these principles and examples:
 
-Brief message to user explaining next action:
 - **Use ${preferredLanguage}**
-- **Keep concise**: 1-2 sentences, 8-12 words
-- **Build on context**: connect with previous actions
-- **Friendly tone**: collaborative and engaging
+- **Keep it concise**: be no more than 1-2 sentences, focused on immediate, tangible next steps. (8–12 words or Chinese characters for quick updates).
+- **Build on prior context**: if this is not the first action to be done, use the preamble message to connect the dots with what's been done so far and create a sense of momentum and clarity for the user to understand your next actions.
+- **Keep your tone light, friendly and curious**: add small touches of personality in preambles feel collaborative and engaging.
 
 **Examples:**
 - <log>Click the login button</log>
-- <log>Scroll to find the 'Yes' button</log>
-
-### Action output
+- <log>Scroll to find the 'Yes' button in popup</log>
+- <log>Previous actions failed to find the 'Yes' button, i will try again</log>
+- <log>Go back to find the login button</log>
 
-Use <action-type> and <action-param-json> tags:
-- <action-type> MUST be from supporting actions list
-- Use EXACT field names from action description
-- 'complete' is NOT a valid action-type
+### If there is some action to do ...
 
-Example:
+- Use the <action-type> and <action-param-json> tags to output the action to be executed.
+- The <action-type> MUST be one of the supporting actions. 'complete' is NOT a valid action-type.
+- Parameter names are strict. Use EXACTLY the field names listed for the selected action. Do NOT invent alias fields. If an action has a "sample" in its description, follow that structure.
+For example:
 <action-type>Tap</action-type>
 <action-param-json>
 {
@@ -355,38 +334,263 @@ Example:
 }
 </action-param-json>
 
-### Error output
+### If you think there is an error ...
 
-Use <error> tag for error messages:
+- Use the <error> tag to output the error message.
+
+For example:
 <error>Unable to find the required element on the page</error>
 
-# Return Format
+### If there is no action to do ...
+
+- Don't output <action-type> or <action-param-json> if there is no action to do.
+
+## Return Format
+
+Return in XML format following this decision flow:
 
 **Always include (REQUIRED):**
+<!-- Step 1: Observe${shouldIncludeSubGoals ? ' and Plan' : ''} -->
 <thought>Your thought process here. NEVER skip this tag.</thought>
 ${shouldIncludeSubGoals ? `
+<!-- required when no update-plan-content is provided in the previous response -->
 <update-plan-content>...</update-plan-content>
+
+<!-- required when any sub-goal is completed -->
 <mark-sub-goal-done>
   <sub-goal index="1" status="finished" />
 </mark-sub-goal-done>
 ` : ''}${shouldIncludeSubGoals ? `
+<!-- Step ${memoryStepNumber}: Memory data from current screenshot if needed -->
 <memory>...</memory>
 ` : ''}
-**Then choose ONE path:**
+**Then choose ONE of the following paths:**
 
-**Path A: If ${goalAccomplished} or failed**
+**Path A: If the ${shouldIncludeSubGoals ? 'goal is accomplished' : 'instruction is fulfilled'} or failed (Step ${checkGoalStepNumber})**
 <complete success="true|false">...</complete>
 
-**Path B: If ${goalAccomplished.replace('is', 'is not yet')}**
+**Path B: If the ${shouldIncludeSubGoals ? 'goal is NOT complete' : 'instruction is NOT fulfilled'} yet (Step ${actionStepNumber})**
+<!-- Determine next action -->
 <log>...</log>
 <action-type>...</action-type>
 <action-param-json>...</action-param-json>
 
 <!-- OR if there's an error -->
 <error>...</error>
+${shouldIncludeSubGoals ? `
+## Multi-turn Conversation Example
+
+Below is an example of a multi-turn conversation for "fill out the registration form with name 'John' and email 'john@example.com', then return the filled email address":
+
+### Turn 1 - Initial instruction
+
+**User message:**
+<user_instruction>fill out the registration form with name 'John' and email 'john@example.com', then return the filled email address</user_instruction>
+
+**Screenshot:** [Shows a registration form with empty Name and Email fields]
+
+**Your response:**
+<thought>The user wants me to fill out the registration form with specific values and return the email address. I can see the form has two fields: Name and Email. Both are currently empty. I'll break this down into sub-goals and start with the Name field. Note: The instruction is to fill the form only (not submit), and return the email at the end.</thought>
+<update-plan-content>
+  <sub-goal index="1" status="pending">Fill in the Name field with 'John'</sub-goal>
+  <sub-goal index="2" status="pending">Fill in the Email field with 'john@example.com'</sub-goal>
+  <sub-goal index="3" status="pending">Return the filled email address</sub-goal>
+</update-plan-content>
+<log>Click on the Name field to start filling the form</log>
+<action-type>Tap</action-type>
+<action-param-json>
+{
+  "locate": ${locateNameField}
+}
+</action-param-json>
+
+### Turn 2 - After clicking Name field
+
+**User message:**
+The previous action has been executed, here is the latest screenshot. Please continue according to the instruction.
+
+Sub-goals:
+1. Fill in the Name field with 'John' (running)
+2. Fill in the Email field with 'john@example.com' (pending)
+3. Return the filled email address (pending)
+Current sub-goal is: Fill in the Name field with 'John'
+Actions performed for current sub-goal:
+- Click on the Name field to start filling the form
+
+**Screenshot:** [Shows the form with Name field now focused/active]
+
+**Your response:**
+<thought>The Name field is now focused. I need to type 'John' into this field. Current sub-goal is running, will be completed after input.</thought>
+<log>Typing 'John' into the Name field</log>
+<action-type>Input</action-type>
+<action-param-json>
+{
+  "value": "John"
+}
+</action-param-json>
+
+### Turn 3 - After entering name
+
+**User message:**
+The previous action has been executed, here is the latest screenshot. Please continue according to the instruction.
+
+Sub-goals:
+1. Fill in the Name field with 'John' (running)
+2. Fill in the Email field with 'john@example.com' (pending)
+3. Return the filled email address (pending)
+Current sub-goal is: Fill in the Name field with 'John'
+Actions performed for current sub-goal:
+- Click on the Name field to start filling the form
+- Typing 'John' into the Name field
+
+**Screenshot:** [Shows the form with Name field containing 'John']
+
+**Your response:**
+<thought>The Name field now shows 'John'. Sub-goal 1 is complete. Next, I need to fill the Email field for sub-goal 2.</thought>
+<mark-sub-goal-done>
+  <sub-goal index="1" status="finished" />
+</mark-sub-goal-done>
+<memory>Name field has been filled with 'John'</memory>
+<log>Moving to the Email field</log>
+<action-type>Tap</action-type>
+<action-param-json>
+{
+  "locate": ${locateEmailField}
+}
+</action-param-json>
+
+### Turn 4 - After clicking Email field
+
+**User message:**
+The previous action has been executed, here is the latest screenshot. Please continue according to the instruction.
+
+Sub-goals:
+1. Fill in the Name field with 'John' (finished)
+2. Fill in the Email field with 'john@example.com' (running)
+3. Return the filled email address (pending)
+Current sub-goal is: Fill in the Email field with 'john@example.com'
+Actions performed for current sub-goal:
+- Moving to the Email field
+
+**Screenshot:** [Shows the form with Name='John' and Email field focused]
+
+**Your response:**
+<thought>The Email field is now focused. I'll enter 'john@example.com'. After this, sub-goal 2 will be complete and my task will be done.</thought>
+<log>Typing email address into the Email field</log>
+<action-type>Input</action-type>
+<action-param-json>
+{
+  "value": "john@example.com"
+}
+</action-param-json>
+
+### Turn 5 - After entering email (Goal accomplished)
+
+**User message:**
+The previous action has been executed, here is the latest screenshot. Please continue according to the instruction.
+
+Sub-goals:
+1. Fill in the Name field with 'John' (finished)
+2. Fill in the Email field with 'john@example.com' (running)
+3. Return the filled email address (pending)
+Current sub-goal is: Fill in the Email field with 'john@example.com'
+Actions performed for current sub-goal:
+- Moving to the Email field
+- Typing email address into the Email field
+
+**Screenshot:** [Shows the form with Name='John' and Email='john@example.com']
+
+**Your response:**
+<thought>Both fields are now filled: Name shows 'John' and Email shows 'john@example.com'. Sub-goal 2 is complete. The user asked me to return the filled email address, so I need to include 'john@example.com' in my response. All sub-goals are now finished.</thought>
+<mark-sub-goal-done>
+  <sub-goal index="2" status="finished" />
+  <sub-goal index="3" status="finished" />
+</mark-sub-goal-done>
+<complete success="true">john@example.com</complete>
+` : `
+## Multi-turn Conversation Example
+
+Below is an example of a multi-turn conversation for "fill out the registration form with name 'John' and email 'john@example.com', then return the filled email address":
+
+### Turn 1 - Initial instruction
+
+**User message:**
+<user_instruction>fill out the registration form with name 'John' and email 'john@example.com', then return the filled email address</user_instruction>
+
+**Screenshot:** [Shows a registration form with empty Name and Email fields]
+
+**Your response:**
+<thought>The user wants me to fill out the registration form with specific values and return the email address. I can see the form has two fields: Name and Email. Both are currently empty. I should start by clicking on the Name field. Note: The instruction is to fill the form only (not submit), and return the email at the end.</thought>
+<log>Click on the Name field to start filling the form</log>
+<action-type>Tap</action-type>
+<action-param-json>
+{
+  "locate": ${locateNameField}
+}
+</action-param-json>
+
+### Turn 2 - After clicking Name field
+
+**User message:**
+The previous action has been executed, here is the latest screenshot. Please continue according to the instruction.
+
+**Screenshot:** [Shows the form with Name field now focused/active]
+
+**Your response:**
+<thought>The Name field is now focused. I need to type 'John' into this field. After this, I'll need to fill the Email field as well.</thought>
+<log>Typing 'John' into the Name field</log>
+<action-type>Input</action-type>
+<action-param-json>
+{
+  "value": "John"
+}
+</action-param-json>
+
+### Turn 3 - After entering name
+
+**User message:**
+The previous action has been executed, here is the latest screenshot. Please continue according to the instruction.
+
+**Screenshot:** [Shows the form with Name field containing 'John']
+
+**Your response:**
+<thought>The Name field now shows 'John'. Next, I need to fill the Email field with 'john@example.com'. I'll click on the Email field first.</thought>
+<log>Moving to the Email field</log>
+<action-type>Tap</action-type>
+<action-param-json>
+{
+  "locate": ${locateEmailField}
+}
+</action-param-json>
+
+### Turn 4 - After clicking Email field
+
+**User message:**
+The previous action has been executed, here is the latest screenshot. Please continue according to the instruction.
+
+**Screenshot:** [Shows the form with Name='John' and Email field focused]
+
+**Your response:**
+<thought>The Email field is now focused. I'll enter 'john@example.com'. After this, both required fields will be filled and my task will be complete.</thought>
+<log>Typing email address into the Email field</log>
+<action-type>Input</action-type>
+<action-param-json>
+{
+  "value": "john@example.com"
+}
+</action-param-json>
+
+### Turn 5 - After entering email (Instruction fulfilled)
+
+**User message:**
+The previous action has been executed, here is the latest screenshot. Please continue according to the instruction.
+
+**Screenshot:** [Shows the form with Name='John' and Email='john@example.com']
 
-${generateSimplifiedExample(shouldIncludeSubGoals, locateNameField, locateEmailField)}
-`;
+**Your response:**
+<thought>Both fields are now filled: Name shows 'John' and Email shows 'john@example.com'. The user asked me to return the filled email address, so I should include 'john@example.com' in my response. The instruction has been fulfilled.</thought>
+<complete success="true">john@example.com</complete>
+`}`;
 }
 exports.descriptionForAction = __webpack_exports__.descriptionForAction;
 exports.systemPromptToTaskPlanning = __webpack_exports__.systemPromptToTaskPlanning;