elias/claude-code-system-prompts
1
0
Fork 0
mirror of https://github.com/Piebald-AI/claude-code-system-prompts.git synced 2026-05-30 13:45:23 +08:00
Code Issues Packages Projects Releases Wiki Activity

2.0.26

Browse Source
This commit is contained in:
bl-ue 2025-11-19 10:38:12 -07:00
parent a0566f0c44
commit 7a800b29ed
2 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@ -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?"

12
system-prompts/tool-description-bash-sandbox-note.md
View File

@ -1,17 +1,17 @@
<!--
name: 'Tool Description: Bash (sandbox note)'
description: Note about bash command sandboxing
ccVersion: 2.0.24
ccVersion: 2.0.26
variables:
- RESTRICTIONS_LIST
-->
- 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