codeloop_visual_attribution
Identify which commit, branch, and section introduced each visual diff. Pair with codeloop_design_compare or update_baseline to gate visual regressions.
When to use codeloop_visual_attribution
Use `codeloop_visual_attribution` when your AI agent needs to identify which commit, branch, and section introduced each visual diff. pair with codeloop_design_compare or update_baseline to gate visual regressions.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
| run_id | string | yes | Run id. |
| project_dir | string | no | Project root. |
What you get back
Diff-by-commit map; per-screen attribution metadata.
FAQ
What does codeloop_visual_attribution do?
Identify which commit, branch, and section introduced each visual diff. Pair with codeloop_design_compare or update_baseline to gate visual regressions.
When should an AI agent call codeloop_visual_attribution?
Use `codeloop_visual_attribution` when your AI agent needs to identify which commit, branch, and section introduced each visual diff. pair with codeloop_design_compare or update_baseline to gate visual regressions.
What does codeloop_visual_attribution return?
Diff-by-commit map; per-screen attribution metadata.
Is codeloop_visual_attribution part of the CodeLoop MCP server?
Yes. CodeLoop ships as an MCP server installed via `npx codeloop init`. Cursor and Claude Code call it automatically once the User Rule (Cursor) or CLAUDE.md (Claude Code) is in place.