Tab · Insights
Activity ledger
Prove who did what, with consent, before the contractor invoice goes out. Per-developer session timing, prompt cadence, files touched. The contractor-governance surface — consented, disclosed, signed.
See it in motion
Where to find it
- Localhost:
/activity-ledger.html?repo=<id> - API:
GET /api/activity-ledger?repo=<id> - Keyboard: ⌘ K then
ledger - Sidebar: Insights → Activity ledger
What it does for you
One row per developer, per day.Session count, active hours (idle-capped), files touched, prompts written. The active-hours number is the honest one — it subtracts idle gaps, so it matches what you'd defend on a timesheet.
Consent badge on every row.Each developer's rows carry their consent record (date + scope). No consent, no capture — and the row makes that visible.
Integrity badge so the invoice holds up.A signed journal tells you the row hasn't been hand-edited.
verified, no-journal-yet, or tampering-detected — read it before you send the invoice.Configure
Privacy mode (metadata-only or content-redacted) is set in Settings. Team-tier orgs pin a floor (e.g. force metadata-only for contractors); the desktop shows the 🔒 pinned state when bound.
Use it well
Before paying a contractor, open the ledger for their date range. Sort by active hours; spot-check one expensive session with a click-through to the per-prompt view. If the integrity badge isn't green, fix that before sending money.