User audits Claude Code transcripts, finds long sessions with breaks cause high costs due to cache expiry
A user auditing their Claude Code transcripts discovered that long sessions with breaks are expensive because prompt caching expires after one hour, forcing full history rewrites at premium prices. The user shares details on cache economics to help others optimize usage.
Entities
Related
User reports 30% Fable consumption waste from cache rewrites in long Claude Code sessions
A Claude Code user audited their transcripts and found that long sessions with breaks caused frequent cache expiration, leading to 30% wasted Fable consumption. Prompt caching re-reads history at 10% of normal input price but has a 1-hour window; when it expires, each turn replays full conversation history at full cost.
Users report Claude Code consuming excessive usage due to large context bug
Multiple users report that Claude Code consumes 20-40% of their usage allowance per session due to a bug that sends 300k+ message contexts even on fresh sessions. One user lost significant paid usage before realizing the issue. Another user describes a layered configuration setup with CLAUDE.md and AGENTS.md files, and a cleanup that removed ~700MB of empty content but still faced model selection inefficiencies.
Local CLI tool to analyze Claude AI token usage and costs
A Go-based CLI that parses local Claude AI logs to show token usage and cost breakdown by project, session, and model. It helps users understand where their API quota is going and how much they would have spent without caching.
CLI to analyze Claude Code session token costs
Tokenbill is an open-source CLI tool that parses local Claude Code session logs and estimates token costs. It runs entirely offline with no network calls, helping developers understand and optimize their Claude Code usage costs.
Developer criticizes prompt caching fees for one-shot inference workloads
A developer argues that prompt caching fees are unjustified for task-oriented applications like document processing and data extraction, where prompts are never reused. The post highlights frustration with paying a premium for cache writes that provide no benefit for unique, one-shot inference tasks.
