Structural review
Supported files can show higher-level code movement and changed units, reducing noise during refactors.
Structural diff Git
Semantic diffs when structure matters.
Normal Git diff is correct, but it can be noisy when code is moved, reformatted or refactored. FluxGit adds semantic diff surfaces for supported files so developers and agents can reason about structural change while still falling back to plain patches when analysis is unavailable.
The problem: line diffs are sometimes the wrong lens.
A safe review needs to know whether a change rewrote behavior, moved a symbol or only reshaped text. Plain patches remain the source of truth, but semantic analysis can make large refactors easier to inspect.
Honest beta limit
FluxGit does not claim full semantic diff for every language or file. Semantic views are beta surfaces and must label fallback clearly. When semantic parsing is unavailable, normal Git diff is the correct behavior.
How FluxGit helps.
Patch fallback
The UI should always make it clear when it is showing a regular textual diff rather than semantic analysis.
Safer agent context
MCP tools can expose read-only diff context while keeping write operations controlled by the desktop app.
Privacy and security posture.
Diffs can contain sensitive code. FluxGit treats semantic diff as local app context unless a user deliberately sends content to a configured AI/provider flow or shares diagnostics with consent.
Related features.
- Trinity conflict resolution uses clear review surfaces for merge conflicts.
- MCP agent Git requires agents to label semantic fallback honestly.
- Reflog recovery helps inspect recovered commits before keeping them.