Each member needs the cubic CLI, which installs git-ai
to record AI authorship on each commit. Until cubic finds git-ai data for the period, the tab
shows only setup steps and an Install CLI link. See AI attribution
tracking.
AI coding adoption
The AI coding adoption chart shows lines of code authored by AI and by humans over time.
The header shows % of AI code: the share of attributed lines written with AI help (AI plus
AI + human). Lines from commits without attribution are left out. A Total lines with AI
line runs over the bars. Two controls change the chart:
- Normalize: switches from line counts to percentages.
- Day and Week: change the interval each point covers.
Team members
The team members table shows adoption per developer or per team. Switch between Members and Teams, and filter by name.
Members who merged PRs in the period but have no attribution data show No CLI installed in the
Top model column, with a link to set it up. Select a column header to sort, except Top coding
agent and Top model. The table starts sorted by % AI code.
CSV export
Select the download button to export the current view as CSV. The export includes every row that matches your name filter, across all pages, in your sort order. It leaves out rows marked No CLI installed.AI coding agents and models
The AI coding agents section charts lines of code written per agent. Two tables list each coding agent and each model:
Use them to see which agents and models your team uses most, and whether their code is accepted
as-is or edited before merge.
Quality and review burden
Quality and review burden by AI contribution compares merged PRs by how much of their code AI wrote. A PR is mostly AI-authored when AI-attributed lines are more than 50% of attributed lines. Otherwise it’s mostly human-authored, and so are PRs with no attribution data. With low attribution, the human-authored group includes AI code that wasn’t tracked. Four cards show two measures for each group: issues cubic flagged per 1,000 lines added, and average review rounds before merge. These are comparisons and don’t show cause. AI-heavy PRs can differ from others in size and type. The section doesn’t appear when the period has no data.Issues flagged by coding agent and model
Issues flagged by coding agent and model shows, per agent and per model:
By default the tables show only agents and models with at least 5,000 lines authored, plus rows
without line counts. Turn on Show all to include the rest.
Some agents are detected only from commit metadata, such as a
Co-authored-by line, not from
git-ai. Their rows have no line data, so Lines authored, Issues / 1k lines, and AI edited
by human don’t describe them. Install the CLI for every member to get line-level attribution.
AI attribution tracking
% of commits with AI attribution is the share of merged-PR commits that carry AI attribution metadata, the same number as the chart’s commits tracked subtitle. The card shows the commit counts and the change from the previous period. Low attribution usually has one of four causes:- Some members haven’t installed the cubic CLI.
- Their coding agent, or its version, doesn’t record AI authorship.
- Code was pasted in from a chat app.
- A squash merge on GitHub created new commits without the authorship data.
Setup with the cubic CLI
The cubic CLI installs git-ai during setup. git-ai adds AI authorship notes to commits, so cubic records AI code even when your coding tool doesn’t. Opt out at install time withCUBIC_DISABLE_GIT_AI=true, or turn tracking off and on later with
cubic stats disable and cubic stats enable. See
Advanced settings in the CLI docs.