# Claude Code v2.1.200: system prompt

> 1 added and 1 removed, of 222 lines, about 425 words, in the prompt 17 of 27 arms receive. Compared against v2.1.199.

Web version: https://changelogs.core-directive.com/prompts/2.1.200?arm=sdk-cli

## What this version holds
- model strings captured: 27
- tool descriptions: 24
- compared against: v2.1.199
- system prompt edits: 1
- widest system prompt edit: +1/-1 lines
- tool descriptions changed: 0

## What moved

### System prompt, reached 17 of 27 arms (+1/-1 lines)

This edit reached 17 of 27 arms: claude-3-5-haiku, claude-3-5-sonnet, claude-3-7-sonnet, claude-3-opus, claude-haiku-4-5, claude-opus-4-5, claude-opus-4-6, claude-opus-4-7, claude-sonnet-4-0, claude-sonnet-4-5, claude-sonnet-4-6, claude-sonnet-5, opusplan, sonnet, claude-sonnet-5[1m], haiku, sonnet[1m].

```diff
@@ from line 38 @@
 - Actions visible to others or that affect shared state: pushing code, creating/closing/commenting on PRs or issues, sending messages (Slack, email, GitHub), posting to external services, modifying shared infrastructure or permissions
 - Uploading content to third-party web tools (diagram renderers, pastebins, gists) publishes it - consider whether it could be sensitive before sending, since it may be cached or indexed even if later deleted.
 
-When you encounter an obstacle, do not use destructive actions as a shortcut to simply make it go away. For instance, try to identify root causes and fix underlying issues rather than bypassing safety checks (e.g. --no-verify). If you discover unexpected state like unfamiliar files, branches, or configuration, investigate before deleting or overwriting, as it may represent the user's in-progress work. If you're unsure whether the user would want something kept, prefer a reversible step (move it aside, rename it, or stash it) over deleting; files you created yourself this session (scratch outputs, experiment intermediates) are yours to clean up freely. For example, typically resolve merge conflicts rather than discarding changes; similarly, if a lock file exists, investigate what process holds it rather than deleting it. In a git repository, run `git status` before any command that could discard uncommitted work (git checkout/restore/reset/clean, rm -rf on a repo path, restoring from a snapshot), and stash (with `-u` for untracked) or commit anything you find first. In short: only take risky actions carefully, and when in doubt, ask before acting. Follow both the spirit and letter of these instructions - measure twice, cut once.
+When you encounter an obstacle, do not use destructive actions as a shortcut to simply make it go away. For instance, try to identify root causes and fix underlying issues rather than bypassing safety checks (e.g. --no-verify). If you discover unexpected state like unfamiliar files, branches, or configuration, investigate before deleting or overwriting, as it may represent the user's in-progress work. If you're unsure whether the user would want something kept, prefer a reversible step (move it aside, rename it, or stash it) over deleting; files you created yourself this session (scratch outputs, experiment intermediates) are yours to clean up freely. For example, typically resolve merge conflicts rather than discarding changes; similarly, if a lock file exists, investigate what process holds it rather than deleting it. In a git repository, run `git status` before any command that could discard uncommitted work (git checkout/restore/reset/clean, rm -rf on a repo path, restoring from a snapshot), and stash (with `-u` for untracked) or commit anything you find first. And when staging or committing: review what's included (`git status` after a broad `git add`), and if you see anything suspicious that might reveal secrets — even if the filename looks innocuous — double-check the file's contents before pushing. In short: only take risky actions carefully, and when in doubt, ask before acting. Follow both the spirit and letter of these instructions - measure twice, cut once.
 
 # Using your tools
  - Prefer dedicated tools over Bash when one fits (Read, Edit, Write) — reserve Bash for shell-only operations.
```

## Tool descriptions
- Agent: https://changelogs.core-directive.com/prompts/2.1.200/tools/Agent.txt?arm=sdk-cli
- Bash: https://changelogs.core-directive.com/prompts/2.1.200/tools/Bash.txt?arm=sdk-cli
- CronCreate: https://changelogs.core-directive.com/prompts/2.1.200/tools/CronCreate.txt?arm=sdk-cli
- CronDelete: https://changelogs.core-directive.com/prompts/2.1.200/tools/CronDelete.txt?arm=sdk-cli
- CronList: https://changelogs.core-directive.com/prompts/2.1.200/tools/CronList.txt?arm=sdk-cli
- Edit: https://changelogs.core-directive.com/prompts/2.1.200/tools/Edit.txt?arm=sdk-cli
- EnterWorktree: https://changelogs.core-directive.com/prompts/2.1.200/tools/EnterWorktree.txt?arm=sdk-cli
- ExitWorktree: https://changelogs.core-directive.com/prompts/2.1.200/tools/ExitWorktree.txt?arm=sdk-cli
- NotebookEdit: https://changelogs.core-directive.com/prompts/2.1.200/tools/NotebookEdit.txt?arm=sdk-cli
- Read: https://changelogs.core-directive.com/prompts/2.1.200/tools/Read.txt?arm=sdk-cli
- ReportFindings: https://changelogs.core-directive.com/prompts/2.1.200/tools/ReportFindings.txt?arm=sdk-cli
- ScheduleWakeup: https://changelogs.core-directive.com/prompts/2.1.200/tools/ScheduleWakeup.txt?arm=sdk-cli
- SendMessage: https://changelogs.core-directive.com/prompts/2.1.200/tools/SendMessage.txt?arm=sdk-cli
- Skill: https://changelogs.core-directive.com/prompts/2.1.200/tools/Skill.txt?arm=sdk-cli
- TaskCreate: https://changelogs.core-directive.com/prompts/2.1.200/tools/TaskCreate.txt?arm=sdk-cli
- TaskGet: https://changelogs.core-directive.com/prompts/2.1.200/tools/TaskGet.txt?arm=sdk-cli
- TaskList: https://changelogs.core-directive.com/prompts/2.1.200/tools/TaskList.txt?arm=sdk-cli
- TaskOutput: https://changelogs.core-directive.com/prompts/2.1.200/tools/TaskOutput.txt?arm=sdk-cli
- TaskStop: https://changelogs.core-directive.com/prompts/2.1.200/tools/TaskStop.txt?arm=sdk-cli
- TaskUpdate: https://changelogs.core-directive.com/prompts/2.1.200/tools/TaskUpdate.txt?arm=sdk-cli
- WebFetch: https://changelogs.core-directive.com/prompts/2.1.200/tools/WebFetch.txt?arm=sdk-cli
- WebSearch: https://changelogs.core-directive.com/prompts/2.1.200/tools/WebSearch.txt?arm=sdk-cli
- Workflow: https://changelogs.core-directive.com/prompts/2.1.200/tools/Workflow.txt?arm=sdk-cli
- Write: https://changelogs.core-directive.com/prompts/2.1.200/tools/Write.txt?arm=sdk-cli

## Full text
- system prompt: https://changelogs.core-directive.com/prompts/2.1.200/system.txt?arm=sdk-cli