{"version":"2.1.290","anchor":"cumulative-cost-pushed-to-the-remote-session-mid-turn-throt","canonical_anchor":"cumulative-cost-pushed-to-the-remote-session-mid-turn-throt","heading":"Running cost can now be sent to remote sessions during a turn","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/cumulative-cost-pushed-to-the-remote-session-mid-turn-throt","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Running cost can now be sent to remote sessions during a turn\n\nClaude Code can now send the session's running cost and token count to a remote session during a turn, at most once per set interval\n\n**Unclear.** It is not settled whether Claude Code actually sends these mid-turn updates yet.\n\n**What**\n\nClaude Code keeps a running total of a session's cost and the tokens (the units of text the model reads and writes) it has used. It can now send that total to a remote session while a turn is still under way, no more than once per set interval. Before, it sent the total only when it had changed.\n\n**Why**\n\nApps showing a remote session can keep the cost up to date during a long turn instead of waiting for it to end.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}