Review · For: agent

Static dependency graphs miss files that always change together, so agents edit one side of a coupled pair and break the other.

Change Coupling parses git history into bounded co-change pairs and surfaces coupled neighbors before an agent edits.

$ aindex context "touch the auth callback" --json

co_changes
pair_count
focus_files
history_window

Command

Change Coupling

Surface files that historically change together as a git co-change blast-radius signal.

CLI

aindex context "touch the auth callback" --json

MCP

context action=autopilot

Example output

What the Brain does automatically

The agent sees the files that git history says change together before it edits one side of a coupled pair.

intent

When a task is classified as a refactor.

intent

When you ask an agent to build a feature.

Not measuredProof

Not measuredNo public benchmark covers this workflow yet — the proof is the live command output above, not a positioning claim.

Source—

AvailableRuntime feature status · 0 evidence item(s). Metadata-only; no raw source included.

Required tier

Surfaces files that historically change together so agents stop editing one side of a coupled pair.

Advanced · €9.99/mo

Visible as a product workflow and pilot proof target; do not treat as fully shipped enterprise automation yet.

Buyer grade

Names the parity workflow and proof path without claiming full Sourcegraph-class depth.

Visible in

This workflow stays discoverable across setup, CLI, MCP status, docs, dashboard and pricing — never a hidden command.

Feature visibility checklist

This keeps grouped product names discoverable without claiming a separate maturity level from the underlying workflow.

Change CouplingFoundation

Git co-change pairs surface coupled neighbors a static dependency graph misses.

Review

Hidden blast radius