Command Center
Claude Code health across 500 engineers · last 30 days
Activity
Sessions and active engineers · last 30 days
Real work
Inferred work threads across the org — the track layer between session and standup
- Saved-filters panel rebuildweb-storefront · 4 sessions · 4 engineers · 17 cycles2.8h19M tokens
- Token theming rolloutdesign-system · 3 sessions · 3 engineers · 30 cycles5.8h12M tokens
- Checkout retry logic hardeningweb-storefront · 3 sessions · 3 engineers · 15 cycles3.1h10M tokens
- Usage-metering accuracybilling-core · 2 sessions · 2 engineers · 9 cycles2.2h10.0M tokens
Threads are inferred from session telemetry — clustering and titles are PROXY. Evidence of agent-assisted activity only: it does not verify delivery, and coverage of non-agent work is unknown by design.
Departments
Adoption & health by department
| Department | Eng. | Adoption | Craft | Tokens | Risks |
|---|---|---|---|---|---|
Product Engineering Priya Nair | 182 | 86% | 74 | 10.3B tokens | 7 |
Platform Marcus Feld | 121 | 91% | 81 | 8.4B tokens | 3 |
Infrastructure & SRE Deepa Rao | 88 | 72% | 68 | 5.4B tokens | 2 |
Data & ML Tom Weaver | 109 | 79% | 71 | 7.2B tokens | 3 |
Coaching throughput
What coaching delivered — throughput, not names
This shows what coaching delivered — never who was coached — so it reads the same in both trust modes. At this altitude you steer with the craft distribution and this throughput, not names.
Executive summary
Auto-generated · every claim measured or labeled an estimate
Adoption is 83% and rising (5% MoM). ~86 engineers are still dormant — activation is the single biggest lever left.
Average craft posture is 74/100 (+2 pts); 51% of active engineers sit at ≥70. Teams are improving most on plan-mode and verification discipline — using the agent well, not just using it.
5.5B tokens/mo of tokens is optimizable (18%) — mostly model right-sizing and low cache-hit. Projections are audited: the ledger in Token Efficiency shows what each acted move actually saved, including the moves that saved nothing.
27 risky patterns (secrets, destructive commands, prod access) were flagged in-session — measured directly from telemetry.
Risk flags
15 open
- low
- critical
- medium
- critical
- low