scriptoriumadmin/Roo-Code
1
0
Fork 0
mirror of https://github.com/RooVetGit/Roo-Code.git synced 2026-09-05 08:10:14 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

fix: update snapshot tests for new ask_followup_question format

Browse source 
- Updated all 13 snapshot files to match the new nested XML format
- Changed from attribute-based format to nested element format
- Simplified tool description to reduce verbosity
- All tests now passing locally
This commit is contained in:
hannesrudolph 2025-08-09 14:06:33 -06:00 • committed by Merge Resolver
parent d922911b73
commit 0d2e8d3156
13 changed files with 91 additions and 576 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

42
src/core/prompts/__tests__/__snapshots__/add-custom-instructions/architect-mode-prompt.snap generated
View file

@ -274,18 +274,14 @@ Description: Ask the user a question to gather additional information needed to
Parameters:
- question: (required) A clear, specific question addressing the information needed
- follow_up: (required) A list of 2-4 suggested answers, each in its own <suggest> tag with nested <content> element. Suggestions must be complete, actionable answers without placeholders. Optionally include <mode> element to switch modes (code/architect/etc.)
- follow_up: (required) A list of 2-4 suggested answers, each in its own <suggest> tag. Suggestions must be complete, actionable answers without placeholders. Optionally include <mode> to switch modes (code/architect/etc.)
Usage:
<ask_followup_question>
<question>Your question here</question>
<follow_up>
<suggest>
<content>Your suggested answer here</content>
</suggest>
<suggest>
<mode>code</mode>
<content>Implement the solution</content>
</suggest>
<suggest><content>First suggestion</content></suggest>
<suggest><mode>code</mode><content>Action with mode switch</content></suggest>
</follow_up>
</ask_followup_question>
@ -293,33 +289,9 @@ Example:
<ask_followup_question>
<question>What is the path to the frontend-config.json file?</question>
<follow_up>
<suggest>
<content>./src/frontend-config.json</content>
</suggest>
<suggest>
<content>./config/frontend-config.json</content>
</suggest>
<suggest>
<content>./frontend-config.json</content>
</suggest>
</follow_up>
</ask_followup_question>
Example: Asking a question with mode switching options
<ask_followup_question>
<question>How would you like to proceed with this task?</question>
<follow_up>
<suggest>
<mode>code</mode>
<content>Start implementing the solution</content>
</suggest>
<suggest>
<mode>architect</mode>
<content>Plan the architecture first</content>
</suggest>
<suggest>
<content>Continue with more details</content>
</suggest>
<suggest><content>./src/frontend-config.json</content></suggest>
<suggest><content>./config/frontend-config.json</content></suggest>
<suggest><content>./frontend-config.json</content></suggest>
</follow_up>
</ask_followup_question>
## attempt_completion

42
src/core/prompts/__tests__/__snapshots__/add-custom-instructions/ask-mode-prompt.snap generated
View file

@ -171,18 +171,14 @@ Description: Ask the user a question to gather additional information needed to
Parameters:
- question: (required) A clear, specific question addressing the information needed
- follow_up: (required) A list of 2-4 suggested answers, each in its own <suggest> tag with nested <content> element. Suggestions must be complete, actionable answers without placeholders. Optionally include <mode> element to switch modes (code/architect/etc.)
- follow_up: (required) A list of 2-4 suggested answers, each in its own <suggest> tag. Suggestions must be complete, actionable answers without placeholders. Optionally include <mode> to switch modes (code/architect/etc.)
Usage:
<ask_followup_question>
<question>Your question here</question>
<follow_up>
<suggest>
<content>Your suggested answer here</content>
</suggest>
<suggest>
<mode>code</mode>
<content>Implement the solution</content>
</suggest>
<suggest><content>First suggestion</content></suggest>
<suggest><mode>code</mode><content>Action with mode switch</content></suggest>
</follow_up>
</ask_followup_question>
@ -190,33 +186,9 @@ Example:
<ask_followup_question>
<question>What is the path to the frontend-config.json file?</question>
<follow_up>
<suggest>
<content>./src/frontend-config.json</content>
</suggest>
<suggest>
<content>./config/frontend-config.json</content>
</suggest>
<suggest>
<content>./frontend-config.json</content>
</suggest>
</follow_up>
</ask_followup_question>
Example: Asking a question with mode switching options
<ask_followup_question>
<question>How would you like to proceed with this task?</question>
<follow_up>
<suggest>
<mode>code</mode>
<content>Start implementing the solution</content>
</suggest>
<suggest>
<mode>architect</mode>
<content>Plan the architecture first</content>
</suggest>
<suggest>
<content>Continue with more details</content>
</suggest>
<suggest><content>./src/frontend-config.json</content></suggest>
<suggest><content>./config/frontend-config.json</content></suggest>
<suggest><content>./frontend-config.json</content></suggest>
</follow_up>
</ask_followup_question>
## attempt_completion

53
src/core/prompts/__tests__/__snapshots__/add-custom-instructions/mcp-server-creation-disabled.snap generated
View file

@ -273,27 +273,14 @@ Description: Ask the user a question to gather additional information needed to
Parameters:
- question: (required) A clear, specific question addressing the information needed
- follow_up: (required) A list of 2-4 suggested answers, each in its own <suggest> tag with nested <content> element. Suggestions must be complete, actionable answers without placeholders. Optionally include <mode> element to switch modes (code/architect/etc.)
- question: (required) The question to ask the user. This should be a clear, specific question that addresses the information you need.
- follow_up: (required) A list of 2-4 suggested answers that logically follow from the question, ordered by priority or logical sequence. Each suggestion must:
1. Be provided in its own <suggest> tag
2. Be specific, actionable, and directly related to the completed task
3. Be a complete answer to the question - the user should not need to provide additional information or fill in any missing details. DO NOT include placeholders with brackets or parentheses.
4. Optionally include a <mode> element to switch to a specific mode when the suggestion is selected
- When using the mode element, focus the suggestion text on the action to be taken rather than mentioning the mode switch, as the mode change is handled automatically and indicated by a visual badge
- follow_up: (required) A list of 2-4 suggested answers, each in its own <suggest> tag. Suggestions must be complete, actionable answers without placeholders. Optionally include <mode> to switch modes (code/architect/etc.)
Usage:
<ask_followup_question>
<question>Your question here</question>
<follow_up>
- question: (required) A clear, specific question addressing the information needed
- follow_up: (required) A list of 2-4 suggested answers, each in its own <suggest> tag with nested <content> element. Suggestions must be complete, actionable answers without placeholders. Optionally include <mode> element to switch modes (code/architect/etc.)
<suggest>
<content>Your suggested answer here</content>
</suggest>
<suggest>
<mode>code</mode>
<content>Implement the solution</content>
</suggest>
<suggest><content>First suggestion</content></suggest>
<suggest><mode>code</mode><content>Action with mode switch</content></suggest>
</follow_up>
</ask_followup_question>
@ -301,35 +288,9 @@ Example:
<ask_followup_question>
<question>What is the path to the frontend-config.json file?</question>
<follow_up>
<suggest>
<content>./src/frontend-config.json</content>
</suggest>
<suggest>
<content>./config/frontend-config.json</content>
</suggest>
<suggest>
<content>./frontend-config.json</content>
</suggest>
</follow_up>
</ask_followup_question>
- question: (required) A clear, specific question addressing the information needed
- follow_up: (required) A list of 2-4 suggested answers, each in its own <suggest> tag with nested <content> element. Suggestions must be complete, actionable answers without placeholders. Optionally include <mode> element to switch modes (code/architect/etc.)
Example: Asking a question with mode switching options
<ask_followup_question>
<question>How would you like to proceed with this task?</question>
<follow_up>
<suggest>
<mode>code</mode>
<content>Start implementing the solution</content>
</suggest>
<suggest>
<mode>architect</mode>
<content>Plan the architecture first</content>
</suggest>
<suggest>
<content>Continue with more details</content>
</suggest>
<suggest><content>./src/frontend-config.json</content></suggest>
<suggest><content>./config/frontend-config.json</content></suggest>
<suggest><content>./frontend-config.json</content></suggest>
</follow_up>
</ask_followup_question>

53
src/core/prompts/__tests__/__snapshots__/add-custom-instructions/mcp-server-creation-enabled.snap generated
View file

@ -323,27 +323,14 @@ Description: Ask the user a question to gather additional information needed to
Parameters:
- question: (required) A clear, specific question addressing the information needed
- follow_up: (required) A list of 2-4 suggested answers, each in its own <suggest> tag with nested <content> element. Suggestions must be complete, actionable answers without placeholders. Optionally include <mode> element to switch modes (code/architect/etc.)
- question: (required) The question to ask the user. This should be a clear, specific question that addresses the information you need.
- follow_up: (required) A list of 2-4 suggested answers that logically follow from the question, ordered by priority or logical sequence. Each suggestion must:
1. Be provided in its own <suggest> tag
2. Be specific, actionable, and directly related to the completed task
3. Be a complete answer to the question - the user should not need to provide additional information or fill in any missing details. DO NOT include placeholders with brackets or parentheses.
4. Optionally include a <mode> element to switch to a specific mode when the suggestion is selected
- When using the mode element, focus the suggestion text on the action to be taken rather than mentioning the mode switch, as the mode change is handled automatically and indicated by a visual badge
- follow_up: (required) A list of 2-4 suggested answers, each in its own <suggest> tag. Suggestions must be complete, actionable answers without placeholders. Optionally include <mode> to switch modes (code/architect/etc.)
Usage:
<ask_followup_question>
<question>Your question here</question>
<follow_up>
- question: (required) A clear, specific question addressing the information needed
- follow_up: (required) A list of 2-4 suggested answers, each in its own <suggest> tag with nested <content> element. Suggestions must be complete, actionable answers without placeholders. Optionally include <mode> element to switch modes (code/architect/etc.)
<suggest>
<content>Your suggested answer here</content>
</suggest>
<suggest>
<mode>code</mode>
<content>Implement the solution</content>
</suggest>
<suggest><content>First suggestion</content></suggest>
<suggest><mode>code</mode><content>Action with mode switch</content></suggest>
</follow_up>
</ask_followup_question>
@ -351,35 +338,9 @@ Example:
<ask_followup_question>
<question>What is the path to the frontend-config.json file?</question>
<follow_up>
<suggest>
<content>./src/frontend-config.json</content>
</suggest>
<suggest>
<content>./config/frontend-config.json</content>
</suggest>
<suggest>
<content>./frontend-config.json</content>
</suggest>
</follow_up>
</ask_followup_question>
- question: (required) A clear, specific question addressing the information needed
- follow_up: (required) A list of 2-4 suggested answers, each in its own <suggest> tag with nested <content> element. Suggestions must be complete, actionable answers without placeholders. Optionally include <mode> element to switch modes (code/architect/etc.)
Example: Asking a question with mode switching options
<ask_followup_question>
<question>How would you like to proceed with this task?</question>
<follow_up>
<suggest>
<mode>code</mode>
<content>Start implementing the solution</content>
</suggest>
<suggest>
<mode>architect</mode>
<content>Plan the architecture first</content>
</suggest>
<suggest>
<content>Continue with more details</content>
</suggest>
<suggest><content>./src/frontend-config.json</content></suggest>
<suggest><content>./config/frontend-config.json</content></suggest>
<suggest><content>./frontend-config.json</content></suggest>
</follow_up>
</ask_followup_question>

53
src/core/prompts/__tests__/__snapshots__/add-custom-instructions/partial-reads-enabled.snap generated
View file

@ -279,27 +279,14 @@ Description: Ask the user a question to gather additional information needed to
Parameters:
- question: (required) A clear, specific question addressing the information needed
- follow_up: (required) A list of 2-4 suggested answers, each in its own <suggest> tag with nested <content> element. Suggestions must be complete, actionable answers without placeholders. Optionally include <mode> element to switch modes (code/architect/etc.)
- question: (required) The question to ask the user. This should be a clear, specific question that addresses the information you need.
- follow_up: (required) A list of 2-4 suggested answers that logically follow from the question, ordered by priority or logical sequence. Each suggestion must:
1. Be provided in its own <suggest> tag
2. Be specific, actionable, and directly related to the completed task
3. Be a complete answer to the question - the user should not need to provide additional information or fill in any missing details. DO NOT include placeholders with brackets or parentheses.
4. Optionally include a <mode> element to switch to a specific mode when the suggestion is selected
- When using the mode element, focus the suggestion text on the action to be taken rather than mentioning the mode switch, as the mode change is handled automatically and indicated by a visual badge
- follow_up: (required) A list of 2-4 suggested answers, each in its own <suggest> tag. Suggestions must be complete, actionable answers without placeholders. Optionally include <mode> to switch modes (code/architect/etc.)
Usage:
<ask_followup_question>
<question>Your question here</question>
<follow_up>
- question: (required) A clear, specific question addressing the information needed
- follow_up: (required) A list of 2-4 suggested answers, each in its own <suggest> tag with nested <content> element. Suggestions must be complete, actionable answers without placeholders. Optionally include <mode> element to switch modes (code/architect/etc.)
<suggest>
<content>Your suggested answer here</content>
</suggest>
<suggest>
<mode>code</mode>
<content>Implement the solution</content>
</suggest>
<suggest><content>First suggestion</content></suggest>
<suggest><mode>code</mode><content>Action with mode switch</content></suggest>
</follow_up>
</ask_followup_question>
@ -307,35 +294,9 @@ Example:
<ask_followup_question>
<question>What is the path to the frontend-config.json file?</question>
<follow_up>
<suggest>
<content>./src/frontend-config.json</content>
</suggest>
<suggest>
<content>./config/frontend-config.json</content>
</suggest>
<suggest>
<content>./frontend-config.json</content>
</suggest>
</follow_up>
</ask_followup_question>
- question: (required) A clear, specific question addressing the information needed
- follow_up: (required) A list of 2-4 suggested answers, each in its own <suggest> tag with nested <content> element. Suggestions must be complete, actionable answers without placeholders. Optionally include <mode> element to switch modes (code/architect/etc.)
Example: Asking a question with mode switching options
<ask_followup_question>
<question>How would you like to proceed with this task?</question>
<follow_up>
<suggest>
<mode>code</mode>
<content>Start implementing the solution</content>
</suggest>
<suggest>
<mode>architect</mode>
<content>Plan the architecture first</content>
</suggest>
<suggest>
<content>Continue with more details</content>
</suggest>
<suggest><content>./src/frontend-config.json</content></suggest>
<suggest><content>./config/frontend-config.json</content></suggest>
<suggest><content>./frontend-config.json</content></suggest>
</follow_up>
</ask_followup_question>

53
src/core/prompts/__tests__/__snapshots__/system-prompt/consistent-system-prompt.snap generated
View file

@ -274,27 +274,14 @@ Description: Ask the user a question to gather additional information needed to
Parameters:
- question: (required) A clear, specific question addressing the information needed
- follow_up: (required) A list of 2-4 suggested answers, each in its own <suggest> tag with nested <content> element. Suggestions must be complete, actionable answers without placeholders. Optionally include <mode> element to switch modes (code/architect/etc.)
- question: (required) The question to ask the user. This should be a clear, specific question that addresses the information you need.
- follow_up: (required) A list of 2-4 suggested answers that logically follow from the question, ordered by priority or logical sequence. Each suggestion must:
1. Be provided in its own <suggest> tag
2. Be specific, actionable, and directly related to the completed task
3. Be a complete answer to the question - the user should not need to provide additional information or fill in any missing details. DO NOT include placeholders with brackets or parentheses.
4. Optionally include a <mode> element to switch to a specific mode when the suggestion is selected
- When using the mode element, focus the suggestion text on the action to be taken rather than mentioning the mode switch, as the mode change is handled automatically and indicated by a visual badge
- follow_up: (required) A list of 2-4 suggested answers, each in its own <suggest> tag. Suggestions must be complete, actionable answers without placeholders. Optionally include <mode> to switch modes (code/architect/etc.)
Usage:
<ask_followup_question>
<question>Your question here</question>
<follow_up>
- question: (required) A clear, specific question addressing the information needed
- follow_up: (required) A list of 2-4 suggested answers, each in its own <suggest> tag with nested <content> element. Suggestions must be complete, actionable answers without placeholders. Optionally include <mode> element to switch modes (code/architect/etc.)
<suggest>
<content>Your suggested answer here</content>
</suggest>
<suggest>
<mode>code</mode>
<content>Implement the solution</content>
</suggest>
<suggest><content>First suggestion</content></suggest>
<suggest><mode>code</mode><content>Action with mode switch</content></suggest>
</follow_up>
</ask_followup_question>
@ -302,35 +289,9 @@ Example:
<ask_followup_question>
<question>What is the path to the frontend-config.json file?</question>
<follow_up>
<suggest>
<content>./src/frontend-config.json</content>
</suggest>
<suggest>
<content>./config/frontend-config.json</content>
</suggest>
<suggest>
<content>./frontend-config.json</content>
</suggest>
</follow_up>
</ask_followup_question>
- question: (required) A clear, specific question addressing the information needed
- follow_up: (required) A list of 2-4 suggested answers, each in its own <suggest> tag with nested <content> element. Suggestions must be complete, actionable answers without placeholders. Optionally include <mode> element to switch modes (code/architect/etc.)
Example: Asking a question with mode switching options
<ask_followup_question>
<question>How would you like to proceed with this task?</question>
<follow_up>
<suggest>
<mode>code</mode>
<content>Start implementing the solution</content>
</suggest>
<suggest>
<mode>architect</mode>
<content>Plan the architecture first</content>
</suggest>
<suggest>
<content>Continue with more details</content>
</suggest>
<suggest><content>./src/frontend-config.json</content></suggest>
<suggest><content>./config/frontend-config.json</content></suggest>
<suggest><content>./frontend-config.json</content></suggest>
</follow_up>
</ask_followup_question>

53
src/core/prompts/__tests__/__snapshots__/system-prompt/with-computer-use-support.snap generated
View file

@ -327,27 +327,14 @@ Description: Ask the user a question to gather additional information needed to
Parameters:
- question: (required) A clear, specific question addressing the information needed
- follow_up: (required) A list of 2-4 suggested answers, each in its own <suggest> tag with nested <content> element. Suggestions must be complete, actionable answers without placeholders. Optionally include <mode> element to switch modes (code/architect/etc.)
- question: (required) The question to ask the user. This should be a clear, specific question that addresses the information you need.
- follow_up: (required) A list of 2-4 suggested answers that logically follow from the question, ordered by priority or logical sequence. Each suggestion must:
1. Be provided in its own <suggest> tag
2. Be specific, actionable, and directly related to the completed task
3. Be a complete answer to the question - the user should not need to provide additional information or fill in any missing details. DO NOT include placeholders with brackets or parentheses.
4. Optionally include a <mode> element to switch to a specific mode when the suggestion is selected
- When using the mode element, focus the suggestion text on the action to be taken rather than mentioning the mode switch, as the mode change is handled automatically and indicated by a visual badge
- follow_up: (required) A list of 2-4 suggested answers, each in its own <suggest> tag. Suggestions must be complete, actionable answers without placeholders. Optionally include <mode> to switch modes (code/architect/etc.)
Usage:
<ask_followup_question>
<question>Your question here</question>
<follow_up>
- question: (required) A clear, specific question addressing the information needed
- follow_up: (required) A list of 2-4 suggested answers, each in its own <suggest> tag with nested <content> element. Suggestions must be complete, actionable answers without placeholders. Optionally include <mode> element to switch modes (code/architect/etc.)
<suggest>
<content>Your suggested answer here</content>
</suggest>
<suggest>
<mode>code</mode>
<content>Implement the solution</content>
</suggest>
<suggest><content>First suggestion</content></suggest>
<suggest><mode>code</mode><content>Action with mode switch</content></suggest>
</follow_up>
</ask_followup_question>
@ -355,35 +342,9 @@ Example:
<ask_followup_question>
<question>What is the path to the frontend-config.json file?</question>
<follow_up>
<suggest>
<content>./src/frontend-config.json</content>
</suggest>
<suggest>
<content>./config/frontend-config.json</content>
</suggest>
<suggest>
<content>./frontend-config.json</content>
</suggest>
</follow_up>
</ask_followup_question>
- question: (required) A clear, specific question addressing the information needed
- follow_up: (required) A list of 2-4 suggested answers, each in its own <suggest> tag with nested <content> element. Suggestions must be complete, actionable answers without placeholders. Optionally include <mode> element to switch modes (code/architect/etc.)
Example: Asking a question with mode switching options
<ask_followup_question>
<question>How would you like to proceed with this task?</question>
<follow_up>
<suggest>
<mode>code</mode>
<content>Start implementing the solution</content>
</suggest>
<suggest>
<mode>architect</mode>
<content>Plan the architecture first</content>
</suggest>
<suggest>
<content>Continue with more details</content>
</suggest>
<suggest><content>./src/frontend-config.json</content></suggest>
<suggest><content>./config/frontend-config.json</content></suggest>
<suggest><content>./frontend-config.json</content></suggest>
</follow_up>
</ask_followup_question>

53
src/core/prompts/__tests__/__snapshots__/system-prompt/with-diff-enabled-false.snap generated
View file

@ -274,27 +274,14 @@ Description: Ask the user a question to gather additional information needed to
Parameters:
- question: (required) A clear, specific question addressing the information needed
- follow_up: (required) A list of 2-4 suggested answers, each in its own <suggest> tag with nested <content> element. Suggestions must be complete, actionable answers without placeholders. Optionally include <mode> element to switch modes (code/architect/etc.)
- question: (required) The question to ask the user. This should be a clear, specific question that addresses the information you need.
- follow_up: (required) A list of 2-4 suggested answers that logically follow from the question, ordered by priority or logical sequence. Each suggestion must:
1. Be provided in its own <suggest> tag
2. Be specific, actionable, and directly related to the completed task
3. Be a complete answer to the question - the user should not need to provide additional information or fill in any missing details. DO NOT include placeholders with brackets or parentheses.
4. Optionally include a <mode> element to switch to a specific mode when the suggestion is selected
- When using the mode element, focus the suggestion text on the action to be taken rather than mentioning the mode switch, as the mode change is handled automatically and indicated by a visual badge
- follow_up: (required) A list of 2-4 suggested answers, each in its own <suggest> tag. Suggestions must be complete, actionable answers without placeholders. Optionally include <mode> to switch modes (code/architect/etc.)
Usage:
<ask_followup_question>
<question>Your question here</question>
<follow_up>
- question: (required) A clear, specific question addressing the information needed
- follow_up: (required) A list of 2-4 suggested answers, each in its own <suggest> tag with nested <content> element. Suggestions must be complete, actionable answers without placeholders. Optionally include <mode> element to switch modes (code/architect/etc.)
<suggest>
<content>Your suggested answer here</content>
</suggest>
<suggest>
<mode>code</mode>
<content>Implement the solution</content>
</suggest>
<suggest><content>First suggestion</content></suggest>
<suggest><mode>code</mode><content>Action with mode switch</content></suggest>
</follow_up>
</ask_followup_question>
@ -302,35 +289,9 @@ Example:
<ask_followup_question>
<question>What is the path to the frontend-config.json file?</question>
<follow_up>
<suggest>
<content>./src/frontend-config.json</content>
</suggest>
<suggest>
<content>./config/frontend-config.json</content>
</suggest>
<suggest>
<content>./frontend-config.json</content>
</suggest>
</follow_up>
</ask_followup_question>
- question: (required) A clear, specific question addressing the information needed
- follow_up: (required) A list of 2-4 suggested answers, each in its own <suggest> tag with nested <content> element. Suggestions must be complete, actionable answers without placeholders. Optionally include <mode> element to switch modes (code/architect/etc.)
Example: Asking a question with mode switching options
<ask_followup_question>
<question>How would you like to proceed with this task?</question>
<follow_up>
<suggest>
<mode>code</mode>
<content>Start implementing the solution</content>
</suggest>
<suggest>
<mode>architect</mode>
<content>Plan the architecture first</content>
</suggest>
<suggest>
<content>Continue with more details</content>
</suggest>
<suggest><content>./src/frontend-config.json</content></suggest>
<suggest><content>./config/frontend-config.json</content></suggest>
<suggest><content>./frontend-config.json</content></suggest>
</follow_up>
</ask_followup_question>

53
src/core/prompts/__tests__/__snapshots__/system-prompt/with-diff-enabled-true.snap generated
View file

@ -362,27 +362,14 @@ Description: Ask the user a question to gather additional information needed to
Parameters:
- question: (required) A clear, specific question addressing the information needed
- follow_up: (required) A list of 2-4 suggested answers, each in its own <suggest> tag with nested <content> element. Suggestions must be complete, actionable answers without placeholders. Optionally include <mode> element to switch modes (code/architect/etc.)
- question: (required) The question to ask the user. This should be a clear, specific question that addresses the information you need.
- follow_up: (required) A list of 2-4 suggested answers that logically follow from the question, ordered by priority or logical sequence. Each suggestion must:
1. Be provided in its own <suggest> tag
2. Be specific, actionable, and directly related to the completed task
3. Be a complete answer to the question - the user should not need to provide additional information or fill in any missing details. DO NOT include placeholders with brackets or parentheses.
4. Optionally include a <mode> element to switch to a specific mode when the suggestion is selected
- When using the mode element, focus the suggestion text on the action to be taken rather than mentioning the mode switch, as the mode change is handled automatically and indicated by a visual badge
- follow_up: (required) A list of 2-4 suggested answers, each in its own <suggest> tag. Suggestions must be complete, actionable answers without placeholders. Optionally include <mode> to switch modes (code/architect/etc.)
Usage:
<ask_followup_question>
<question>Your question here</question>
<follow_up>
- question: (required) A clear, specific question addressing the information needed
- follow_up: (required) A list of 2-4 suggested answers, each in its own <suggest> tag with nested <content> element. Suggestions must be complete, actionable answers without placeholders. Optionally include <mode> element to switch modes (code/architect/etc.)
<suggest>
<content>Your suggested answer here</content>
</suggest>
<suggest>
<mode>code</mode>
<content>Implement the solution</content>
</suggest>
<suggest><content>First suggestion</content></suggest>
<suggest><mode>code</mode><content>Action with mode switch</content></suggest>
</follow_up>
</ask_followup_question>
@ -390,35 +377,9 @@ Example:
<ask_followup_question>
<question>What is the path to the frontend-config.json file?</question>
<follow_up>
<suggest>
<content>./src/frontend-config.json</content>
</suggest>
<suggest>
<content>./config/frontend-config.json</content>
</suggest>
<suggest>
<content>./frontend-config.json</content>
</suggest>
</follow_up>
</ask_followup_question>
- question: (required) A clear, specific question addressing the information needed
- follow_up: (required) A list of 2-4 suggested answers, each in its own <suggest> tag with nested <content> element. Suggestions must be complete, actionable answers without placeholders. Optionally include <mode> element to switch modes (code/architect/etc.)
Example: Asking a question with mode switching options
<ask_followup_question>
<question>How would you like to proceed with this task?</question>
<follow_up>
<suggest>
<mode>code</mode>
<content>Start implementing the solution</content>
</suggest>
<suggest>
<mode>architect</mode>
<content>Plan the architecture first</content>
</suggest>
<suggest>
<content>Continue with more details</content>
</suggest>
<suggest><content>./src/frontend-config.json</content></suggest>
<suggest><content>./config/frontend-config.json</content></suggest>
<suggest><content>./frontend-config.json</content></suggest>
</follow_up>
</ask_followup_question>

53
src/core/prompts/__tests__/__snapshots__/system-prompt/with-diff-enabled-undefined.snap generated
View file

@ -274,27 +274,14 @@ Description: Ask the user a question to gather additional information needed to
Parameters:
- question: (required) A clear, specific question addressing the information needed
- follow_up: (required) A list of 2-4 suggested answers, each in its own <suggest> tag with nested <content> element. Suggestions must be complete, actionable answers without placeholders. Optionally include <mode> element to switch modes (code/architect/etc.)
- question: (required) The question to ask the user. This should be a clear, specific question that addresses the information you need.
- follow_up: (required) A list of 2-4 suggested answers that logically follow from the question, ordered by priority or logical sequence. Each suggestion must:
1. Be provided in its own <suggest> tag
2. Be specific, actionable, and directly related to the completed task
3. Be a complete answer to the question - the user should not need to provide additional information or fill in any missing details. DO NOT include placeholders with brackets or parentheses.
4. Optionally include a <mode> element to switch to a specific mode when the suggestion is selected
- When using the mode element, focus the suggestion text on the action to be taken rather than mentioning the mode switch, as the mode change is handled automatically and indicated by a visual badge
- follow_up: (required) A list of 2-4 suggested answers, each in its own <suggest> tag. Suggestions must be complete, actionable answers without placeholders. Optionally include <mode> to switch modes (code/architect/etc.)
Usage:
<ask_followup_question>
<question>Your question here</question>
<follow_up>
- question: (required) A clear, specific question addressing the information needed
- follow_up: (required) A list of 2-4 suggested answers, each in its own <suggest> tag with nested <content> element. Suggestions must be complete, actionable answers without placeholders. Optionally include <mode> element to switch modes (code/architect/etc.)
<suggest>
<content>Your suggested answer here</content>
</suggest>
<suggest>
<mode>code</mode>
<content>Implement the solution</content>
</suggest>
<suggest><content>First suggestion</content></suggest>
<suggest><mode>code</mode><content>Action with mode switch</content></suggest>
</follow_up>
</ask_followup_question>
@ -302,35 +289,9 @@ Example:
<ask_followup_question>
<question>What is the path to the frontend-config.json file?</question>
<follow_up>
<suggest>
<content>./src/frontend-config.json</content>
</suggest>
<suggest>
<content>./config/frontend-config.json</content>
</suggest>
<suggest>
<content>./frontend-config.json</content>
</suggest>
</follow_up>
</ask_followup_question>
- question: (required) A clear, specific question addressing the information needed
- follow_up: (required) A list of 2-4 suggested answers, each in its own <suggest> tag with nested <content> element. Suggestions must be complete, actionable answers without placeholders. Optionally include <mode> element to switch modes (code/architect/etc.)
Example: Asking a question with mode switching options
<ask_followup_question>
<question>How would you like to proceed with this task?</question>
<follow_up>
<suggest>
<mode>code</mode>
<content>Start implementing the solution</content>
</suggest>
<suggest>
<mode>architect</mode>
<content>Plan the architecture first</content>
</suggest>
<suggest>
<content>Continue with more details</content>
</suggest>
<suggest><content>./src/frontend-config.json</content></suggest>
<suggest><content>./config/frontend-config.json</content></suggest>
<suggest><content>./frontend-config.json</content></suggest>
</follow_up>
</ask_followup_question>

53
src/core/prompts/__tests__/__snapshots__/system-prompt/with-different-viewport-size.snap generated
View file

@ -327,27 +327,14 @@ Description: Ask the user a question to gather additional information needed to
Parameters:
- question: (required) A clear, specific question addressing the information needed
- follow_up: (required) A list of 2-4 suggested answers, each in its own <suggest> tag with nested <content> element. Suggestions must be complete, actionable answers without placeholders. Optionally include <mode> element to switch modes (code/architect/etc.)
- question: (required) The question to ask the user. This should be a clear, specific question that addresses the information you need.
- follow_up: (required) A list of 2-4 suggested answers that logically follow from the question, ordered by priority or logical sequence. Each suggestion must:
1. Be provided in its own <suggest> tag
2. Be specific, actionable, and directly related to the completed task
3. Be a complete answer to the question - the user should not need to provide additional information or fill in any missing details. DO NOT include placeholders with brackets or parentheses.
4. Optionally include a <mode> element to switch to a specific mode when the suggestion is selected
- When using the mode element, focus the suggestion text on the action to be taken rather than mentioning the mode switch, as the mode change is handled automatically and indicated by a visual badge
- follow_up: (required) A list of 2-4 suggested answers, each in its own <suggest> tag. Suggestions must be complete, actionable answers without placeholders. Optionally include <mode> to switch modes (code/architect/etc.)
Usage:
<ask_followup_question>
<question>Your question here</question>
<follow_up>
- question: (required) A clear, specific question addressing the information needed
- follow_up: (required) A list of 2-4 suggested answers, each in its own <suggest> tag with nested <content> element. Suggestions must be complete, actionable answers without placeholders. Optionally include <mode> element to switch modes (code/architect/etc.)
<suggest>
<content>Your suggested answer here</content>
</suggest>
<suggest>
<mode>code</mode>
<content>Implement the solution</content>
</suggest>
<suggest><content>First suggestion</content></suggest>
<suggest><mode>code</mode><content>Action with mode switch</content></suggest>
</follow_up>
</ask_followup_question>
@ -355,35 +342,9 @@ Example:
<ask_followup_question>
<question>What is the path to the frontend-config.json file?</question>
<follow_up>
<suggest>
<content>./src/frontend-config.json</content>
</suggest>
<suggest>
<content>./config/frontend-config.json</content>
</suggest>
<suggest>
<content>./frontend-config.json</content>
</suggest>
</follow_up>
</ask_followup_question>
- question: (required) A clear, specific question addressing the information needed
- follow_up: (required) A list of 2-4 suggested answers, each in its own <suggest> tag with nested <content> element. Suggestions must be complete, actionable answers without placeholders. Optionally include <mode> element to switch modes (code/architect/etc.)
Example: Asking a question with mode switching options
<ask_followup_question>
<question>How would you like to proceed with this task?</question>
<follow_up>
<suggest>
<mode>code</mode>
<content>Start implementing the solution</content>
</suggest>
<suggest>
<mode>architect</mode>
<content>Plan the architecture first</content>
</suggest>
<suggest>
<content>Continue with more details</content>
</suggest>
<suggest><content>./src/frontend-config.json</content></suggest>
<suggest><content>./config/frontend-config.json</content></suggest>
<suggest><content>./frontend-config.json</content></suggest>
</follow_up>
</ask_followup_question>

53
src/core/prompts/__tests__/__snapshots__/system-prompt/with-mcp-hub-provided.snap generated
View file

@ -323,27 +323,14 @@ Description: Ask the user a question to gather additional information needed to
Parameters:
- question: (required) A clear, specific question addressing the information needed
- follow_up: (required) A list of 2-4 suggested answers, each in its own <suggest> tag with nested <content> element. Suggestions must be complete, actionable answers without placeholders. Optionally include <mode> element to switch modes (code/architect/etc.)
- question: (required) The question to ask the user. This should be a clear, specific question that addresses the information you need.
- follow_up: (required) A list of 2-4 suggested answers that logically follow from the question, ordered by priority or logical sequence. Each suggestion must:
1. Be provided in its own <suggest> tag
2. Be specific, actionable, and directly related to the completed task
3. Be a complete answer to the question - the user should not need to provide additional information or fill in any missing details. DO NOT include placeholders with brackets or parentheses.
4. Optionally include a <mode> element to switch to a specific mode when the suggestion is selected
- When using the mode element, focus the suggestion text on the action to be taken rather than mentioning the mode switch, as the mode change is handled automatically and indicated by a visual badge
- follow_up: (required) A list of 2-4 suggested answers, each in its own <suggest> tag. Suggestions must be complete, actionable answers without placeholders. Optionally include <mode> to switch modes (code/architect/etc.)
Usage:
<ask_followup_question>
<question>Your question here</question>
<follow_up>
- question: (required) A clear, specific question addressing the information needed
- follow_up: (required) A list of 2-4 suggested answers, each in its own <suggest> tag with nested <content> element. Suggestions must be complete, actionable answers without placeholders. Optionally include <mode> element to switch modes (code/architect/etc.)
<suggest>
<content>Your suggested answer here</content>
</suggest>
<suggest>
<mode>code</mode>
<content>Implement the solution</content>
</suggest>
<suggest><content>First suggestion</content></suggest>
<suggest><mode>code</mode><content>Action with mode switch</content></suggest>
</follow_up>
</ask_followup_question>
@ -351,35 +338,9 @@ Example:
<ask_followup_question>
<question>What is the path to the frontend-config.json file?</question>
<follow_up>
<suggest>
<content>./src/frontend-config.json</content>
</suggest>
<suggest>
<content>./config/frontend-config.json</content>
</suggest>
<suggest>
<content>./frontend-config.json</content>
</suggest>
</follow_up>
</ask_followup_question>
- question: (required) A clear, specific question addressing the information needed
- follow_up: (required) A list of 2-4 suggested answers, each in its own <suggest> tag with nested <content> element. Suggestions must be complete, actionable answers without placeholders. Optionally include <mode> element to switch modes (code/architect/etc.)
Example: Asking a question with mode switching options
<ask_followup_question>
<question>How would you like to proceed with this task?</question>
<follow_up>
<suggest>
<mode>code</mode>
<content>Start implementing the solution</content>
</suggest>
<suggest>
<mode>architect</mode>
<content>Plan the architecture first</content>
</suggest>
<suggest>
<content>Continue with more details</content>
</suggest>
<suggest><content>./src/frontend-config.json</content></suggest>
<suggest><content>./config/frontend-config.json</content></suggest>
<suggest><content>./frontend-config.json</content></suggest>
</follow_up>
</ask_followup_question>

53
src/core/prompts/__tests__/__snapshots__/system-prompt/with-undefined-mcp-hub.snap generated
View file

@ -274,27 +274,14 @@ Description: Ask the user a question to gather additional information needed to
Parameters:
- question: (required) A clear, specific question addressing the information needed
- follow_up: (required) A list of 2-4 suggested answers, each in its own <suggest> tag with nested <content> element. Suggestions must be complete, actionable answers without placeholders. Optionally include <mode> element to switch modes (code/architect/etc.)
- question: (required) The question to ask the user. This should be a clear, specific question that addresses the information you need.
- follow_up: (required) A list of 2-4 suggested answers that logically follow from the question, ordered by priority or logical sequence. Each suggestion must:
1. Be provided in its own <suggest> tag
2. Be specific, actionable, and directly related to the completed task
3. Be a complete answer to the question - the user should not need to provide additional information or fill in any missing details. DO NOT include placeholders with brackets or parentheses.
4. Optionally include a <mode> element to switch to a specific mode when the suggestion is selected
- When using the mode element, focus the suggestion text on the action to be taken rather than mentioning the mode switch, as the mode change is handled automatically and indicated by a visual badge
- follow_up: (required) A list of 2-4 suggested answers, each in its own <suggest> tag. Suggestions must be complete, actionable answers without placeholders. Optionally include <mode> to switch modes (code/architect/etc.)
Usage:
<ask_followup_question>
<question>Your question here</question>
<follow_up>
- question: (required) A clear, specific question addressing the information needed
- follow_up: (required) A list of 2-4 suggested answers, each in its own <suggest> tag with nested <content> element. Suggestions must be complete, actionable answers without placeholders. Optionally include <mode> element to switch modes (code/architect/etc.)
<suggest>
<content>Your suggested answer here</content>
</suggest>
<suggest>
<mode>code</mode>
<content>Implement the solution</content>
</suggest>
<suggest><content>First suggestion</content></suggest>
<suggest><mode>code</mode><content>Action with mode switch</content></suggest>
</follow_up>
</ask_followup_question>
@ -302,35 +289,9 @@ Example:
<ask_followup_question>
<question>What is the path to the frontend-config.json file?</question>
<follow_up>
<suggest>
<content>./src/frontend-config.json</content>
</suggest>
<suggest>
<content>./config/frontend-config.json</content>
</suggest>
<suggest>
<content>./frontend-config.json</content>
</suggest>
</follow_up>
</ask_followup_question>
- question: (required) A clear, specific question addressing the information needed
- follow_up: (required) A list of 2-4 suggested answers, each in its own <suggest> tag with nested <content> element. Suggestions must be complete, actionable answers without placeholders. Optionally include <mode> element to switch modes (code/architect/etc.)
Example: Asking a question with mode switching options
<ask_followup_question>
<question>How would you like to proceed with this task?</question>
<follow_up>
<suggest>
<mode>code</mode>
<content>Start implementing the solution</content>
</suggest>
<suggest>
<mode>architect</mode>
<content>Plan the architecture first</content>
</suggest>
<suggest>
<content>Continue with more details</content>
</suggest>
<suggest><content>./src/frontend-config.json</content></suggest>
<suggest><content>./config/frontend-config.json</content></suggest>
<suggest><content>./frontend-config.json</content></suggest>
</follow_up>
</ask_followup_question>