mlco2/codecarbon

Allow all options to `codecarbon monitor`

Open

#1,273 opened on Jul 26, 2026

View on GitHubContributor guide
 (1 comment) (0 reactions) (0 assignees)Python (306 forks)auto 404
enhancementgood first issue

Repository metrics

Stars
 (1,885 stars)
PR merge metrics
 (PR metrics pending)

Description

Is your feature request related to a problem? Please describe. When I run codecarbon monitor --help I only see:

╭─ Options ────────────────────────────────────────────────────────────────────────────────────────────────╮
│ --measure-power-secs                    <int>  Interval between two measures. [default: 10]              │
│ --api-call-interval                     <int>  Number of measures between API calls. [default: 30]       │
│ --api                   --no-api               Choose to call Code Carbon API or not [default: api]      │
│ --offline               --no-offline           Run in offline mode [default: no-offline]                 │
│ --country-iso-code                      <str>  3-letter country ISO code for offline mode                │
│ --region                                <str>  Region/province for offline mode                          │
│ --log-level                             <str>  Log level (critical, error, warning, info, debug)         │
│                                                [default: error]                                          │
│ --help                                         Show this message and exit.                               │
╰──────────────────────────────────────────────────────────────────────────────────────────────────────────╯

Describe the solution you'd like

I would like to have all the options of the package, like PUE, WUE...

It need to be a dynamic implementation, to always be synchronised with the package.

Describe alternatives you've considered You can already use the .codecarbon.config to set the option.

Contributor guide

Research direction
Inspect the `monitor` command implementation in the codecarbon CLI. Identify where options are defined and how the package's configuration model (e.g., Pydantic or dataclass) stores settings. Look for existing patterns for exposing options dynamically in other commands or libraries. Consider using the `typer` library's ability to create dynamic options or implement a custom callback that generates options from the configuration schema.
Tech stack
python
Domain
clideveloper experiencetooling
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GitPythonFamiliarity with CLI frameworks
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50