{"version":"2.1.280","anchor":"context-usage-reporting-is-now-awaited-and-errors-are-caught","canonical_anchor":"context-usage-reporting-is-now-awaited-and-errors-are-caught","heading":"Context usage reporting is now awaited and errors are caught","tier":"notice","area":"Context Usage","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/context-usage-reporting-is-now-awaited-and-errors-are-caught","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Context usage reporting is now awaited and errors are caught\n\nContext usage reporting is now awaited and its errors are caught before other logic runs\n\n**What**\n\nWhen Claude Code reports how much of the context window (the space available for the conversation) has been used, it now waits for that report to finish, and wraps it in error handling, before moving on to idle-report and cost-push logic. Previously this report was fired off without waiting for it to complete.\n\n**Why**\n\nThis prevents a context-usage report from silently failing or racing with the logic that runs after it, making that sequence more reliable.\n\n- Area: Context Usage\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}