Understanding Your Claude Code Spend: What’s Actually Driving the Cost

Teams using Claude Code often face unexpected cost issues, not from conversation history, but from accumulated overhead before any work starts, such as loading MCP servers, memory files, and other components. This issue, termed the Session Startup Problem, is compounded by a lack of organizational visibility into what is being loaded, which developers have the most overhead, and whether lighter models might suffice. This context accumulation happens as developers add elements for projects that remain connected even after completion, increasing session overhead unnoticed. Default model selection also contributes to costs, as teams often use more expensive models like Opus for tasks where cheaper models like Sonnet would suffice. Current tools only provide session-level visibility, lacking the capacity to identify specific cost drivers at the organizational level. Opik's Cost Intelligence aims to address this by offering real-time spend insights at the org level, breaking down where tokens are used, and suggesting configuration changes based on actual usage patterns, resulting in significant spend reductions. Despite improvements like Anthropic's lazy loading for tool schemas, the issue of organizational visibility remains unsolved, highlighting the importance of examining what's loaded into context by default across teams.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.