Claude Code shows a single usage number for the whole account — the same on every machine. Claude Room breaks it down per person, so you can see exactly whose sessions are driving the limit before you hit it.
zero config · works offline · free & open source
Share one Claude account and the status line shows one combined percentage — identical on every machine, with no way to tell whose sessions are driving it. When the account gets throttled before reset, nobody knows why, and nobody can plan around it.
Each person's estimated share of the account's real 5-hour and 7-day limits — derived from their cost inside the window. See who's driving usage, without ranking or blaming anyone.
Know whether you're ahead of, on, or within pace for the window — so a reset never blindsides the team.
Cost, tokens, and percentages leave your machine — prompts, code, and files never do. By design, not policy.
Install the extension and it wires Claude Code's status-line hook itself. Nothing to set up, works offline first.
Delta-based accounting per session and per window — resumed sessions, parallel tabs, and window boundaries are all handled, so daily peaks and costs are trustworthy.
Each person adds the VS Code extension. It hooks into Claude Code automatically — no config, no account setup.
On every render it captures Claude Code's official cost and rate-limit fields, then syncs only aggregates to your Room.
Your slice shows right in VS Code. The account owner signs in to the dashboard for the full per-member breakdown.
A live status-bar item and a full panel: your share of the room, the team's pace, your cost and tokens this window, per-session context, and recent activity — all scoped to your room, never the account-wide blend.
for VS Code, Cursor, Windsurf & VSCodium
Claude Room is free and open source — no seats, no plan, no catch. If it saves your team a headache, the nicest thing you can do is buy me a coffee.