Leanmote

AI Lines of Code measures coding volume associated with AI tool usage. The dashboard surfaces it from two complementary sources — vendor-reported Copilot telemetry, and PR-level diff sizes from Git — so you can compare AI-tagged and non-AI work at the same scale.

Copilot LOC — sum of <code>loc_added_sum</code> reported by Copilot's telemetry, aggregated for the period.

PR-level Lines of Code — total <code>lines_added + lines_deleted</code> from merged PRs in the period, used to build the AI-tagged vs non-AI comparison.

Avg Lines per PR (AI-tagged) — total AI-tagged PR lines divided by the count of AI-tagged PRs.

Avg Lines per PR (non-AI) — same calculation for the non-AI cohort.

- Copilot LOC — sum of <code>loc_added_sum</code> reported by Copilot's telemetry, aggregated for the period.
- PR-level Lines of Code — total <code>lines_added + lines_deleted</code> from merged PRs in the period, used to build the AI-tagged vs non-AI comparison.
- Avg Lines per PR (AI-tagged) — total AI-tagged PR lines divided by the count of AI-tagged PRs.
- Avg Lines per PR (non-AI) — same calculation for the non-AI cohort.

copilot_loc      = sum(loc_added_sum)  -- vendor-reported Copilot telemetry
pr_size(pr)      = lines_added(pr) + lines_deleted(pr)
avg_lines_ai     = sum(pr_size) over AI-tagged PRs / count(AI-tagged PRs)
avg_lines_non_ai = sum(pr_size) over non-AI PRs / count(non-AI PRs)

Copilot LOC is pre-aggregated by GitHub before Leanmote receives it; line counts already account for whatever exclusions the vendor applies in the telemetry pipeline.

PR-level Lines of Code is unfiltered today. Renames, generated files, lockfiles, vendored code, and migrations all count toward <code>pr_size</code>. There's no per-workspace exclusion configuration available right now.

The same formula and the same lack of exclusions apply equally to AI-tagged and non-AI cohorts, so the comparison between them is internally consistent — just be aware the absolute numbers can be inflated by mechanical churn.

- Copilot LOC is pre-aggregated by GitHub before Leanmote receives it; line counts already account for whatever exclusions the vendor applies in the telemetry pipeline.
- PR-level Lines of Code is unfiltered today. Renames, generated files, lockfiles, vendored code, and migrations all count toward <code>pr_size</code>. There's no per-workspace exclusion configuration available right now.
- The same formula and the same lack of exclusions apply equally to AI-tagged and non-AI cohorts, so the comparison between them is internally consistent — just be aware the absolute numbers can be inflated by mechanical churn.

AI PRs larger than non-AI PRs — AI is being used to draft larger changes. Watch review latency carefully; large PRs are slower to review.

AI PRs about the same size as non-AI — AI is augmenting normal sizing decisions, not replacing them.

AI PRs smaller than non-AI — usually indicates AI is being used for surgical fixes or short boilerplate.

Outlier PRs distort the average — a single huge dependency bump or generated-code commit can move the cohort average sharply. Use the trend across weeks rather than a single number.

- AI PRs larger than non-AI PRs — AI is being used to draft larger changes. Watch review latency carefully; large PRs are slower to review.
- AI PRs about the same size as non-AI — AI is augmenting normal sizing decisions, not replacing them.
- AI PRs smaller than non-AI — usually indicates AI is being used for surgical fixes or short boilerplate.
- Outlier PRs distort the average — a single huge dependency bump or generated-code commit can move the cohort average sharply. Use the trend across weeks rather than a single number.

If AI PRs are systematically larger, coach authors to slice AI-drafted changes into smaller PRs.

Pair with AI Lead Time Comparison — if AI PRs are bigger and slower in review, you've found a workflow to fix.

If your repos have a lot of generated code or dependency churn, treat the absolute numbers as directional only and focus on the AI-vs-non-AI delta.

- If AI PRs are systematically larger, coach authors to slice AI-drafted changes into smaller PRs.
- Pair with AI Lead Time Comparison — if AI PRs are bigger and slower in review, you've found a workflow to fix.
- If your repos have a lot of generated code or dependency churn, treat the absolute numbers as directional only and focus on the AI-vs-non-AI delta.

- AI Lead Time Comparison
- AI Intensity
- AI Governance metrics overview

Lines changed (additions + deletions) sourced from Copilot telemetry and PR-level diff data. No content-type exclusions today; AI and non-AI cohorts use the same formula.

AI Lines of Code

Sign In

Roadmap & Feedback

Find answers and get help from Intercom Support and Community Experts

Conversations you've started through the messenger will appear here.

No conversations created by you

Try using different keywords or checking for typos.

No conversations found

Title

This site employs cookies and other technologies that we and our third party vendors use to monitor and record personal information about you and your interactions with the site (including content viewed, cursor movements, screen recordings, and chat contents) for the purposes described in our Cookie Policy. By continuing to visit our site, you agree to our {websiteTermsLink}, {privacyPolicyLink} and {cookiePolicyLink}.

This site uses cookies and similar technologies ("cookies") as strictly necessary for site operation. We and our partners also would like to set additional cookies to enable site performance analytics, functionality, advertising and social media features. See our {cookiePolicyLink} for details. You can change your cookie preferences in our Cookie Settings.

We use cookies to make our site work and also for analytics and advertising purposes. You can enable or disable optional cookies as desired. See our {cookiePolicyLink} for more details.

Advertising cookies are set by our advertising partners to collect information about your use of the site, our communications, and other online services over time and with different browsers and devices. They use this information to show you ads online that they think will interest you and measure the ads' performance. Social media cookies are set by social media platforms to enable you to share content on those platforms, and are capable of tracking information about your activity across other online services for use as described in their privacy policies.

These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.

These cookies are necessary for the website to function and cannot be switched off in our systems.

These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site.

You have the right to opt out of the sale of your personal information. See our {cookiePolicyLink} for more details about how we use your data.

Your Privacy Choices

We use cookies to enhance your experience. You can customize your cookie preferences below. See our {cookiePolicyLink} for more details.

Cookie Settings

Empty Help Center

Uh oh. That page doesn’t exist.

Home

Search results

Disappointed

Neutral

Smiley

Thinking...

Searching through sources...

Analyzing...

Tickets submitted through the messenger or by a support agent in your conversation will appear here.

No tickets created by you

No tickets found

Track the progress of all tickets and conversations related to your company.

Customer Portal.

Track the progress of all tickets related to your company.

Tickets portal.

{assigneeName} needs more information from you

Tickets

No access to tickets portal

Search and ask

Find guides, answers, and references.

Skip the search. Describe what you’re trying to do and get a grounded answer.

Browse articles and guides in this topic.

Create your workspace and invite the people you work with.

Set up your account

Build your first workflow and watch it run end to end.

Ship something

Connect the tools your team already uses to bring data in.

Connect your stack

A quick lap of the product so you know where everything lives.

{appName} in 60 seconds

This prototype demo is aware that you are reading “{title}”. It can point you back to the current article, but a production article-aware Fin contract is still follow-up work.

Prototype article-aware answer

Because you already asked about invitations, this prototype demo can add the follow-up: use the role selector before sending each invite to limit access to the teammate responsibilities.

Prototype role-limiting follow-up

This prototype demo suggests starting with your workspace profile, inviting the team members who need access, and then connecting the integrations you use.

Prototype getting-started answer

In this prototype demo, integrations are configured from workspace settings. Choose the integration, connect the account, and review the enabled permissions.

Prototype integrations answer

In this prototype demo, invite teammates from workspace settings, then choose the access each teammate needs before sending the invitation.

Prototype invite-team answer

This prototype demo does not have a scripted answer for that question yet. Try asking how to invite your team or open a source article. No production Fin API was called.

Prototype answer unavailable

I’ve got this page open. Ask me anything about it and I’ll answer from the docs.

AI Lines of Code

What it measures

How Leanmote calculates it

What's included and excluded

How to interpret it

What to do about it

Related metrics