Local Git FAQs

Question 1

What Git operations can Local Git facilitate?

Accepted Answer

Local Git supports a comprehensive set of common Git commands including status, commit (with automatic lock file cleanup), log, diff, add, push, pull, branch, and checkout, enabling full version control workflows for AI assistants.

Question 2

What problem does Local Git solve for AI coding assistants?

Accepted Answer

Local Git specifically addresses the issue of Git lock files (e.g., HEAD.lock, index.lock) failing to clean up in sandboxed environments due to permission restrictions. This service runs outside the sandbox, allowing AI assistants to perform Git operations reliably.

Question 3

Does Local Git manage or store my Git credentials?

Accepted Answer

No, Local Git does not store or manage your Git credentials. It runs as your user account and leverages your existing host OS's Git configuration, including SSH keys, credential helpers (like macOS Keychain), and environment variables, inheriting your full permissions.

Question 4

How is Local Git installed and run?

Accepted Answer

Local Git is installed as a persistent per-user service (macOS LaunchAgent or Linux systemd user unit) via a simple installer script. It runs as a local HTTP service (defaulting to 127.0.0.1) outside any sandbox, providing a secure API endpoint for AI assistants.

Question 5

How does Local Git ensure secure access and operations?

Accepted Answer

It implements two main security layers: client authentication via a bearer token stored in an owner-read-only file (mode 0600), and per-repository access control requiring a mandatory '.git-mcp-allowed' sentinel file in the repo root before any operations can be performed.

Local Git

Local Git

Key Features

Use Cases

Key Features

Use Cases