Install
Install

JetBrains

Install the Blamely plugin for IntelliJ IDEA, WebStorm, PyCharm, GoLand, Rider, CLion, RubyMine, PhpStorm, and the rest of the JetBrains family.

You need the CLI installed first

The plugin reads from data the CLI produces. See Install the CLI.

Install from the IDE

  1. Open your JetBrains IDE.
  2. Open Settings (Windows/Linux) or Preferences (macOS):
    • macOS: <IDE name> → Settings… or Cmd+,
    • Windows/Linux: File → Settings or Ctrl+Alt+S
  3. Go to Plugins.
  4. Click Marketplace.
  5. Search for Blamely.
  6. Click Install, then Apply / OK.
  7. Restart the IDE when prompted.

Install from the website

Open the JetBrains Marketplace in a browser, search for Blamely, and use Install to IDE if you’re signed in with a JetBrains Account linked to Toolbox or a running IDE.

Verify

  1. Open a project that’s under git.
  2. View → Tool Windows → Blamely (or look for Blamely in the tool-window strip at the side/bottom of the IDE).
  3. Open the Changes tab and edit a file. The view should update.
  4. Commit. The History tab should populate with the new commit and its AI / Human share.

If you don’t see the tool window, use Help → Find Action (Shift+Shift) and search for Blamely.

What the plugin adds

  • Tool window — Changes. Per-file AI vs Human breakdown for uncommitted changes.
  • Tool window — History. Commit list with attribution, models, coding time, AI wait time.
  • Status bar widget. Live AI / Human chars and lines for the active file; click to open the tool window.
  • Gutter line icons. Optional AI/Human markers next to line numbers (Settings → Tools → Blamely).
  • Inline completion detection. Observes IntelliJ DocumentListener events and reports Tab-style accepts to the daemon as gen_type=completion events.

Settings

Settings → Tools → Blamely:

SettingDefaultEffect
Show line icons in gutterOnAI/Human gutter decorations
Detect inline completionOnObserve document changes and report inline-completion accepts to the daemon

Actions

Tools → Blamely menu:

ActionWhat it does
Show Blame for Current FileRefresh gutter attribution for the active editor

The other CLI-side actions (blamely report, blamely stats, blamely history) run from your terminal — see CLI commands.

How it talks to the CLI

The plugin reads the daemon’s port from ~/.blamely/daemon.port and POSTs to http://127.0.0.1:<port>/edit. The daemon must be running; if it isn’t, the plugin logs a single warning per 30 seconds and keeps polling. Starting the daemon resumes attribution.

Update

Settings → Plugins → Installed → Blamely → Update if a newer version is available.

Uninstall

Settings → Plugins → Installed → Blamely → Uninstall → restart.

To stop attribution entirely, also run blamely uninstall on the CLI — see CLI uninstall.

Next

Something unclear or wrong? Tell us.