Developer profile
A developer profile is one developer's engagement, effort, AI usage, and code quality over the selected period. You reach it by selecting a name in any roster, on a dashboard or in developer traces.
- Deployment: SaaS, On-premises
The profile is a read of one person's captured work. For the exact definition of any metric on it, see the Metrics glossary.
What the profile covers


The profile is organized into sections:
- Engagement at a glance: active days, AI-active days, High-AI-usage days, and an activity heatmap.
- Where the effort went: effort by repository or work area.
- Working with AI: the human-versus-AI contribution mix, AI usage and spend, and tool mix.
- Code quality: Completion rate, stale work, and AI abandonment rate.
- Work & activity: change volume and risk, and work branches.

Some fields are deliberately blank
The profile follows the platform's honesty convention: a field shown as not yet available is telling you the evidence is missing, not that the value is zero. Those fields are shown as unavailable rather than guessed at.
Two reads in particular are worth understanding:
- The human-versus-AI split is based on retained work attribution, not on IDE time. It reflects who wrote the kept lines, not how long an editor was open.
- Unattributed work is left out of the split. Kept lines that carry no human or AI evidence are not forced onto one side, which can make the split cover less than all of the person's work.
Related
- Members and developers — how a person's captured activity forms their identity.
- Value points — the human and AI split shown on the profile.
- Validate data with developer traces — auditing the numbers behind a profile.
- Metrics glossary — the profile's metrics defined.