Attention stack
Repos are sorted by signals that matter: WIP, divergence, behind/ahead state, conflicts and recovery context.
Multi-repo Git dashboard
Know which repo needs attention.
Fleet Radar is FluxGit's local attention stack for developers juggling many repositories. It highlights dirty worktrees, branches ahead or behind, divergence, stale snapshots, recovery signals and possible conflict risk without pretending to be enterprise telemetry.
The problem: multi-repo work hides risk.
Developers often have several repos, worktrees or related projects open across a feature. Without a dashboard, drift and dirty work surface too late: during push, release, merge or context switch.
Honest beta limit
Fleet Radar is beta hardening. It focuses on selected, opened or recent local repositories and explicit refresh. It is not real-time company-wide monitoring, telemetry, auto-discovery of every repo or an agent-operated repair system.
How FluxGit helps.
Throttled refresh
Fleet state is designed around controlled local checks and explicit refresh rather than aggressive background fetch behavior.
Jump to safety
When a repo needs action, FluxGit points back to the relevant safety or recovery surface instead of hiding it in a list.
Privacy and security posture.
Fleet Radar is local-first repository awareness. It should not send repo names, paths, remotes, branch names, commit IDs or file names to licensing or feedback by default. MCP access is read-only and should avoid aggressive fetch from agents.
Related features.
- Safety rails handle risky operations after Fleet Radar identifies attention.
- Reflog recovery gives rescue paths when a repo shows recovery signals.
- MCP agent Git lets agents inspect fleet state read-only.