Your team runs Claude Code in three places. Count it as one.
Laptops, cloud sessions and CI each report their own usage. SessClone collects every Turn into one ledger your whole Org can read, priced and per person.
$ claude plugin marketplace add NotTahaAli/sessclone$ claude plugin install sessclone- Laptop · 41 turns$6.12
- Cloud sessions · 18 turns$2.40
- CI · 4 turns, running$0.31
- One Org, one total$8.83
How it counts
On the machinepluginA hook reads each finished Turn. Nothing is proxied.
On the wire~300 B/turnPushes from its cursor, never the whole session.
In the ledgerpricedDated rates. An unknown one reads as unpriced, never $0.
Questions
- Do you read our code?
- No. Usage counters and identifiers are what the Collector reports, and that is all the dashboard needs. Transcripts contain source code, so archiving them is off by default and each Member turns it on for themselves, per Project. Nobody can turn it on for somebody else.
- How does it see cloud sessions and CI?
- The same plugin. A cloud environment installs it in its setup script, and the key goes in an API credential, so the proxy adds it on the way out and it never sits in the container. A cloud session keys by account rather than by container, so every container a Member burns through collapses into one Device.
- What happens when a session is killed?
- The Collector reports from a cursor and re-reports on restart. A Turn has an identity, so the same Turn reported twice leaves one row, and a run that died mid-stream is marked incomplete rather than silently counted as a total.
- Can we run it ourselves?
- Yes, free, at any size: your database, your storage, your network. It is AGPL-3.0, so keep the panel’s licence notice and SessClone credit visible, and if you run a modified copy for other people, offer those users its source.