Blamely brings AI vs human code attribution into your IDE. As assistants like Copilot, Cursor, and JetBrains AI become part of daily work, teams need a straight answer to a simple question:
How much of this repo — and this commit — came from a person, and how much from an assistant?
This page is your starting point. From here you can install the plugin, follow the quick start, and read how it works in depth.
What Blamely does
- Line-level attribution — Each changed line can be labeled AI or Human, with character and line counts and percentages for the current file and for your uncommitted changes.
- History you can scan — In the tool window, History ties those stats to commits, branches, authors, time spent coding, AI wait time, and which models showed up in the work (where detectable).
- IDE-native — Everything lives in a normal tool window / sidebar and status bar. You are not asked to paste code into a website or wire up a separate dashboard just to see attribution.
Blamely analyzes git history and editor activity from your machine. Core tracking is designed to run locally; you use this website for documentation, account, and licensing where your organization needs it.
Why it exists
Git blame tells you who committed a line. It does not tell you whether that line was typed by a developer or inserted by an AI in the editor. Blamely closes that gap so you can:
- Review AI-heavy changes before merge or release.
- Discuss fairness, velocity, and risk with real numbers instead of guesses.
- Audit over time how assistants show up in your codebase.
Blamely does not judge — it surfaces measurable attribution so you decide what policy, review, or culture should follow.
Supported environments
Blamely ships for VS Code, Cursor, JetBrains IDEs (e.g. IntelliJ IDEA), and Antigravity. Detection covers common assistants (including Copilot, Cursor, Codeium, Tabnine, JetBrains AI, and others — see How it works for the full list and mechanics).
What to do next
- Install — Open Install the plugin and pick your editor (VS Code, Cursor, JetBrains, or Antigravity).
- Open a git repo — Blamely reads history from your project; no extra config is required to get started.
- Open the Blamely panel — Use Changes for live AI vs human breakdown; use History for commits and trends. See Quick start for a minimal walkthrough.
Because git blame only tells half the story.