{"version":"2.1.314","anchor":"cost-tracker-emits-a-spendrecorded-event","canonical_anchor":"cost-tracker-emits-a-spendrecorded-event","heading":"Claude Code now signals each time it records spending","tier":"internal","area":"Cost Tracking","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/cost-tracker-emits-a-spendrecorded-event","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Claude Code now signals each time it records spending\n\nRecording cost or token use now sends a signal that other parts of Claude Code can react to\n\n**Unclear.** Nothing shows whether this changes any spending display or limit that users see.\n\n**What**\n\nWhenever Claude Code records cost or token use, it now sends out a `spendRecorded` signal. Tokens are the small chunks of text the model reads and writes, and they are what usage is measured in. This applies to the main conversation, to side requests and to tokens spent. Before, recording only updated the running totals. The way usage figures are read was also reworked.\n\n**Why**\n\nOther parts of Claude Code can now react to spending as it happens, rather than reading totals later.\n\n- Area: Cost Tracking\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}