Follow Discord
Sweep 03 Nov 2026 · 22:27Z Build v2.1.318 536 read Stable v2.1.311 Latest v2.1.318 Next v2.1.318 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.318 ·

Usage reports leave out sessions from other accounts and say how many were left out

The usage scan now skips sessions from other accounts or organizations, and usage guides must say how many sessions were left out

Group of 2 You'll notice Improvements
JSON All of v2.1.318
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
InsightsArea: what it touches
ImprovementsKind: in v2.1.318,
ImprovementsSection of the release

Unclear It is not clear which command produces this guide or whether it is available to all users.

What

Claude 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.

  • Before, every recent session file was scanned. Now sessions that belong to a different account or organization are skipped.
  • The scan counts the sessions it skipped (leftOutSessionCount) and reports that count as sessionsLeftOut.
  • The usage data also carries sessionProvenance, a record of where the sessions came from.
  • 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.

Why

If 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.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear which command produces this guide or whether it is available to all users.

See this entry in the whole of v2.1.318 →

Feedback