{"version":"2.1.305","anchor":"usage-report-peak-parallelism-and-recommendations-toggle","canonical_anchor":"usage-report-peak-parallelism-and-recommendations-toggle","heading":"Usage report works out how many sessions ran at once","tier":"internal","area":"Usage Report","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/usage-report-peak-parallelism-and-recommendations-toggle","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### Usage report works out how many sessions ran at once\n\nThe usage report's analysis now calculates the most sessions running at the same time, adds per-day and per-week detail, and blanks some recommendations\n\n**Unclear.** Where the peak number of parallel sessions appears in the report is not clear.\n\n**What**\n\nThe analysis behind the usage report now works out a peak: the largest number of sessions running at the same time within a period. The report also now receives a live flag along with per-day and per-week detail, and for some sessions its recommendations are left empty.\n\n**Why**\n\nThe usage report has more data to draw on about how you work, including how many sessions you run side by side.\n\n- Flag `tengu_amber_lark`: Off in both readings (read for one account on one subscription tier against v2.1.305; this account: off, anonymous baseline: off, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Usage Report\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}