Skip to content

Fix #5294: Prevent Architect mode from providing time estimates #5295

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mrubens merged 2 commits into from
Jul 1, 2025
Merged

Fix #5294: Prevent Architect mode from providing time estimates #5295

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f6e71c4
Fixes #5294: Add instruction to Architect mode to avoid time estimates
roomote Jun 30, 2025
94416e6
More tweaks to prompt
mrubens Jul 1, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions src/core/prompts/__tests__/__snapshots__/add-custom-instructions/architect-mode-prompt.snap
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -483,9 +483,9 @@ Mode-specific Instructions:

4. Ask the user if they are pleased with this plan, or if they would like to make any changes. Think of this as a brainstorming session where you can discuss the task and plan the best way to accomplish it.

5. Once the user confirms the plan, ask them if they'd like you to write it to a markdown file.
5. Use the switch_mode tool to request that the user switch to another mode to implement the solution.

6. Use the switch_mode tool to request that the user switch to another mode to implement the solution.
**IMPORTANT: Do not provide time estimates for how long tasks will take to complete. Focus on creating clear, actionable plans without speculating about implementation timeframes.**

Rules:
# Rules from .clinerules-architect:
Expand Down
4 changes: 2 additions & 2 deletions ...prompts/__tests__/__snapshots__/add-custom-instructions/mcp-server-creation-disabled.snap
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -545,9 +545,9 @@ Mode-specific Instructions:

4. Ask the user if they are pleased with this plan, or if they would like to make any changes. Think of this as a brainstorming session where you can discuss the task and plan the best way to accomplish it.

5. Once the user confirms the plan, ask them if they'd like you to write it to a markdown file.
5. Use the switch_mode tool to request that the user switch to another mode to implement the solution.

6. Use the switch_mode tool to request that the user switch to another mode to implement the solution.
**IMPORTANT: Do not provide time estimates for how long tasks will take to complete. Focus on creating clear, actionable plans without speculating about implementation timeframes.**

Rules:
# Rules from .clinerules-architect:
Expand Down
4 changes: 2 additions & 2 deletions .../prompts/__tests__/__snapshots__/add-custom-instructions/mcp-server-creation-enabled.snap
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -551,9 +551,9 @@ Mode-specific Instructions:

4. Ask the user if they are pleased with this plan, or if they would like to make any changes. Think of this as a brainstorming session where you can discuss the task and plan the best way to accomplish it.

5. Once the user confirms the plan, ask them if they'd like you to write it to a markdown file.
5. Use the switch_mode tool to request that the user switch to another mode to implement the solution.

6. Use the switch_mode tool to request that the user switch to another mode to implement the solution.
**IMPORTANT: Do not provide time estimates for how long tasks will take to complete. Focus on creating clear, actionable plans without speculating about implementation timeframes.**

Rules:
# Rules from .clinerules-architect:
Expand Down
4 changes: 2 additions & 2 deletions src/core/prompts/__tests__/__snapshots__/add-custom-instructions/partial-reads-enabled.snap
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -488,9 +488,9 @@ Mode-specific Instructions:

4. Ask the user if they are pleased with this plan, or if they would like to make any changes. Think of this as a brainstorming session where you can discuss the task and plan the best way to accomplish it.

5. Once the user confirms the plan, ask them if they'd like you to write it to a markdown file.
5. Use the switch_mode tool to request that the user switch to another mode to implement the solution.

6. Use the switch_mode tool to request that the user switch to another mode to implement the solution.
**IMPORTANT: Do not provide time estimates for how long tasks will take to complete. Focus on creating clear, actionable plans without speculating about implementation timeframes.**

Rules:
# Rules from .clinerules-architect:
Expand Down
4 changes: 2 additions & 2 deletions src/core/prompts/__tests__/__snapshots__/system-prompt/consistent-system-prompt.snap
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -483,9 +483,9 @@ Mode-specific Instructions:

4. Ask the user if they are pleased with this plan, or if they would like to make any changes. Think of this as a brainstorming session where you can discuss the task and plan the best way to accomplish it.

5. Once the user confirms the plan, ask them if they'd like you to write it to a markdown file.
5. Use the switch_mode tool to request that the user switch to another mode to implement the solution.

6. Use the switch_mode tool to request that the user switch to another mode to implement the solution.
**IMPORTANT: Do not provide time estimates for how long tasks will take to complete. Focus on creating clear, actionable plans without speculating about implementation timeframes.**

Rules:
# Rules from .clinerules-architect:
Expand Down
4 changes: 2 additions & 2 deletions src/core/prompts/__tests__/__snapshots__/system-prompt/with-computer-use-support.snap
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -539,9 +539,9 @@ Mode-specific Instructions:

4. Ask the user if they are pleased with this plan, or if they would like to make any changes. Think of this as a brainstorming session where you can discuss the task and plan the best way to accomplish it.

5. Once the user confirms the plan, ask them if they'd like you to write it to a markdown file.
5. Use the switch_mode tool to request that the user switch to another mode to implement the solution.

6. Use the switch_mode tool to request that the user switch to another mode to implement the solution.
**IMPORTANT: Do not provide time estimates for how long tasks will take to complete. Focus on creating clear, actionable plans without speculating about implementation timeframes.**

Rules:
# Rules from .clinerules-architect:
Expand Down
4 changes: 2 additions & 2 deletions src/core/prompts/__tests__/__snapshots__/system-prompt/with-diff-enabled-false.snap
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -483,9 +483,9 @@ Mode-specific Instructions:

4. Ask the user if they are pleased with this plan, or if they would like to make any changes. Think of this as a brainstorming session where you can discuss the task and plan the best way to accomplish it.

5. Once the user confirms the plan, ask them if they'd like you to write it to a markdown file.
5. Use the switch_mode tool to request that the user switch to another mode to implement the solution.

6. Use the switch_mode tool to request that the user switch to another mode to implement the solution.
**IMPORTANT: Do not provide time estimates for how long tasks will take to complete. Focus on creating clear, actionable plans without speculating about implementation timeframes.**

Rules:
# Rules from .clinerules-architect:
Expand Down
4 changes: 2 additions & 2 deletions src/core/prompts/__tests__/__snapshots__/system-prompt/with-diff-enabled-true.snap
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -571,9 +571,9 @@ Mode-specific Instructions:

4. Ask the user if they are pleased with this plan, or if they would like to make any changes. Think of this as a brainstorming session where you can discuss the task and plan the best way to accomplish it.

5. Once the user confirms the plan, ask them if they'd like you to write it to a markdown file.
5. Use the switch_mode tool to request that the user switch to another mode to implement the solution.

6. Use the switch_mode tool to request that the user switch to another mode to implement the solution.
**IMPORTANT: Do not provide time estimates for how long tasks will take to complete. Focus on creating clear, actionable plans without speculating about implementation timeframes.**

Rules:
# Rules from .clinerules-architect:
Expand Down
4 changes: 2 additions & 2 deletions src/core/prompts/__tests__/__snapshots__/system-prompt/with-diff-enabled-undefined.snap
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -483,9 +483,9 @@ Mode-specific Instructions:

4. Ask the user if they are pleased with this plan, or if they would like to make any changes. Think of this as a brainstorming session where you can discuss the task and plan the best way to accomplish it.

5. Once the user confirms the plan, ask them if they'd like you to write it to a markdown file.
5. Use the switch_mode tool to request that the user switch to another mode to implement the solution.

6. Use the switch_mode tool to request that the user switch to another mode to implement the solution.
**IMPORTANT: Do not provide time estimates for how long tasks will take to complete. Focus on creating clear, actionable plans without speculating about implementation timeframes.**

Rules:
# Rules from .clinerules-architect:
Expand Down
4 changes: 2 additions & 2 deletions src/core/prompts/__tests__/__snapshots__/system-prompt/with-different-viewport-size.snap
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -539,9 +539,9 @@ Mode-specific Instructions:

4. Ask the user if they are pleased with this plan, or if they would like to make any changes. Think of this as a brainstorming session where you can discuss the task and plan the best way to accomplish it.

5. Once the user confirms the plan, ask them if they'd like you to write it to a markdown file.
5. Use the switch_mode tool to request that the user switch to another mode to implement the solution.

6. Use the switch_mode tool to request that the user switch to another mode to implement the solution.
**IMPORTANT: Do not provide time estimates for how long tasks will take to complete. Focus on creating clear, actionable plans without speculating about implementation timeframes.**

Rules:
# Rules from .clinerules-architect:
Expand Down
4 changes: 2 additions & 2 deletions src/core/prompts/__tests__/__snapshots__/system-prompt/with-mcp-hub-provided.snap
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -551,9 +551,9 @@ Mode-specific Instructions:

4. Ask the user if they are pleased with this plan, or if they would like to make any changes. Think of this as a brainstorming session where you can discuss the task and plan the best way to accomplish it.

5. Once the user confirms the plan, ask them if they'd like you to write it to a markdown file.
5. Use the switch_mode tool to request that the user switch to another mode to implement the solution.

6. Use the switch_mode tool to request that the user switch to another mode to implement the solution.
**IMPORTANT: Do not provide time estimates for how long tasks will take to complete. Focus on creating clear, actionable plans without speculating about implementation timeframes.**

Rules:
# Rules from .clinerules-architect:
Expand Down
4 changes: 2 additions & 2 deletions src/core/prompts/__tests__/__snapshots__/system-prompt/with-undefined-mcp-hub.snap
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -483,9 +483,9 @@ Mode-specific Instructions:

4. Ask the user if they are pleased with this plan, or if they would like to make any changes. Think of this as a brainstorming session where you can discuss the task and plan the best way to accomplish it.

5. Once the user confirms the plan, ask them if they'd like you to write it to a markdown file.
5. Use the switch_mode tool to request that the user switch to another mode to implement the solution.

6. Use the switch_mode tool to request that the user switch to another mode to implement the solution.
**IMPORTANT: Do not provide time estimates for how long tasks will take to complete. Focus on creating clear, actionable plans without speculating about implementation timeframes.**

Rules:
# Rules from .clinerules-architect:
Expand Down
2 changes: 1 addition & 1 deletion src/shared/modes.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -72,7 +72,7 @@ export const modes: readonly ModeConfig[] = [
description: "Plan and design before implementation",
groups: ["read", ["edit", { fileRegex: "\\.md$", description: "Markdown files only" }], "browser", "mcp"],
customInstructions:
"1. Do some information gathering (for example using read_file or search_files) to get more context about the task.\n\n2. You should also ask the user clarifying questions to get a better understanding of the task.\n\n3. Once you've gained more context about the user's request, you should create a detailed plan for how to accomplish the task. Include Mermaid diagrams if they help make your plan clearer.\n\n4. Ask the user if they are pleased with this plan, or if they would like to make any changes. Think of this as a brainstorming session where you can discuss the task and plan the best way to accomplish it.\n\n5. Once the user confirms the plan, ask them if they'd like you to write it to a markdown file.\n\n6. Use the switch_mode tool to request that the user switch to another mode to implement the solution.",
Copy link
Member

@daniel-lxs daniel-lxs Jul 1, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I noticed that step 5 about creating a Markdown file was removed, which doesn't appear to have been mentioned in the original issue.

If this change is desirable, then I don't see any issues with this PR.

"1. Do some information gathering (for example using read_file or search_files) to get more context about the task.\n\n2. You should also ask the user clarifying questions to get a better understanding of the task.\n\n3. Once you've gained more context about the user's request, you should create a detailed plan for how to accomplish the task. Include Mermaid diagrams if they help make your plan clearer.\n\n4. Ask the user if they are pleased with this plan, or if they would like to make any changes. Think of this as a brainstorming session where you can discuss the task and plan the best way to accomplish it.\n\n5. Use the switch_mode tool to request that the user switch to another mode to implement the solution.\n\n**IMPORTANT: Do not provide time estimates for how long tasks will take to complete. Focus on creating clear, actionable plans without speculating about implementation timeframes.**",
},
{
slug: "code",
Expand Down
Loading