Quick start

Get from zero to first attribution in a few minutes. If you have not installed Blamely yet, start with Install the plugin and pick your editor.

Before you begin

  • A git repository opened in the IDE (Blamely reads .git and stores state under .git/blamely).
  • Blamely plugin installed for VS Code, Cursor, JetBrains, or Antigravity.
  • No API keys or Blamely account are required for local tracking in the IDE.

1. Open your project

Open a folder that is already a git repo (or initialize git if you are experimenting). Blamely activates per project, not globally across unrelated folders.

2. Open the Blamely tool window / panel

  • JetBrains — View → Tool Windows → Blamely (or find Blamely in the tool-window strip). If you do not see it, use Help → Find Action and search for Blamely.
  • VS Code / Cursor — Open the Blamely view from the Activity Bar (sidebar icon) or the Command Palette (Blamely: Focus / similar, depending on version).
  • Antigravity — Use the extension’s entry point in the UI (sidebar or command palette) once installed.

You should see tabs such as Changes and History (names may match your IDE skin).

3. Make a small edit and watch Changes

  1. Open any source file.
  2. Type a few lines by hand, then trigger your AI assistant (e.g. accept a completion or apply a chat edit) on another line.
  3. Open Changes (or the equivalent uncommitted changes view). You should see AI vs Human counts and often a per-file breakdown.

The status bar (where the IDE shows file/encoding info) usually shows live AI / Human character and line stats for the current file — click it to jump to the Blamely window if your build supports that.

4. Commit and explore History

Create a commit as you normally would. Open History to see that commit in context: AI share, human share, models (when detectable), coding time, AI wait time, and links into per-commit detail.

For how detection and persistence work under the hood, see How it works.

5. Optional: gutter and settings

On JetBrains, you can enable line icons in the gutter for uncommitted changes (Settings → Tools → Blamely). VS Code / Cursor may expose similar options in Settings under the Blamely extension.

Troubleshooting (quick)

  • Nothing shows up — Confirm the directory is a git root and the plugin is enabled for this workspace.
  • All lines Human — Some assistants need a moment after an AI edit; try another completion or check How it works for what each IDE can detect.
  • Wrong project — Blamely is per repo; open the correct root folder.

That is enough to use Blamely day to day. For reports, git notes, and hooks, read the How it works page.