Read-only tools
Expose repository status, fleet signals, diff context and recovery surfaces without granting mutation endpoints.
AI agents inspect Git safely
MCP context without handing over the controls.
FluxGit's MCP layer is designed for AI agents that need repository context: status, fleet radar, diffs, reflog hints, restore points and safety timeline details. Agents inspect read-only; Git writes stay controlled by the desktop app and the human user.
The problem: agents need context, but Git writes are high-risk.
AI coding agents can help explain diffs, summarize branch state and plan next steps. They should not get silent end-to-end control over reset, rebase, patch application or branch mutation just because they can read a repo.
Honest beta limit
FluxGit does not claim that agents operate Git safely end-to-end. The MCP sidecar has validated read-only behavior, while installed app visibility and real client smoke testing remain part of beta hardening.
How FluxGit helps.
Write boundary
Risky Git actions stay in the FluxGit desktop cockpit where previews, safety rails and human confirmation can apply.
Audit trail
Beta workflows can review what context agents requested, helping teams debug and set trust boundaries.
Privacy and security posture.
MCP can expose sensitive repository facts to a connected agent, so the boundary must be explicit. FluxGit keeps writes blocked from MCP, labels semantic diff fallback, avoids aggressive fleet fetch from agents and treats AI/provider data sharing as a separate user-controlled decision.
Related features.
- Fleet Radar gives agents a read-only attention stack across selected local repos.
- Semantic diff gives structural context when supported and fallback labels when not.
- Safety rails keep write decisions in the guarded desktop workflow.