claude-carbon plugin
A Claude Code plugin that shows a session's CO2 estimate in the status line next to its cost
- 245 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Adds hooks and a status line script to Claude Code that estimate emissions from token usage
- Writes session history to a local SQLite database and reads past transcripts
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/claude-carbonDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Adds hooks and a status line script to Claude Code that estimate emissions from token usage
- Writes session history to a local SQLite database and reads past transcripts
This is third-party code. Review the repository files before installing.
What it does
The plugin adds a live CO2 estimate to the Claude Code status line, computed locally from token usage. Each session is stored in a local SQLite database, so history survives the purge of old logs. It backfills from existing transcripts and offers commands: a text report, an image card and the footprint of a single pull request. A README badge can show the all-time total, and the methodology with sourced factors is public.
Who it is for. For developers who want to see the environmental footprint of their Claude Code sessions next to the cost.
Good fit when
- You want a session CO2 estimate right in the status line
- You need an emissions report for a period or a pull request
- You track a team's footprint and want a README badge
Not a fit when
- You do not use Claude Code
- You do not need an emissions estimate and the cost counter is enough
- You do not want to install hooks and a local database
Example request
Show the CO2 emissions report for the last week and build an image cardLimitations
This is an estimate from token usage, not an exact measurement; the factors and methodology are documented in the repository. It works with Claude Code. Installing from a third-party community marketplace may fail on an old pinned version, so the authors recommend their own install commands. MIT licensed.
How to disable. Uninstall the claude-carbon plugin through the plugin manager and, if you like, remove the local database and the README badge.
FAQ
Where does the emissions number come from?
It is computed locally from the session's token usage using open factors; the sourced methodology is in the repository.
Does data leave the machine?
No, history is kept in a local SQLite database on your machine.
Discussion
No questions or reviews yet.
Related
Pluginsclaudetop shows session cost, cache hit rate, plan limit windows and overspend alerts in the Claude Code status line
A Claude Code plugin: a status line with context, 5-hour and 7-day limits, cost and usage of Codex, Gemini and z.ai
A real-time terminal monitor for Claude Code usage: tokens, messages and cost in the five-hour window, with forecasts and export
A Claude Code status line showing 5-hour and 7-day quota use plus the pace: whether what is left lasts until the window resets
claudeline draws a Claude Code status line: plan, model, context usage and 5-hour and 7-day limits.
A Claude Code status line with 5-hour and weekly limit usage, reset countdowns, model and prompt cache lifetime
README in short
The README describes an open Claude Code plugin that puts a live CO2 estimate in the status line next to session cost. Data is stored in a local SQLite database and backfilled from existing transcripts. Slash commands give a text report, an image card and a pull-request footprint, and a README badge shows the all-time total. Install via npx or a script for macOS, Linux and WSL, with a separate Windows path. MIT licensed, with an open methodology of factors.