v2.0.52 (+42 tokens)

This commit is contained in:
bl-ue 2025-11-24 16:39:06 -07:00
parent 0902a0e57d
commit 74f41c979c
2 changed files with 5 additions and 3 deletions

View File

@ -1,6 +1,6 @@
# Claude Code System Prompts # 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.51](https://www.npmjs.com/package/@anthropic-ai/claude-code/v/2.0.51) (November 24th, 2025).** It also contains a [**CHANGELOG.md**](./CHANGELOG.md) for the system prompts across 32 versions since v2.0.14. 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.52](https://www.npmjs.com/package/@anthropic-ai/claude-code/v/2.0.52) (November 24th, 2025).** It also contains a [**CHANGELOG.md**](./CHANGELOG.md) for the system prompts across 33 versions since v2.0.14.
Why multiple "system prompts?" Why multiple "system prompts?"
@ -94,7 +94,7 @@ Text for large system reminders.
- [System Reminder: Plan mode is active (enhanced)](./system-prompts/system-reminder-plan-mode-is-active-enhanced.md) (**789** tks) - Enhanced plan mode system reminder with parallel exploration and multi-agent planning. - [System Reminder: Plan mode is active (enhanced)](./system-prompts/system-reminder-plan-mode-is-active-enhanced.md) (**789** tks) - Enhanced plan mode system reminder with parallel exploration and multi-agent planning.
- [System Reminder: Plan mode is active (for subagents)](./system-prompts/system-reminder-plan-mode-is-active-for-subagents.md) (**310** tks) - Simplified plan mode system reminder for sub agents. - [System Reminder: Plan mode is active (for subagents)](./system-prompts/system-reminder-plan-mode-is-active-for-subagents.md) (**310** tks) - Simplified plan mode system reminder for sub agents.
- [System Reminder: Plan mode is active](./system-prompts/system-reminder-plan-mode-is-active.md) (**242** tks) - System reminder sent to Claude when the user enters plan mode. - [System Reminder: Plan mode is active](./system-prompts/system-reminder-plan-mode-is-active.md) (**242** tks) - System reminder sent to Claude when the user enters plan mode.
- [System Reminder: Plan mode re-entry](./system-prompts/system-reminder-plan-mode-re-entry.md) (**194** tks) - System reminder sent when the user enters Plan mode after having previously exited it either via shift+tab or by approving Claude's plan.. - [System Reminder: Plan mode re-entry](./system-prompts/system-reminder-plan-mode-re-entry.md) (**236** tks) - System reminder sent when the user enters Plan mode after having previously exited it either via shift+tab or by approving Claude's plan..
- [System Reminder: `mcp-cli` Large Output](./system-prompts/system-reminder-mcp-cli-large-output.md) (**265** tks) - System reminder sent when the output of an `mcp-cli read` or `mcp-cli call` command is greater than the MAX_MCP_OUTPUT_TOKENS environment variable (defaults to 25000). - [System Reminder: `mcp-cli` Large Output](./system-prompts/system-reminder-mcp-cli-large-output.md) (**265** tks) - System reminder sent when the output of an `mcp-cli read` or `mcp-cli call` command is greater than the MAX_MCP_OUTPUT_TOKENS environment variable (defaults to 25000).
### Builtin Tool Descriptions ### Builtin Tool Descriptions

View File

@ -1,9 +1,10 @@
<!-- <!--
name: 'System Reminder: Plan mode re-entry' name: 'System Reminder: Plan mode re-entry'
description: System reminder sent when the user enters Plan mode after having previously exited it either via shift+tab or by approving Claude's plan. description: System reminder sent when the user enters Plan mode after having previously exited it either via shift+tab or by approving Claude's plan.
ccVersion: 2.0.47 ccVersion: 2.0.52
variables: variables:
- SYSTEM_REMINDER - SYSTEM_REMINDER
- EXIT_PLAN_MODE_TOOL_OBJECT
--> -->
## Re-entering Plan Mode ## Re-entering Plan Mode
@ -15,5 +16,6 @@ You are returning to plan mode after having previously exited it. A plan file ex
3. Decide how to proceed: 3. Decide how to proceed:
- **Different task**: If the user's request is for a different task—even if it's similar or related—start fresh by overwriting the existing plan - **Different task**: If the user's request is for a different task—even if it's similar or related—start fresh by overwriting the existing plan
- **Same task, continuing**: If this is explicitly a continuation or refinement of the exact same task, modify the existing plan while cleaning up outdated or irrelevant sections - **Same task, continuing**: If this is explicitly a continuation or refinement of the exact same task, modify the existing plan while cleaning up outdated or irrelevant sections
4. Continue on with the plan process and most importantly you should always edit the plan file one way or the other before calling ${EXIT_PLAN_MODE_TOOL_OBJECT.name}
Treat this as a fresh planning session. Do not assume the existing plan is relevant without evaluating it first. Treat this as a fresh planning session. Do not assume the existing plan is relevant without evaluating it first.