Cursor

Cursor is a VS Code fork and uses the same extension. The installation flow is identical to VS Code — what changes is what gets detected.

Install #

1. Open Cursor.
2. Open Extensions (sidebar icon or Cmd+Shift+X / Ctrl+Shift+X).
3. Search for Blamely.
4. Click Install.
5. Reload the window (Cmd+Shift+P → Developer: Reload Window).

Direct link: Blamely on Open VSX.

What Cursor users get specifically #

The extension is essential for Cursor users. Cursor’s Tab completion (its native inline AI) doesn’t fire any hook, doesn’t write a log file the daemon can tail, and doesn’t expose an extension API for “Tab accepted”. The only observable signal is the editor’s document-change event — and the extension is what observes it.

Tagged as: tool=cursor, gen_type=completion.

Verify #

1. Open a git project in Cursor.
2. Accept a Tab completion of 3+ lines (or 1+ line of 8+ characters).
3. Open the Source Control panel — Blamely: Changes should show the inserted lines attributed to cursor with completion as the generation type.
4. Commit. The bar shows the Cursor share alongside Composer / Chat activity.

Settings #

Same as VS Code:

Turn off detectInlineCompletion if you don’t want plugin-side Cursor Tab attribution — the CLI will still capture Composer / Chat.

Cursor-specific notes #

• Composer / Chat sessions are captured by the CLI’s log tail — no extension needed for those.
• Snippet expansion (typing for<Tab> triggering a built-in snippet) looks the same as a 1-line completion to the detector and will be attributed as such.
• The extension respects Cursor’s “workspace trust” model — allow the workspace if Cursor prompts.

Update / uninstall #

Same as VS Code: Extensions → Blamely → Update or Uninstall → reload.

Next #

• Quick start — first commit walkthrough.
• How it works — the detection model.
• VS Code guide — same extension, plain VS Code context.