← Open Source
Piebald-AI

claude-code-system-prompts

All parts of Claude Code's system prompt, 27 builtin tool descriptions, sub agent prompts (Plan/Explore/Task), utility prompts (CLAUDE.md, compact, statusline, magic docs, WebFetch, Bash cmd, security review, agent creation). Updated for each Claude Code version.

ListsPrompt collectionsJavaScript
Open on GitHub
Momentum
+6stars in 24 hours+0.0%
12.8k
Stars
2.04k
Forks
+37
This week
5
Contributors
Created 2025-11-18 · Updated 2026-10-05 · #1288 today
Top developers
README

Check out Piebald

We've released Piebald, the ultimate agentic AI developer experience.
Download it and try it out for free! https://piebald.ai/

Join our Discord X

Scroll down for Claude Code's system prompts. :point_down:

hero

Claude Code System Prompts

Mentioned in Awesome Claude Code

[!tip] NEW (June 12, 2026): We've greatly expanded this list with many more of Claude Code's prompts—from 350 to 515 (+165)—our most complete coverage yet.

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.1.290 (October 5th, 2026). It also contains a CHANGELOG.md for the system prompts across 306 versions since v2.0.14. From the team behind Piebald.

This repository is updated within minutes of each Claude Code release. See the changelog, and follow @PiebaldAI on X for a summary of the system prompt changes in each release.

[!note] ⭐ Star this repository to get notified about new Claude Code versions. For each new Claude Code version, we create a release on GitHub, which will notify all users who've starred the repository.


Why multiple "system prompts?"

Claude Code doesn't just have one single string for its system prompt.

Instead, there are:

  • Large portions conditionally added depending on the environment and various configs.
  • Descriptions for builtin tools like Write, Bash, and TodoWrite, and some are fairly large.
  • Separate system prompts for builtin agents like Explore and Plan.
  • Numerous AI-powered utility functions, such as conversation compaction, CLAUDE.md generation, session title generation, etc. featuring their own systems prompts.

The result—500+ strings that are constantly changing and moving within a very large minified JS file.

[!important] Want to modify a particular piece of the system prompt in your own Claude Code installation? Use tweakcc. It—

  • lets you customize the individual pieces of the system prompt as markdown files, and then
  • patches your npm-based or native (binary) Claude Code installation with them, and also
  • provides diffing and conflict management for when both you and Anthropic have conflicting modifications to the same prompt file.

Extraction

This repository contains the system prompts extracted using a script from the latest npm version of Claude Code. As they're extracted directly from Claude Code's compiled source code, they're guaranteed to be exactly what Claude Code uses. If you use tweakcc to customize the system prompts, it works in a similar way—it patches the exact same strings in your local installation as are extracted into this repository.

Prompts

Note that some prompts contain interpolated bits such as builtin tool name references, lists of available sub agents, and various other context-specific variables, so the actual counts in a particular Claude Code session will differ slightly—likely not beyond ±20 tokens, however.

Agent Prompts

Sub-agents and utilities.

Sub-agents

Creation Assistants

Slash Commands

Utilities

Data

The content of various template files embedded in Claude Code.

  • Data: /auto-mode-setup usage (406 tks) - Defines /auto-mode-setup proposal and reviewed-apply command syntax, request ID ordering, save-target validation, and integrity requirements.
  • Data: Artifact MCP connector guidance (351 tks) - Explains how Artifact MCP manifests declare claude.ai, built-in, and host connectors and how to discover exact server and upstream tool names.
  • Data: Artifact capability verification pass (271 tks) - Requires one functional pass over a page's session-declared runtime capabilities before handing over its link, assembling the preview, database read and endpoint checks to run and what to report to the user.
  • Data: Artifact connector call observation requirement (305 tks) - Explains how to obtain connector argument names from the loaded tool schema, learn result shapes from safe real calls, and disclose shapes that cannot be verified before publishing.
  • Data: Artifact connector server naming guidance (241 tks) - Explains how connector tool prefixes map to manifest server identifiers and why in-page calls must use the resolved connector display name.
  • Data: Artifact decision component HTML skeleton (1117 tks) - Provides the canonical HTML and JSON-island skeleton for embedding one reusable Artifact decision block.
  • Data: Artifact host MCP server guidance (420 tks) - Explains how locally configured MCP servers may be declared as Artifact host servers and distinguishes them from Claude.ai connectors and built-in servers.
  • Data: Artifact publish merged-over newer version file changes notice (481 tks) - Tool-result notice appended when an artifact publish was merged over a newer live version, listing files changed, added, or removed there since the base version, that stale copies must be read again, and how many further files are not listed.
  • Data: Artifact runtime capability declarations (496 tks) - Defines Artifact runtime capability declaration, carry-forward, clearing, replacement, and contract pinning semantics.
  • Data: Auto-compact inputs changed event schema (221 tks) - Schema description for worker-resolved auto-compaction state events used by thin clients to display the effective compaction countdown.
  • Data: Background tasks changed event schema (342 tks) - Schema description for the background_tasks_changed system event and its replace-set semantics.
  • Data: Built-in gh stand-in api command help (1149 tks) - Usage text for Claude Code's built-in gh stand-in, which supports only gh api REST requests to GitHub hosts through the session's GitHub proxy, listing its flags and how {owner}, {repo} and {branch} placeholders are filled in.
  • Data: Chrome browser hints control request (207 tks) - Documents the set_chrome_browser_hints control request that tells a session which connected Claude in Chrome browser to prefer, and that the hints are session-only and never override the live relay roster.
  • Data: Claude API reference — PHP (2877 tks) - PHP SDK reference.
  • Data: Claude API reference — Ruby (2120 tks) - Ruby SDK reference including installation, client initialization, basic requests, streaming, and beta tool runner.
  • Data: Claude Code agent proxy troubleshooting guide (2214 tks) - Troubleshooting guide for Claude Code's policy-enforcing HTTPS agent proxy, covering TLS trust setup, status checks, git, docker, and unsupported traffic.
  • Data: Claude Code gateway customer-routed inference protocol (2945 tks) - Conditional extension to the Claude Code gateway protocol defining customer-routed inference authentication, forwarding, response hygiene, error recovery, policy blocking, discovery, and endpoint requirements.
  • Data: Claude Code gateway protocol (7396 tks) - Markdown reference documenting the Claude Code gateway wire contract, including OAuth 2.0 device flow, RFC 8414 discovery, Messages API inference, managed settings, model discovery, OTLP telemetry, error envelopes, TLS certificate pinning, and proxying to Bedrock, Vertex, and Foundry.
  • Data: Claude Code live documentation sources (2477 tks) - WebFetch URLs for fetching current Claude Code documentation from official sources.
  • Data: Claude Code recent changes reference (1854 tks) - Reference mapping of recently removed or renamed Claude Code commands, flags, and terms to their current replacements.
  • Data: Claude Platform on AWS reference (1805 tks) - Reference documentation for using the Claude Developer Platform through AWS infrastructure, including AnthropicAWS clients, required region and workspace configuration, SigV4 authentication, and short-term API keys.
  • Data: Claude Tag (Claude in Slack) reference (1999 tks) - Offline reference for Claude Tag, Claude Code's org-managed Slack surface, covering what it is, availability, setup, configuration, and how it differs from the earlier Claude in Slack app.
  • Data: Claude Test spec file format (1745 tks) - Reference for the Markdown spec files in .claude-test/specs/ — front matter keys, the three required parts, data-creating specs, and what makes a spec goal-oriented and checkable from a single end screenshot.
  • Data: Claude gateway landing page (392 tks) - HTML status page served at a Claude Code gateway root, showing the gateway logo, the running gateway URL, the identity-provider host, an OAuth discovery link, and the gateway version.
  • Data: Cloud session unverified remote branch push notice (255 tks) - Notice shown when no remote of the checkout could be read, so it could not be checked whether the current branch or detached HEAD commit exists on the remote host, telling the user to push their work to a branch and start a new cloud session from it.
  • Data: Code change published event schema (349 tks) - Schema description for the code_change_published system event, including provenance, idempotency, trust boundaries, and best-effort delivery.
  • Data: Command plugin source command field (160 tks) - Describes the command field for command-based plugin sources, including its one-line directory output contract, cache-copy lifecycle, platform shell, and re-resolution behavior.
  • Data: Cowork plugin MCP discovery and connection (1746 tks) - Reference guidance for finding MCP connectors during plugin customization, using search and suggestion tools, mapping categories to keywords, and writing .mcp.json entries.
  • Data: Cowork plugin examples (3158 tks) - Reference examples of minimal, medium, and complex Cowork plugin structures with plugin metadata, skills, agents, hooks, MCP config, README, and connectors.
  • Data: Cross-session inbound setting (175 tks) - Describes crossSessionInbound delivery, hold, refusal, and permission-mode parity behavior for peer messages.
  • Data: Data visualization anti-patterns (2339 tks) - Reference list of chart and dashboard anti-patterns to check against before shipping a data visualization.
  • Data: Data visualization choosing a form (1177 tks) - Reference guidance for choosing the appropriate chart, stat tile, or non-chart form based on the data's job.
  • Data: Data visualization components (836 tks) - Reference specification for the HTML/SVG pieces, layers, and system parameters that make up a data visualization.
  • Data: Data visualization interaction (1318 tks) - Reference guidance for chart hover layers, tooltips, filters, linked highlighting, and interaction behavior.
  • Data: Data visualization marks and anatomy (2164 tks) - Reference specifications for chart marks, spacing, labels, axes, legends, and stat-tile anatomy.
  • Data: Dialog expiry setting (204 tks) - Describes dialogExpiry deadlines for remote permission dialogs and held cross-session messages, including defaults and overrides.
  • Data: DirectoryAdded hook description (216 tks) - Describes when the DirectoryAdded hook fires, its input fields, and how failures and output are handled for add-dir and register_repo_root sources.
  • Data: Files API reference — C# (378 tks) - C# Files API reference including beta file upload and use with beta message types.
  • Data: Files API reference — Go (413 tks) - Go Files API reference including file upload, listing, deletion, and usage in messages.
  • Data: Files API reference — Java (492 tks) - Java Files API reference including file upload, beta message references, listing, deletion, download, and metadata retrieval.
  • Data: Files API reference — PHP (186 tks) - PHP Files API reference with a beta-era upload example and a warning that current SDKs use the stable Files API shape.
  • Data: Files API reference — Python (1719 tks) - Python Files API reference including file upload, listing, deletion, and usage in messages.
  • Data: Files API reference — TypeScript (961 tks) - TypeScript Files API reference including file upload, listing, deletion, and usage in messages.
  • Data: Gateway device code entry page (261 tks) - HTML verification page served at a gateway device endpoint, prompting the user to enter the short device code shown by Claude Code so they can sign in through their company identity provider.
  • Data: Gateway ignored X-Forwarded-For warning (254 tks) - Gateway startup warning that an X-Forwarded-For header was ignored because the requesting address is not covered by listen.trusted_proxies, and what to configure when a load balancer or ingress fronts the gateway.
  • Data: Get task output control request (201 tks) - Schema description for the get_task_output control request that reads the last 8 KiB of a background shell or Monitor task's output without a model turn, and when it is refused.
  • Data: GitHub Actions workflow for @claude mentions (525 tks) - GitHub Actions workflow template for triggering Claude Code via @claude mentions.
  • Data: GitHub App installation PR description (409 tks) - Template for PR description when installing Claude Code GitHub App integration.
  • Data: Hook classifier context field (654 tks) - Schema description for the classifierContext hook response field, including trust semantics, size and timing limits, transcript visibility, and rewrite-integrity requirements.
  • Data: Hook mcp_server field (312 tks) - Describes the mcp_server object attached to tool-related hook payloads — the server's config key and the source its definition came from — and why trust must key on source rather than on the server name or tool-name prefix.
  • Data: Interrupt cancel queued parameter (646 tks) - Schema description for the optional interrupt cancel_queued request parameter and its queued-command cancellation semantics.
  • Data: Interrupt receipt cancelled field (291 tks) - Schema description for the cancelled UUID list returned when an interrupt request cancels queued commands.
  • Data: Interrupt receipt still queued field (1116 tks) - Schema description for the still_queued UUID list returned by interrupt control responses.
  • Data: Interrupt send_now message_uuid parameter (246 tks) - Schema description for the interrupt message_uuid parameter read only beside send_now, which restricts the request to one exact-match waiting user message and answers nothing_waiting when that message is not waiting.
  • Data: Interrupt send_now parameter (596 tks) - Schema description for the optional interrupt send_now request parameter, which asks that waiting user messages reach the model now without acting as a Stop, and how the CLI chooses between moving the turn's waits to the background and aborting it.
  • Data: Knowledge MCP search strategies (447 tks) - Reference query patterns for using knowledge MCPs to discover organization-specific tool names, project identifiers, team names, and workflow details during plugin customization.
  • Data: MCP HTTP client capability validation rationale (189 tks) - Explains where required client capabilities are validated in the modern MCP HTTP request ladder and how the pre-dispatch gate affects observable precedence.
  • Data: MCP HTTP parameter header validation rationale (247 tks) - Explains validation of Mcp-Param headers against tool declarations and request arguments, including error shape and pre-dispatch precedence.
  • Data: MCP HTTP standard header validation rationale (326 tks) - Explains the modern MCP HTTP validation ladder's Mcp-Method and Mcp-Name header checks and their observed pre-dispatch precedence.
  • Data: MCP read resource control request (397 tks) - Documents the mcp_read_resource control request that reads one MCP Apps (SEP-1865) ui:// resource from a connected MCP server, its sandboxed-render requirement, SDK-server rejection, refused lanes and error cases.
  • Data: MCP server status error_code field (200 tks) - Schema description for the MCP server status error_code field, naming the host-fixable failure causes — a rejected claude.ai connector login, a rejected first-party Anthropic credential, and a project-scoped server awaiting approval — and noting that it is absent for every other failure and that new values are additive.
  • Data: Managed Agents outcomes (3058 tks) - Reference documentation for Managed Agents outcomes, including user.define_outcome events, rubrics, outcome evaluation events, deliverables, and interaction rules.
  • Data: Managed Agents quickstart — Contract tracker (689 tks) - Bundled Managed Agents quickstart template for a contract tracker agent that reads a Box contract, extracts clauses and dates, and creates Asana deadline and obligation tasks, with its agent.md definition and system prompt.
  • Data: Managed Agents quickstart — Data analyst (579 tks) - Bundled Managed Agents quickstart template for a data analyst agent that loads, cleans and charts datasets and can query Amplitude, with its agent.md definition and system prompt.
  • Data: Managed Agents quickstart — Deep researcher (798 tks) - Bundled Managed Agents quickstart template for a deep research agent that decomposes a question, cites primary sources and ends with a confidence-and-gaps section, with its agent.md definition and a user.define_outcome rubric.
  • Data: Managed Agents quickstart — Field monitor (813 tks) - Bundled Managed Agents quickstart template for a field monitor agent that scans technical blogs and writes a weekly Notion digest, with its agent.md definition and a Monday-morning cron deployment.
  • Data: Managed Agents quickstart — Incident commander (684 tks) - Bundled Managed Agents quickstart template for an incident commander agent that triages a Sentry alert, opens a Linear ticket and runs the Slack war room, with its agent.md definition and system prompt.
  • Data: Managed Agents quickstart — Sprint retro facilitator (870 tks) - Bundled Managed Agents quickstart template for a sprint retro facilitator agent that pulls a closed Linear sprint, reads Slack sentiment and writes a retro doc, with its agent.md definition and a twice-monthly cron deployment.
  • Data: Managed Agents quickstart — Structured extractor (545 tks) - Bundled Managed Agents quickstart template for a structured extractor agent that parses unstructured text into JSON that validates against a target schema, with its agent.md definition and system prompt.
  • Data: Managed Agents quickstart — Support agent (532 tks) - Bundled Managed Agents quickstart template for a support agent that answers from Notion docs with quoted sources and escalates low-confidence questions to Slack, with its agent.md definition and system prompt.
  • Data: Managed Agents quickstart — Support-to-eng escalator (709 tks) - Bundled Managed Agents quickstart template for an escalator agent that reads an Intercom conversation, reproduces the bug and files a linked Jira issue with a Slack note, with its agent.md definition and system prompt.
  • Data: Managed settings helper onFailure field (593 tks) - Schema description for the managed settings helper onFailure field, including source-dependent defaults, startup refusal behavior, static fallbacks, and background refresh handling.
  • Data: Managed settings helper retries field (311 tks) - Schema description for the managed settings helper retries field, including retryable failures, limits, per-attempt timeouts, backoff, and terminal failure handling.
  • Data: Message Batches API reference — C# (188 tks) - C# Batches API reference including batch creation, status polling, and result retrieval.
  • Data: Message Batches API reference — PHP (196 tks) - PHP Batches API reference including batch creation, status polling, and result retrieval.
  • Data: Message Batches API reference — Python (2038 tks) - Python Batches API reference including batch creation, status polling, and result retrieval at 50% cost.
  • Data: Message Batches API — TypeScript (1022 tks) - TypeScript usage guide for Claude's asynchronous Message Batches endpoint.
  • Data: Peer sender display name field (199 tks) - Schema description for the normalized display name on cross-session peer message senders.
  • Data: Plugin manifest types field (214 tks) - Schema description for the plugin manifest types field naming a self-contained .d.ts type contract for the noun the plugin's hooks module adds in engine.create, which dependent mods receive under .claude-plugin/types and claude plugin validate checks.
  • Data: Prompt suggestions paused control request (229 tks) - Documents the set_prompt_suggestions_paused control request that pauses or resumes a session's prompt suggestions at runtime and the process-local, non-persisted scope of that state.
  • Data: Query result pending command count (167 tks) - Describes the query result field that counts queued user sends still awaiting turns and clarifies when it is absent or zero.
  • Data: Rate limit grace signal (306 tks) - Describes the usage-limit grace-window signal tracked from the latest served response, including when it sets, clears, and how it interacts with overage status at hard exhaustion.
  • Data: Rate limit unified windows (325 tks) - Describes per-window subscription rate-limit utilization and reset data derived from unified rate-limit response headers.
  • Data: Remote tools reannounce control request (220 tks) - Documents the remote_tools_reannounce control request a replacement worker sends so the attached client re-announces a machine missing from its tool roster, including worker-epoch, once-per-epoch, ten-second and deadline rules.
  • Data: Review upload excluded changes error (327 tks) - Error shown when a review upload has no new commits or uploadable changes because every uncommitted file was excluded from the git bundle.
  • Data: Rewind files skippedLinks field (223 tks) - Describes the rewindFiles skippedLinks count, including link-safety refusal semantics and dry-run behavior.
  • Data: SDK API error kind field (1370 tks) - Documents the typed api_error kinds carried on SDK assistant messages that wrap an API error, and what each kind means for replaying, rewinding, or remedying the request.
  • Data: SDK footer indicator schema (249 tks) - Schema description for the SDK footer indicator, its environment-variable and cached-bootstrap sources, and its delivery on system/init and initialize responses so host UIs can render the terminal status pill.
  • Data: SDK frame_intake_phases_ms field (444 tks) - Schema description for the SDK turn-timing frame_intake_phases_ms field, breaking the wait between frame receipt and enqueue into named steps and their sum and presence invariants.
  • Data: SDK frame_received_wall_ms field (193 tks) - Schema description for the SDK turn-timing frame_received_wall_ms field recording when the triggering send's frame arrived on a session reading input from the session server's SSE stream, how it pairs with the enqueue and turn-start timestamps to split transit from queue wait, and when it is absent.
  • Data: SDK initialize response sdk_mcp_manifests_parked field (482 tks) - Schema description for the SDK initialize response sdk_mcp_manifests_parked field, reporting per server whether a manifest entry was parked, already connected, mismatched on protocol version, malformed, or not honoured, and when the field is absent.
  • Data: SDK set max thinking tokens request schema (477 tks) - Schema description for the SDK set_max_thinking_tokens control request, covering null reset versus omitted budget, session-scoped thinking_display overrides, and when the highlights display mode is accepted, downgraded to omitted, or refused.
  • Data: SDK set model system prompt field (243 tks) - Schema description for the internal set_model system_prompt field, including next-turn application with unchanged tool definitions, non-empty updates, feature overrides, and compatibility behavior.
  • Data: SDK system init plugin_errors field (315 tks) - Schema description for the plugin_errors array on the SDK system/init message, covering failed versus partially loaded plugins, name@marketplace and positional inline/synced tags, open-set error types, omission when clean, and Remote Control workers always omitting it.
  • Data: SDK thinking_duration_ms field (184 tks) - Schema description for the display-only thinking_duration_ms wrapper field giving how long a streamed thinking block took, excluding the wait for the first token, and when it is absent or not replayed to the model.
  • Data: Sandbox TLS termination setting (199 tks) - Describes the experimental sandbox.network.tlsTerminate setting, certificate behavior, Windows trust requirements, source precedence, and initialization validation.
  • Data: Sandbox credential environment no-match setting (188 tks) - Describes sandbox credential environment-variable onExtractNoMatch behavior, including warn, deny, error, and decode-path constraints.
  • Data: Sandbox credential file mask claims setting (179 tks) - Describes sandbox credential file maskClaims behavior for selectively masking decoded JWT payload claims while preserving other claims.
  • Data: Sandbox credential mask empty injectHosts warning (174 tks) - Warns that sandbox credential masks with empty injectHosts expose only sentinel values and explains how to resolve adapter, managed-settings, and local configuration causes.
  • Data: Sandbox deniedResolvedAddresses setting (209 tks) - Schema description for the sandbox deniedResolvedAddresses setting listing IP addresses or CIDR ranges an allowed hostname must not resolve to, its interaction with allowedDomains IP literals, and its exemption for parentProxy and mitmProxy routes.
  • Data: Sandbox filesystem disabled setting (227 tks) - Describes sandbox.filesystem.disabled behavior, platform limits, read-protection effects, and configuration precedence.
  • Data: Sandbox network domain spelling warning (278 tks) - Formats the sandbox diagnostic for unreliable network domain spellings and explains conservative enforcement until entries are corrected.
  • Data: Sandbox root without CAP_SETFCAP error (140 tks) - Linux sandbox dependency error explaining that running as uid 0 without CAP_SETFCAP makes every sandboxed command fail while writing a uid map on kernels 5.12+ and backports, and telling the user to grant CAP_SETFCAP or run as non-root.
  • Data: Self-hosted runner Anthropic git proxy credential warning (338 tks) - Runner warning that sources on hosts not routed through Anthropic-managed git clone with this machine's credentials, which --use-anthropic-git-proxy wipes from HOME-level git config, so credentials must live in /etc/gitconfig, GIT_ASKPASS, or an SSH key.
  • Data: Self-hosted runner GIT_ASKPASS governed hosts warning (311 tks) - Runner warning that a GIT_ASKPASS program answers for every host, so later git config could send this machine's credential for governed hosts through Anthropic's relay, and directs scoping or unsetting it along with core.askPass and SSH_ASKPASS.
  • Data: Self-hosted runner GIT_SSL_CAINFO trust bundle warning (254 tks) - Runner warning that GIT_SSL_CAINFO prevented building the combined certificate file for Anthropic-managed git, giving the failure cause and first remedy and directing the company CA into a per-server http sslCAInfo entry.
  • Data: Self-hosted runner GIT_SSL_NO_VERIFY lifecycle hook exception (330 tks) - Runner warning addendum explaining that checkout and post-session hooks of sessions with a repository on Anthropic-managed git get http.sslVerify=false with certificate checks re-enabled for the mount, while other sessions' hooks inherit the switch.
  • Data: Self-hosted runner GIT_SSL_NO_VERIFY session relocation note (325 tks) - Runner warning addendum explaining that inside a session GIT_SSL_NO_VERIFY becomes http.sslVerify=false that no longer covers the git mount or governed hosts, that per-server sslVerify takes precedence, and to name a company CA on certificate failures.
  • Data: Self-hosted runner client certificate relay warning (539 tks) - Runner warning that TLS client certificate variables set on the runner would be offered to the session relay rather than governed hosts, with remedies of asking for direct listing, unsetting the variables, or scoping sslCert and sslKey per URL.
  • Data: Self-hosted runner decode-token command help (869 tks) - Documents self-hosted runner token decoding, redaction, validation, input, and output command-line options.
  • Data: Self-hosted runner deferred shutdown timing notice (320 tks) - Explains deferred shutdown release and drain timing, supervisor timeout sizing, forced-kill consequences, and second-signal behavior for self-hosted runners.
  • Data: Self-hosted runner git-lfs hook warning (342 tks) - Runner warning that git-lfs's pre-push hook never runs inside lifecycle hooks, so a post-session git push sends LFS pointers without their objects, and how to push the objects or point core.hooksPath instead.
  • Data: Self-hosted runner orchestrator command help (1390 tks) - Documents self-hosted runner orchestrator connection, hook, SCM connector, runtime, health, and debug command-line options.
  • Data: Self-hosted runner session metrics help (622 tks) - Defines Prometheus HELP text for self-hosted runner session lifecycle counters.
  • Data: Streaming reference — C# (376 tks) - C# streaming reference including streaming events and the RawMessageStreamEvent TryPick methods.
  • Data: Streaming reference — Go (452 tks) - Go streaming reference including event handling, error checks, and final-message accumulation.
  • Data: Streaming reference — Java (287 tks) - Java streaming reference including streamed content-block delta handling and text extraction.
  • Data: Streaming reference — PHP (315 tks) - PHP streaming reference including streaming events and handling content block deltas (requires SDK v0.5.0+).
  • Data: Streaming reference — Ruby (116 tks) - Ruby streaming reference including basic streamed text handling.
  • Data: Structured tool output field schema (234 tks) - Schema description for the user-message tool_use_result field, including per-tool output shapes, the completed Agent or Task output contract, and the detachedToolCall placeholder for calls that stepped aside for a user message.
  • Data: Structured usage rate-limit rows field (177 tks) - Schema description for structured usage rate-limit rows, including server-defined meter ordering, null and empty semantics, and the synthesized header-fallback row.
  • Data: Submit feedback control request (231 tks) - Documents the internal submit_feedback control request that sends a /feedback report with the session transcript and sanitized error log, returns unavailable_reason when feedback is disabled or unsendable, and honors save_locally by writing a redacted local bundle instead.
  • Data: Telemetry variables ignored notice (268 tks) - Settings-status warning listing OTEL/telemetry environment variables a settings file sets that Claude Code ignores because such files can only turn telemetry off, with guidance on where to set them intentionally.
  • Data: Thin-client diff dialog schema (198 tks) - Internal data description for workspace git diff payloads used by the thin-client diff dialog.
  • Data: Token counting reference (665 tks) - Reference documentation for counting Claude model tokens with the Messages count_tokens endpoint and Anthropic SDK or CLI examples, including warnings against OpenAI tokenizers.
  • Data: Tool use display metadata field (172 tks) - Documents the tool_use_meta wire field carrying per-block display metadata for a message's tool_use blocks; it is wrapper-level UI metadata and is not replayed to the model.
  • Data: Tool use reference — C# (2401 tks) - C# tool use reference including defining tools and reconstructing response content for the follow-up assistant message.
  • Data: Tool use reference — PHP (3211 tks) - PHP tool use reference including the beta tool runner and the manual agentic loop with camelCase keys.
  • Data: Tool use reference — Ruby (444 tks) - Ruby tool use reference including the beta tool runner and manual agentic-loop guidance.
  • Data: Turn handoff available event schema (269 tks) - Schema description for the turn_handoff_available system event a cloud worker emits right after registering, carrying the tools and turn-handoff options its registration declared, and the rule that readers keep only the entry from the newest worker life.
  • Data: Turn handoff file_names field (283 tks) - Schema description for the turn_handoff file_names member listing user-attached files and their client-facing names that a capable worker copies into the session's home directory before running the handed-over calls, and when a malformed member is ignored.
  • Data: Turn handoff memory_context field (232 tks) - Schema description for the turn_handoff memory_context member carrying the claude.ai memory snapshot the client showed its model, how the worker writes it as a cowork_memory_context attachment line ahead of the handed-over messages, and when a malformed or uuid-colliding member is ignored.
  • Data: Upload device hook template request (200 tks) - Describes the cloud device request that uploads a vetted hook template to a worker before device hooks are registered.
  • Data: VCS state changed branch field (172 tks) - Describes the optional best-effort branch hint on vcs_state_changed events for commits and pushes, including multi-branch and uncertain-attribution behavior.
  • Data: VCS state changed event schema (392 tks) - Schema description for the vcs_state_changed system event as a best-effort repository cache-invalidation signal.
  • Data: Windows transcript read EBADF notice (180 tks) - Explains a Windows-only EBADF error reading the session transcript file likely caused by security or endpoint-management software intercepting file reads, and suggests excluding the .claude folder or allow-listing Claude Code before resuming.
  • Data: Working tree upload refusal for duplicated withheld file (211 tks) - Error refusing a working-tree upload because an index entry appeared holding byte-for-byte the content of a file that must stay on this machine, indicating something outside the upload wrote into its index copy.
  • Data: Working tree upload refusal for git dubious ownership (224 tks) - Error refusing a working-tree upload because git reports dubious ownership of the checkout or its .git, explaining that a safe.directory grant must stand in a file git reads since grants given only through GIT_CONFIG_PARAMETERS or GIT_CONFIG_COUNT do not reach the upload's git.
  • Data: Working tree upload refusal for misplaced .git entry (345 tks) - Error refusing a working-tree upload because the checkout's .git is a pointer file, symbolic link, hard-linked pointer file, or otherwise unfollowable entry, telling the user to start from the repository's ordinary main checkout instead.
  • Data: Working tree upload refusal for missing git objects folders (197 tks) - Error refusing a working-tree upload because the git directory lacks objects/info or objects/pack, as after a copy that skips empty folders, telling the user to check for links with ls -ld and then recreate both with mkdir, or start from a fresh clone.
  • Data: Working tree upload refusal for private git directory setup failure (349 tks) - Error refusing a working-tree upload because its private git directory could not be prepared under the configuration home, telling the user to check that the home and its seed-admin folder are directories only they can write, inspect them with ls -ld, remove scratch directories or links by name without a trailing slash, and retry.
  • Data: Working tree upload refusal for unread git config environment variable (305 tks) - Error refusing a working-tree upload because GIT_CONFIG_GLOBAL or GIT_CONFIG_SYSTEM names a git configuration file a session could change, so the upload's git does not read it, directing the user to move its settings into ~/.gitconfig or git's default system file and remove the variable, or keep the file outside session-writable folders.
  • Data: allowManagedPermissionRulesOnly allowed-tools frontmatter scope (424 tks) - Continues the allowManagedPermissionRulesOnly schema description: skill, command, and plugin allowed-tools frontmatter is ignored except for managed and bundled skills and plugins on admin-backed channels such as pinned managed marketplaces, attested claude.ai-synced plugins, and host-delivered --plugin-dir plugins.
  • Data: allowManagedPermissionRulesOnly deny rules still apply (45 tks) - Closes the allowManagedPermissionRulesOnly schema description by noting that --disallowedTools, skill disallowed-tools, and other command-line or session deny and ask rules still apply.
  • Data: allowManagedPermissionRulesOnly setting (66 tks) - Schema description for the managed allowManagedPermissionRulesOnly setting, which ignores permission rules from user, project, local, and --settings files and --allowedTools allow rules so only managed settings can add allow rules.
  • Data: allowedMcpServers setting (204 tks) - Describes how the enterprise allowedMcpServers setting governs user-added versus organization-delivered MCP servers, including ${VAR} expansion, undefined and empty-array behavior, and denylist precedence.
  • Data: availableModelsMatch setting (315 tks) - Schema description for the managed availableModelsMatch setting, contrasting prefix and exact matching of availableModels entries, family and release-dependent alias handling, Default-model restriction with startup failure, and which background and helper requests stay unrestricted.
  • Data: deniedModels setting (222 tks) - Schema description for the managed deniedModels setting, covering family-alias blocking, version-wide model ID blocking across dates, -fast and provider prefixes, ignored release-dependent aliases, and Default-model step-down or startup failure.
  • Data: syncClaudeAiPlugins setting (332 tks) - Describes how the syncClaudeAiPlugins setting disables account-synced plugin downloads, availability, and cleanup across user, managed, workspace, and invocation scopes.
  • Data: syncClaudeAiSkills setting (314 tks) - Describes how the syncClaudeAiSkills setting disables account-synced skill downloads, availability, and cleanup across user, managed, workspace, and invocation scopes.

System Prompt

Parts of the main system prompt.

System Reminders

Text for large system reminders.