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

test: update snapshots for new ask_followup_question format

Browse source
This commit is contained in:
Roo Code 2025-08-09 18:16:14 +00:00 • committed by Merge Resolver
parent 55884030c4
commit 5dde9513e3
13 changed files with 574 additions and 91 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -274,14 +274,18 @@ 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. Suggestions must be complete, actionable answers without placeholders. Optionally include mode attribute to switch modes (code/architect/etc.)
- 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.)
Usage:
<ask_followup_question>
<question>Your question here</question>
<follow_up>
<suggest>First suggestion</suggest>
<suggest mode="code">Action with mode switch</suggest>
<suggest>
<content>Your suggested answer here</content>
</suggest>
<suggest>
<mode>code</mode>
<content>Implement the solution</content>
</suggest>
</follow_up>
</ask_followup_question>
@ -289,12 +293,35 @@ Example:
<ask_followup_question>
<question>What is the path to the frontend-config.json file?</question>
<follow_up>
<suggest>./src/frontend-config.json</suggest>
<suggest>./config/frontend-config.json</suggest>
<suggest>./frontend-config.json</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>
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>
</follow_up>
</ask_followup_question>
## attempt_completion
Description: After each tool use, the user will respond with the result of that tool use, i.e. if it succeeded or failed, along with any reasons for failure. Once you've received the results of tool uses and can confirm that the task is complete, use this tool to present the result of your work to the user. The user may respond with feedback if they are not satisfied with the result, which you can use to make improvements and try again.
IMPORTANT NOTE: This tool CANNOT be used until you've confirmed from the user that any previous tool uses were successful. Failure to do so will result in code corruption and system failure. Before using this tool, you must ask yourself in <thinking></thinking> tags if you've confirmed from the user that any previous tool uses were successful. If not, then DO NOT use this tool.

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

@ -171,14 +171,18 @@ 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. Suggestions must be complete, actionable answers without placeholders. Optionally include mode attribute to switch modes (code/architect/etc.)
- 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.)
Usage:
<ask_followup_question>
<question>Your question here</question>
<follow_up>
<suggest>First suggestion</suggest>
<suggest mode="code">Action with mode switch</suggest>
<suggest>
<content>Your suggested answer here</content>
</suggest>
<suggest>
<mode>code</mode>
<content>Implement the solution</content>
</suggest>
</follow_up>
</ask_followup_question>
@ -186,12 +190,35 @@ Example:
<ask_followup_question>
<question>What is the path to the frontend-config.json file?</question>
<follow_up>
<suggest>./src/frontend-config.json</suggest>
<suggest>./config/frontend-config.json</suggest>
<suggest>./frontend-config.json</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>
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>
</follow_up>
</ask_followup_question>
## attempt_completion
Description: After each tool use, the user will respond with the result of that tool use, i.e. if it succeeded or failed, along with any reasons for failure. Once you've received the results of tool uses and can confirm that the task is complete, use this tool to present the result of your work to the user. The user may respond with feedback if they are not satisfied with the result, which you can use to make improvements and try again.
IMPORTANT NOTE: This tool CANNOT be used until you've confirmed from the user that any previous tool uses were successful. Failure to do so will result in code corruption and system failure. Before using this tool, you must ask yourself in <thinking></thinking> tags if you've confirmed from the user that any previous tool uses were successful. If not, then DO NOT use this tool.

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

@ -273,14 +273,27 @@ 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. Suggestions must be complete, actionable answers without placeholders. Optionally include mode attribute to switch modes (code/architect/etc.)
- 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
Usage:
<ask_followup_question>
<question>Your question here</question>
<follow_up>
<suggest>First suggestion</suggest>
<suggest mode="code">Action with mode switch</suggest>
- 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>
</follow_up>
</ask_followup_question>
@ -288,9 +301,35 @@ Example:
<ask_followup_question>
<question>What is the path to the frontend-config.json file?</question>
<follow_up>
<suggest>./src/frontend-config.json</suggest>
<suggest>./config/frontend-config.json</suggest>
<suggest>./frontend-config.json</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>
- 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>
</follow_up>
</ask_followup_question>

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

@ -323,14 +323,27 @@ 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. Suggestions must be complete, actionable answers without placeholders. Optionally include mode attribute to switch modes (code/architect/etc.)
- 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
Usage:
<ask_followup_question>
<question>Your question here</question>
<follow_up>
<suggest>First suggestion</suggest>
<suggest mode="code">Action with mode switch</suggest>
- 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>
</follow_up>
</ask_followup_question>
@ -338,9 +351,35 @@ Example:
<ask_followup_question>
<question>What is the path to the frontend-config.json file?</question>
<follow_up>
<suggest>./src/frontend-config.json</suggest>
<suggest>./config/frontend-config.json</suggest>
<suggest>./frontend-config.json</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>
- 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>
</follow_up>
</ask_followup_question>

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

@ -279,14 +279,27 @@ 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. Suggestions must be complete, actionable answers without placeholders. Optionally include mode attribute to switch modes (code/architect/etc.)
- 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
Usage:
<ask_followup_question>
<question>Your question here</question>
<follow_up>
<suggest>First suggestion</suggest>
<suggest mode="code">Action with mode switch</suggest>
- 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>
</follow_up>
</ask_followup_question>
@ -294,9 +307,35 @@ Example:
<ask_followup_question>
<question>What is the path to the frontend-config.json file?</question>
<follow_up>
<suggest>./src/frontend-config.json</suggest>
<suggest>./config/frontend-config.json</suggest>
<suggest>./frontend-config.json</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>
- 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>
</follow_up>
</ask_followup_question>

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

@ -274,14 +274,27 @@ 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. Suggestions must be complete, actionable answers without placeholders. Optionally include mode attribute to switch modes (code/architect/etc.)
- 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
Usage:
<ask_followup_question>
<question>Your question here</question>
<follow_up>
<suggest>First suggestion</suggest>
<suggest mode="code">Action with mode switch</suggest>
- 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>
</follow_up>
</ask_followup_question>
@ -289,9 +302,35 @@ Example:
<ask_followup_question>
<question>What is the path to the frontend-config.json file?</question>
<follow_up>
<suggest>./src/frontend-config.json</suggest>
<suggest>./config/frontend-config.json</suggest>
<suggest>./frontend-config.json</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>
- 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>
</follow_up>
</ask_followup_question>

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

@ -327,14 +327,27 @@ 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. Suggestions must be complete, actionable answers without placeholders. Optionally include mode attribute to switch modes (code/architect/etc.)
- 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
Usage:
<ask_followup_question>
<question>Your question here</question>
<follow_up>
<suggest>First suggestion</suggest>
<suggest mode="code">Action with mode switch</suggest>
- 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>
</follow_up>
</ask_followup_question>
@ -342,9 +355,35 @@ Example:
<ask_followup_question>
<question>What is the path to the frontend-config.json file?</question>
<follow_up>
<suggest>./src/frontend-config.json</suggest>
<suggest>./config/frontend-config.json</suggest>
<suggest>./frontend-config.json</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>
- 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>
</follow_up>
</ask_followup_question>

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

@ -274,14 +274,27 @@ 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. Suggestions must be complete, actionable answers without placeholders. Optionally include mode attribute to switch modes (code/architect/etc.)
- 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
Usage:
<ask_followup_question>
<question>Your question here</question>
<follow_up>
<suggest>First suggestion</suggest>
<suggest mode="code">Action with mode switch</suggest>
- 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>
</follow_up>
</ask_followup_question>
@ -289,9 +302,35 @@ Example:
<ask_followup_question>
<question>What is the path to the frontend-config.json file?</question>
<follow_up>
<suggest>./src/frontend-config.json</suggest>
<suggest>./config/frontend-config.json</suggest>
<suggest>./frontend-config.json</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>
- 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>
</follow_up>
</ask_followup_question>

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

@ -362,14 +362,27 @@ 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. Suggestions must be complete, actionable answers without placeholders. Optionally include mode attribute to switch modes (code/architect/etc.)
- 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
Usage:
<ask_followup_question>
<question>Your question here</question>
<follow_up>
<suggest>First suggestion</suggest>
<suggest mode="code">Action with mode switch</suggest>
- 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>
</follow_up>
</ask_followup_question>
@ -377,9 +390,35 @@ Example:
<ask_followup_question>
<question>What is the path to the frontend-config.json file?</question>
<follow_up>
<suggest>./src/frontend-config.json</suggest>
<suggest>./config/frontend-config.json</suggest>
<suggest>./frontend-config.json</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>
- 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>
</follow_up>
</ask_followup_question>

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

@ -274,14 +274,27 @@ 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. Suggestions must be complete, actionable answers without placeholders. Optionally include mode attribute to switch modes (code/architect/etc.)
- 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
Usage:
<ask_followup_question>
<question>Your question here</question>
<follow_up>
<suggest>First suggestion</suggest>
<suggest mode="code">Action with mode switch</suggest>
- 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>
</follow_up>
</ask_followup_question>
@ -289,9 +302,35 @@ Example:
<ask_followup_question>
<question>What is the path to the frontend-config.json file?</question>
<follow_up>
<suggest>./src/frontend-config.json</suggest>
<suggest>./config/frontend-config.json</suggest>
<suggest>./frontend-config.json</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>
- 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>
</follow_up>
</ask_followup_question>

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

@ -327,14 +327,27 @@ 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. Suggestions must be complete, actionable answers without placeholders. Optionally include mode attribute to switch modes (code/architect/etc.)
- 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
Usage:
<ask_followup_question>
<question>Your question here</question>
<follow_up>
<suggest>First suggestion</suggest>
<suggest mode="code">Action with mode switch</suggest>
- 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>
</follow_up>
</ask_followup_question>
@ -342,9 +355,35 @@ Example:
<ask_followup_question>
<question>What is the path to the frontend-config.json file?</question>
<follow_up>
<suggest>./src/frontend-config.json</suggest>
<suggest>./config/frontend-config.json</suggest>
<suggest>./frontend-config.json</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>
- 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>
</follow_up>
</ask_followup_question>

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

@ -323,14 +323,27 @@ 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. Suggestions must be complete, actionable answers without placeholders. Optionally include mode attribute to switch modes (code/architect/etc.)
- 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
Usage:
<ask_followup_question>
<question>Your question here</question>
<follow_up>
<suggest>First suggestion</suggest>
<suggest mode="code">Action with mode switch</suggest>
- 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>
</follow_up>
</ask_followup_question>
@ -338,9 +351,35 @@ Example:
<ask_followup_question>
<question>What is the path to the frontend-config.json file?</question>
<follow_up>
<suggest>./src/frontend-config.json</suggest>
<suggest>./config/frontend-config.json</suggest>
<suggest>./frontend-config.json</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>
- 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>
</follow_up>
</ask_followup_question>

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

@ -274,14 +274,27 @@ 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. Suggestions must be complete, actionable answers without placeholders. Optionally include mode attribute to switch modes (code/architect/etc.)
- 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
Usage:
<ask_followup_question>
<question>Your question here</question>
<follow_up>
<suggest>First suggestion</suggest>
<suggest mode="code">Action with mode switch</suggest>
- 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>
</follow_up>
</ask_followup_question>
@ -289,9 +302,35 @@ Example:
<ask_followup_question>
<question>What is the path to the frontend-config.json file?</question>
<follow_up>
<suggest>./src/frontend-config.json</suggest>
<suggest>./config/frontend-config.json</suggest>
<suggest>./frontend-config.json</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>
- 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>
</follow_up>
</ask_followup_question>