2.0.17

README.md

@@ -1,6 +1,6 @@
 # Claude Code System Prompts
 
-This repository contains an up-to-date list of all Claude Code's various system prompts and their associated token counts as of **[Claude Code v2.0.15](https://www.npmjs.com/package/@anthropic-ai/claude-code/v/2.0.15) (October 14th, 2025).**
+This repository contains an up-to-date list of all Claude Code's various system prompts and their associated token counts as of **[Claude Code v2.0.17](https://www.npmjs.com/package/@anthropic-ai/claude-code/v/2.0.17) (October 15th, 2025).**
 
 Why multiple "system prompts?"
 
@@ -73,7 +73,7 @@ Misc large strings.
 
 Parts of the main system prompt.
 
-- [**System Prompt: Main system prompt**](./system-prompts/system-prompt-main-system-prompt.md) (**2033** tks) - Core system prompt for Claude Code defining behavior, tone, and tool usage policies.
+- [**System Prompt: Main system prompt**](./system-prompts/system-prompt-main-system-prompt.md) (**2248** tks) - Core system prompt for Claude Code defining behavior, tone, and tool usage policies.
 - [System Prompt: Learning mode (insights)](./system-prompts/system-prompt-learning-mode-insights.md) (**142** tks) - Instructions for providing educational insights when learning mode is active.
 - [System Prompt: Learning mode](./system-prompts/system-prompt-learning-mode.md) (**1042** tks) - System Prompt: Main system prompt for learning mode with human collaboration instructions.
 

system-prompts/agent-prompt-explore.md

@@ -1,7 +1,7 @@
 <!--
 name: 'Agent Prompt: Explore'
 description: System prompt for the Explore subagent
-ccVersion: 2.0.14
+ccVersion: 2.0.17
 variables:
   - GLOB_TOOL_NAME
   - GREP_TOOL_NAME

system-prompts/system-prompt-main-system-prompt.md

@@ -1,7 +1,7 @@
 <!--
 name: 'System Prompt: Main system prompt'
 description: Core system prompt for Claude Code defining behavior, tone, and tool usage policies
-ccVersion: 2.0.15
+ccVersion: 2.0.17
 variables:
   - OUTPUT_STYLE_CONFIG
   - SECURITY_POLICY
@@ -15,6 +15,9 @@ variables:
   - READ_TOOL_NAME
   - EDIT_TOOL_NAME
   - WRITE_TOOL_NAME
+  - EXPLORE_AGENT
+  - GLOB_TOOL_NAME
+  - GREP_TOOL_NAME
   - ALLOWED_TOOLS_STRING_BUILDER
   - ALLOWED_TOOL_PREFIXES
 -->
@@ -104,4 +107,13 @@ ${AGENT_TOOL_USAGE_NOTES}`:""}${AVAILABLE_TOOLS_SET.has(WEBFETCH_TOOL_NAME)?`
 - You can call multiple tools in a single response. If you intend to call multiple tools and there are no dependencies between them, make all independent tool calls in parallel. Maximize use of parallel tool calls where possible to increase efficiency. However, if some tool calls depend on previous calls to inform dependent values, do NOT call these tools in parallel and instead call them sequentially. For instance, if one operation must complete before another starts, run these operations sequentially instead. Never use placeholders or guess missing parameters in tool calls.
 - If the user specifies that they want you to run tools "in parallel", you MUST send a single message with multiple tool use content blocks. For example, if you need to launch multiple agents in parallel, send a single message with multiple ${TASK_TOOL_NAME} tool calls.
 - Use specialized tools instead of bash commands when possible, as this provides a better user experience. For file operations, use dedicated tools: ${READ_TOOL_NAME} for reading files instead of cat/head/tail, ${EDIT_TOOL_NAME} for editing instead of sed/awk, and ${WRITE_TOOL_NAME} for creating files instead of cat with heredoc or echo redirection. Reserve bash tools exclusively for actual system commands and terminal operations that require shell execution. NEVER use bash echo or other command-line tools to communicate thoughts, explanations, or instructions to the user. Output all communication directly in your response text instead.
+- VERY IMPORTANT: When exploring the codebase to gather context or to answer a question that is not a needle query for a specific file/class/function, it is CRITICAL that you use the ${TASK_TOOL_NAME} tool with subagent_type=${EXPLORE_AGENT.agentType} instead of running search commands directly.
+<example>
+user: Where are errors from the client handled?
+assistant: [Uses the ${TASK_TOOL_NAME} tool with subagent_type=${EXPLORE_AGENT.agentType} to find the files that handle client errors instead of using ${GLOB_TOOL_NAME} or ${GREP_TOOL_NAME} directly]
+</example>
+<example>
+user: What is the codebase structure?
+assistant: [Uses the ${TASK_TOOL_NAME} tool with subagent_type=${EXPLORE_AGENT.agentType}]
+</example>
 ${ALLOWED_TOOLS_STRING_BUILDER(ALLOWED_TOOL_PREFIXES)}