your impact

Local first. Your numbers are yours.

ebb-ai writes a per-task carbon receipt to a SQLite ledger on your own machine. Nothing leaves your device. This page explains how to read those numbers.

Where your data lives

Every dispatched task writes one row to ~/.ebb-ai/queue.db — a local SQLite file. Schema: task_id, dispatched_at, region, intensity_g_co2_per_kwh, estimated_carbon_g, actual_carbon_g, intensity_source (one of scheduled / current / expedited).

The Claude Code plugin, the OpenClaw plugin, the MCP server, and the CLI all read and write this same file — defer in one host, check in another.

Read it from the CLI

# Install once
npm install -g @ebb-ai/cli

# Personal-impact summary (counts, totals, per-region, achievements)
ebb stats

# Programmatic
ebb stats --json | jq '.totalEstimatedCarbonGCo2'

# Filter by date
ebb stats --since 2026-05-01

# Per-task receipt
ebb receipts list
ebb receipts show <task_id>

What the summary covers

Cumulative impact: total tasks dispatched, accounted CO₂e in grams, cleanest-window hit rate (scheduled vs. expedited), and run-now overrides.
By region: dispatch counts and totals broken down by grid zone (CISO, ERCO, GB, FR, DE, etc.).
Band distribution: histogram of how dirty/clean the grid was at each dispatch (very_clean → very_dirty).
Achievements: local-only milestones (no leaderboard, no upload). The full list is below.

Achievements (local-only)

These unlock against your local ledger as you queue and ship tasks. There's no server tracking; checking them just walks your SQLite rows.

First Deferral

Queue your first ebb-ai task.

Ten Up

Ship 10 deferred tasks.

Centurion

Ship 100 deferred tasks.

Long Run

Ship 1 000 deferred tasks.

World Tour

Dispatch across three or more grid regions.

Sniper

Honour the scored window for 90% of completed tasks.

Endurance

Active across 7+ calendar days.

Why not show aggregate numbers here?

Every public dashboard that summarizes user impact has to either (a) phone home with telemetry — which we explicitly decided against in v0.8 — or (b) fabricate aggregate numbers that look real but aren't. Both are bad. Local-first is honest.

v0.9 will add an opt-in, signed-anonymous-event aggregate counter that the site can read (no per-user identifying data). Design is at docs/spec/proposal/v09-leaderboard.md. Until then, your stats live on your machine and only there.