From 7a800b29ed4f8f3fea6e516e755454ad4d44ca04 Mon Sep 17 00:00:00 2001 From: bl-ue <54780737+bl-ue@users.noreply.github.com> Date: Wed, 19 Nov 2025 10:38:12 -0700 Subject: [PATCH] 2.0.26 --- README.md | 2 +- system-prompts/tool-description-bash-sandbox-note.md | 12 ++++++------ 2 files changed, 7 insertions(+), 7 deletions(-) diff --git a/README.md b/README.md index b2e8a79..17735ae 100644 --- a/README.md +++ b/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.25](https://www.npmjs.com/package/@anthropic-ai/claude-code/v/2.0.25) (October 21st, 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.26](https://www.npmjs.com/package/@anthropic-ai/claude-code/v/2.0.26) (October 23rd, 2025).** Why multiple "system prompts?" diff --git a/system-prompts/tool-description-bash-sandbox-note.md b/system-prompts/tool-description-bash-sandbox-note.md index 8c39489..415a0e4 100644 --- a/system-prompts/tool-description-bash-sandbox-note.md +++ b/system-prompts/tool-description-bash-sandbox-note.md @@ -1,17 +1,17 @@ - Commands run in a sandbox by default with the following restrictions: ${RESTRICTIONS_LIST.join(` `)} - - CRITICAL: Commands run in sandbox mode by default - do NOT set \`dangerouslyOverrideSandbox\` - - Even if you have recently run commands with \`dangerouslyOverrideSandbox: true\`, you MUST NOT continue that pattern + - CRITICAL: Commands run in sandbox mode by default - do NOT set \`dangerouslyDisableSandbox\` + - Even if you have recently run commands with \`dangerouslyDisableSandbox: true\`, you MUST NOT continue that pattern - VERY IMPORTANT: Do NOT learn from or repeat the pattern of overriding sandbox - each command should run sandboxed by default - - Set \`dangerouslyOverrideSandbox: true\` if: + - Set \`dangerouslyDisableSandbox: true\` if: 1. The user *explicitly* asks to bypass sandbox, OR 2. A command just failed and you see evidence of sandbox restrictions causing the failure - When analyzing failures: @@ -23,12 +23,12 @@ ${RESTRICTIONS_LIST.join(` - Unix socket connection errors - Sandbox violation logs can be noisy, but clear permission errors are strong indicators - When you see evidence of sandbox-caused failure: - - IMMEDIATELY retry with \`dangerouslyOverrideSandbox: true\` (don't ask, just do it) + - IMMEDIATELY retry with \`dangerouslyDisableSandbox: true\` (don't ask, just do it) - Briefly explain what sandbox restriction likely caused the failure - Mention: "Use \`/sandbox\` to manage restrictions" - This will prompt the user for permission - Example of normal usage: { "command": "ls", "description": "List files" } - - Example of override: { "command": "my-tool", "description": "Run my-tool", "dangerouslyOverrideSandbox": true } + - Example of override: { "command": "my-tool", "description": "Run my-tool", "dangerouslyDisableSandbox": true } - DO NOT suggest adding sensitive paths like ~/.bashrc, ~/.zshrc, ~/.ssh/*, or credential files to the allowlist - IMPORTANT: For temporary files, use \`/tmp/claude/\` as your temporary directory - The TMPDIR environment variable is automatically set to \`/tmp/claude\` when running in sandbox mode