Answer: You can watch cache performance live with a statusline script that reads the `current_usage` object, or run `/usage` for a per-session summary showing the session's hit ratio, miss count, and whether the cache is warm. Status: Confirmed Entry: tool/claude-code/troubleshooting/check-cache-performance Revision: 2 Digest: sha256:098acd533486a64a (changes whenever the content changes) Timeline: Created: 2026-11-13T02:28:05Z Last changed: 2026-11-18T12:19:29Z (Session summary contents: — → hit ratio, miss count, and whether the cache is warm right now) Last verified: 2026-11-20T12:24:17Z Next check: 2026-11-21T12:24:17Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Live method | statusline script | [1] | 2026-11-20 Cache read field | cache_read_input_tokens | [1] | 2026-11-20 Cache creation field | cache_creation_input_tokens | [1] | 2026-11-20 Per-session summary command | /usage | [1] | 2026-11-20 Session summary contents | hit ratio, miss count, and whether the cache is warm right now | [1] | 2026-11-20 Minimum version | v2.1.251 | [1] | 2026-11-20 Likely-cause minimum version | v2.1.260 | [1] | 2026-11-20 Sources: [1] Anthropic. "How Claude Code uses prompt caching". https://code.claude.com/docs/en/prompt-caching.md Role: primary. Accessed: 2026-11-20T12:24:17Z Quote: "The most direct way to watch them live is a [statusline script](https://code.claude.com/docs/en/statusline.md) that reads the `current_usage` object" (Supports: Live method) Quote: "`cache_read_input_tokens` | Tokens served from cache on this turn" (Supports: Cache read field) Quote: "`cache_creation_input_tokens` | Tokens written to the cache on this turn" (Supports: Cache creation field) Quote: "For a per-session summary, run `/usage`." (Supports: Per-session summary command) Quote: "showing the session's hit ratio, miss count, and whether the cache is warm right now" (Supports: Session summary contents) Quote: "Both require Claude Code v2.1.251 or later." (Supports: Minimum version) Quote: "The likely-cause text requires Claude Code v2.1.260 or later." (Supports: Likely-cause minimum version) Published: 2026-11-20T02:58:36Z Snapshot SHA-256: 6dd7b7540098e8cdfaa2d530c1a887d120f5e095624e8cac5e3821cf54736a54 (captured 2026-11-20T12:24:17Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. Cross-check: not-available at 2026-11-20T12:24:17Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:24:17Z Last attempt: 2026-11-20T12:24:17Z Notes and limitations: Extracted automatically from a single official source (section "Check cache performance"). Related: https://latestn.com/tool/claude-code/troubleshooting/check-loaded-context How do I check which CLAUDE.md, settings, hooks, or MCP servers actually loaded in Claude Code? https://latestn.com/tool/claude-code/troubleshooting/configure-tmux How do I configure Claude Code to work properly inside tmux? https://latestn.com/tool/claude-code/troubleshooting/confirm-hipaa-configuration How do I confirm the HIPAA configuration is applied on a developer's computer? https://latestn.com/tool/claude-code/troubleshooting/auto-mode-classifier-notice-cause Why does Claude Code show the notice that this session isn't eligible for auto mode's no-charge classifier requests? https://latestn.com/tool/claude-code/troubleshooting/aws-gateway-troubleshooting How do I troubleshoot issues when deploying Claude apps gateway on AWS? https://latestn.com/tool/claude-code/troubleshooting/beta-header-pass-through What happens in Claude Code when a gateway strips beta headers or body fields? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-18T12:19:29Z | changed | Session summary contents: — → hit ratio, miss count, and whether the cache is warm right now | [1] 2026-11-18T12:19:29Z | changed | Summary line: Prompt cache (main) → — | [1] 2026-11-13T02:28:05Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/claude-code/troubleshooting/check-cache-performance/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/claude-code/troubleshooting/check-cache-performance POST: https://latestn.com/dispute/tool/claude-code/troubleshooting/check-cache-performance with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/claude-code/troubleshooting/check-cache-performance?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How can I check Claude Code's cache hit rate or cache performance? Revision 2, last verified 2026-11-20T12:24:17Z. https://latestn.com/tool/claude-code/troubleshooting/check-cache-performance (accessed 2026-11-21T09:53:47Z). @misc{LatestN_tool_claude_code_troubleshooting_check_cache_performance_r2, title = {How can I check Claude Code's cache hit rate or cache performance?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/claude-code/troubleshooting/check-cache-performance}}, note = {Revision 2; digest sha256:098acd533486a64a; last verified 2026-11-20T12:24:17Z; accessed 2026-11-21T09:53:47Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/claude-code/troubleshooting/check-cache-performance