Spend · Team activity

Team activity

Every AI-assisted session, every developer, every dollar - and the proof it's untampered. The team-rollup view of the per-developer activity ledger. Filter by date range, by repo, by developer. Drill into any binding for session-by-session and day-by-day detail. Export for compliance.

See it in motion

Where to find it

  • Hosted: https://repoops.ai/team/activity
  • Drill-down: /team/activity/[bindingId] - one developer, broken out by session and by day.
  • Export: GET /api/team/activity/export?format=csv|json&view=devices|developers - the compliance artifact.
  • Source: The desktop's Layer-B telemetry streamer pushes here every 5 minutes while it's online, once you've bound the install to a team and turned on streaming.

What it does for you

You'll see what each developer did - without surveillance.Session timing (idle-capped), prompt cadence, files touched, model mix, spend. Consented, disclosed, never silent. The audit trail for contractor work.
Integrity proofs you can show a client.Every row is append-only and server-witnessed. Gap / tamper / server-redaction events land in the audit log. The integrity record on each binding tells you whether any row went missing, rolled back, or needed server-side re-redaction after the desktop streamed it.
Export to whatever your compliance team wants.CSV for the SOC 2 auditor, JSON for the security review, per-developer rollup for finance. Same data, three shapes.

Configure

Server-owned policy from /team pins capture mode here. Date range, per-repo filter, and view (devices vs. developers) are URL params.

  • ?since=7d|30d|90d|1y|all - retained-history window selector.
  • ?repo=<id> - scope to one tracked repo.
  • ?view=developers - switch from per-device to per-developer rollup.
  • Sensitive-path watchlist (set on /team) - drives the integrity flags rendered per row.

Use it well

  1. Open weekly with the previous 7-day window.

    Spot stale bindings (last-seen > 24h on an active contractor), unexpected spend spikes, repos with no activity.

  2. Drill into a binding when something looks off.

    Per-binding view shows session-by-session detail - model mix, files touched, the idle gaps. Most "low activity" is actually missed binding, not low work.

  3. Export at month-end for finance + audit.

    CSV for finance (per-developer rollup, sums); JSON for the audit team (full rows with integrity markers).

  4. Watch the integrity badge.

    A red badge means a row was edited after first write OR the desktop streamed a payload that didn't match its signature. Either case = investigate, don't bill against.

Read more