PulseAugur
EN
LIVE 21:25:35

Claude Code prompt cache costs analyzed, revealing fixed overhead and launch path impact

An analysis of Anthropic's Claude Code revealed that the launch path significantly impacts prompt cache costs. Using the VSCode extension or an internal VSCode terminal resulted in hitting a shared server-side cache, whereas a standalone terminal did not, leading to higher costs. The study found that approximately 85% of the cache creation cost is fixed overhead by Claude Code itself, with only about 15% being controllable by the user through trimming files or skills. Furthermore, subagents launched by Claude Code do not inherit the parent session's cache, each incurring its own fixed cost, which can multiply expenses when running multiple subagents in parallel. AI

IMPACT Understanding Claude Code's cost structure can help developers optimize usage and manage expenses.

RANK_REASON Analysis of a specific product's cost structure and usage patterns.

Read on dev.to — Anthropic tag →

AI-generated summary · Google Gemini · from 1 sources. How we write summaries →

Claude Code prompt cache costs analyzed, revealing fixed overhead and launch path impact

COVERAGE [1]

  1. dev.to — Anthropic tag TIER_1 English(EN) · Sho Naka ·

    I Measured Claude Code's Prompt-Cache Cost Three Ways. 85% of It Wasn't Mine to Trim.

    <p>I ran the same empty Claude Code project through three launch paths and read the cache tokens off the session log after every turn. One of those paths never touched the shared server-side cache at all — <code>cache_read</code> stayed at 0 on every run.</p> <p><strong>TL;DR: th…