VS Code
Install the Blamely extension to surface attribution inside VS Code and detect Tab-style inline completions that the CLI alone can’t observe.
You need the CLI installed first
The extension reads from data the CLI produces and posts inline-completion events to the local daemon. See Install the CLI.
Install
- Open VS Code.
- Open Extensions (
Cmd+Shift+Xon macOS,Ctrl+Shift+Xon Windows/Linux). - Search for Blamely.
- Click Install on the official extension by blamely.
- Reload when prompted.
Direct link: Blamely on Open VSX.
Verify
- Open a folder that is a git repository.
- The Blamely view appears in the Source Control sidebar (look for Blamely: Changes and Blamely: History).
- Make a small edit, then commit. The Source Control panel populates with AI vs Human stats; History shows the new commit with its attribution share.
What the extension adds
- Sidebar — Blamely: Changes. Live AI vs Human breakdown for the uncommitted working tree.
- Sidebar — Blamely: History. Per-commit attribution share, tools, models, and coding time across the repo.
- Gutter decorations. Optional line icons (AI / Human) next to line numbers for the current file. Toggle in settings.
- Inline completion detection. Catches Tab/inline accepts (Copilot Tab, etc.) by observing document-change events and posting them to the local daemon as
gen_type=completionevents. The CLI alone can’t see these because they don’t fire a hook.
Settings
Open Settings and search Blamely:
| Setting | Default | Effect |
|---|---|---|
blamely.showGutterDecorations | true | Show AI/Human icons in the gutter |
blamely.detectInlineCompletion | true | Observe document changes and report inline-completion accepts to the daemon |
How it talks to the CLI
The extension reads the daemon’s port from ~/.blamely/daemon.port and POSTs detected completion events to http://127.0.0.1:<port>/edit. It does not open a network listener of its own. If the daemon is offline, the extension logs a single warning and keeps polling silently — installing or restarting the daemon resumes attribution.
Update
Extensions view → Blamely → Update if a newer version is available. Or Check for Updates from the Extensions menu (...).
Uninstall
Extensions view → Blamely → Uninstall → reload.
If you want to stop attribution entirely, also run blamely uninstall on the CLI — see CLI uninstall.
Using Codex in VS Code
Trust all hooks
When you use Codex inside VS Code, Codex prompts you to approve the hooks it runs. Blamely attributes Codex’s edits through a Codex hook, so you must accept / trust all hooks when asked (pick the “Trust” / “Allow all” option, not a one-time allow). If you decline — or only allow a single run — the Blamely hook never fires, and Codex’s changes get recorded as Human instead of AI.
If you already dismissed that prompt, re-enable hooks in Codex’s trust settings (or re-run blamely install to re-register the hook), then accept all hooks the next time Codex runs. Confirm the hook is wired up with blamely doctor.
Next
- Quick start — verify your first attribution bar.
- How it works — the detection model.
Something unclear or wrong? Tell us.