{"version":"2.1.318","anchor":"usage-guide-prompt-notes-sessions-left-out","canonical_anchor":"usage-guide-prompt-notes-sessions-left-out","heading":"Usage reports leave out sessions from other accounts and say how many were left out","tier":"notice","area":"Insights","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/usage-guide-prompt-notes-sessions-left-out","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Usage reports leave out sessions from other accounts and say how many were left out\n\nThe usage scan now skips sessions from other accounts or organizations, and usage guides must say how many sessions were left out\n\n**Unclear.** It is not clear which command produces this guide or whether it is available to all users.\n\n**What**\n\nClaude Code can scan your recent sessions to build usage reports and a usage guide. A session is one conversation with Claude Code, saved as a file on your computer.\n\n- Before, every recent session file was scanned. Now sessions that belong to a different account or organization are skipped.\n\n- The scan counts the sessions it skipped (`leftOutSessionCount`) and reports that count as `sessionsLeftOut`.\n\n- The usage data also carries `sessionProvenance`, a record of where the sessions came from.\n\n- When `sessionsLeftOut` is above 0, the prompt that writes the usage guide tells Claude that those sessions could not be tied to the current sign-in. Claude must say so under \"How We Use Claude\" and again when it presents the draft.\n\n**Why**\n\nIf you switch between accounts or organizations on one computer, your usage output no longer mixes in sessions from the others. When some sessions are left out, the guide tells you, so you know its numbers are incomplete.\n\n- Area: Insights\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}