FinderGit

Product Introduction

1. Definition: FinderGit is a native macOS file browser application built with SwiftUI that integrates Git version control intelligence directly into the file system navigation interface. It is a Git-aware file manager and repository dashboard tool.
2. Core Value Proposition: FinderGit exists to eliminate context switching for developers by providing a unified, real-time overview of all Git repositories' status, branches, and changes within a single, native macOS window. Its primary value is consolidating the workflows of file browsing, Git status checking, and basic repository management.

Main Features

1. Unified Repository Dashboard: The core interface displays all Git repositories within configured root folders in a sortable table view. It shows live Git status for each repo, including branch name, clean/dirty state, ahead/behind counts, changed file count, and repository size. It works by recursively scanning directories for .git folders, using native macOS File System Events for real-time updates (~300ms latency).
2. Inline Git Diff Viewer & Quick Actions: Clicking a modified file opens a side panel displaying a syntax-highlighted, line-numbered diff. From here, users can stage/unstage changes, discard modifications, or commit. The panel also integrates with Kaleidoscope (if installed) for advanced diff visualization, sending the committed version vs. working copy automatically.
3. AI-Powered Commit Message Generation: A built-in feature uses an AI model to generate Conventional Commit-formatted messages from staged diffs. It offers customization for tone (concise, neutral, detailed), length, and emoji prefixes. User data is processed ephemerally; the feature can also use a user's own OpenAI or Anthropic API key for privacy control.
4. Repository Trust & Security Scanner: This feature statically analyzes a repository's auto-execution surface (Git hooks, package manager scripts, IDE configurations) to identify potential supply-chain attack vectors, such as obfuscated droppers like Shai-Hulud/Miasma. It alerts users to changes in these hooks after a git pull without executing any code.
5. Integrated Repository Maintenance & Cleaning: Provides tools to analyze and reclaim disk space. The Maintenance tab visualizes Git object storage (packs, loose objects), while the Cleaning feature identifies and allows bulk deletion of rebuildable artifacts like node_modules, build folders, and tool caches across all repositories.

Problems Solved

1. Pain Point: Developers and engineering managers waste significant time and cognitive load juggling between Finder (for file navigation), terminal (for Git commands), and dedicated Git GUIs (for complex operations) to understand the state of multiple projects.
2. Target Audience: The primary user personas are macOS-based software developers, engineering leads, and open-source maintainers who work with multiple Git repositories simultaneously. It is especially valuable for full-stack developers, DevOps engineers, and tech leads who need a high-level overview of team or project status.
3. Use Cases: Essential for daily stand-up preparation to quickly see which repos have uncommitted work or unpushed commits. Critical for context switching between projects to immediately grasp local state. Vital for auditing clone safety and cleaning up disk space across a development workspace.

Unique Advantages

1. Strengths & Limitations (Pros & Cons):

   • Pros: Exceptional performance and native macOS integration due to 100% SwiftUI (no Electron). Provides a unique "at-a-glance" multi-repo dashboard not found in most Git clients. The Repo Trust feature offers proactive security scanning. The built-in AI commit message generator is a free, convenient productivity booster.
   • Cons: Requires macOS 15 (Sequoia) or later, excluding users on older OS versions. Lacks advanced Git operations like interactive rebase and complex cherry-picking, necessitating a fallback to terminal or full GUI. It is not available on the Mac App Store, requiring direct download and manual update trust.

2. Key Alternatives & Differentiation:

   • vs. Fork / GitKraken / Tower: These are full-featured, dedicated Git GUI clients designed for deep, single-repository operations (e.g., interactive rebase, sophisticated merge conflict resolution). FinderGit differentiates by focusing on the multi-repository overview problem, acting as a dashboard and lightweight action hub, not a replacement for deep surgical work.
   • vs. Terminal + git status: The terminal is infinitely flexible but provides no visual, consolidated overview. FinderGit offers a structured, always-live visual summary of all repos, reducing command-line memorization and manual directory traversal.
   • vs. macOS Finder: Finder shows no Git metadata. FinderGit overlays the crucial Git context (branch, status, changes) directly onto the familiar file browser paradigm, bridging the gap between the file system and version control.

Frequently Asked Questions (FAQ)

1. Is FinderGit a replacement for my current Git client? FinderGit is not a complete replacement for advanced Git GUIs or the terminal. It excels at multi-repository monitoring, quick commits, pushes, pulls, and basic branching. For complex operations like interactive rebase, you will still need a full Git client. It is best used as a complementary dashboard and quick-action panel.
2. How does FinderGit's AI commit message feature handle my code privacy? When using the default (free) built-in AI, your staged diff is sent transiently through findergit.app's servers to generate the message; it is not logged or stored. For maximum privacy, you can configure the feature to use your own OpenAI or Anthropic API key, sending the diff directly to their service under your account's data processing terms.
3. Does FinderGit work with Git hosting services other than GitHub? Yes. FinderGit provides basic issue and pull request counts for public repositories on GitLab, Codeberg, and Bitbucket without requiring an account. Full integration (e.g., GitHub-style account dashboards, star alerts) is currently deepest with GitHub, requiring a personal access token or GitHub CLI authentication.
4. What are the system requirements for FinderGit? FinderGit requires macOS 15 (Sequoia) or later. It is a Universal Binary, meaning it runs natively on both Apple Silicon (M-series) and Intel-based Macs. The application is signed with an Apple Developer ID and notarized for security.
5. How does the automatic update mechanism work? FinderGit checks for updates automatically from its own release feed. When an update is found, it can be downloaded and installed in-place with user permission. This is a self-contained update system separate from the Mac App Store, ensuring rapid iteration (74 releases as of this analysis).