Commitmux FAQs

Question 1

Is Commitmux secure and private?

Accepted Answer

Yes, Commitmux is designed to be local-first. All operations occur on your machine, with no credentials or tokens required. The index lives in a single SQLite file, ensuring nothing leaves your machine and preserving privacy.

Question 2

What is Commitmux and what problem does it solve?

Accepted Answer

Commitmux provides local, credential-free access to your cross-repository Git history. It empowers AI coding agents with structured prior-work context, solving the problem of agents lacking relevant historical information without exposing sensitive data or hitting API rate limits.

Question 3

Can Commitmux search across multiple Git repositories?

Accepted Answer

Absolutely. Commitmux excels at cross-repository queries, allowing you to index and search commit history from multiple local or remote Git repositories in a single query, providing a unified view of your prior work.

Question 4

What kind of search capabilities does Commitmux offer?

Accepted Answer

It offers two main search modes: Full-text search (FTS5) for fast keyword matching over commit subjects, bodies, and patch previews, and Semantic search using vector embeddings for natural language queries like 'find commits related to rate limiting'.

Question 5

How does Commitmux provide context to AI agents?

Accepted Answer

Commitmux builds a read-optimized local index over your commit history and exposes it as a narrow, read-only set of MCP (Model Context Protocol) tools. Agents can then query this history using full-text or semantic search.

Commitmux

Commitmux

主要功能

使用案例

主要功能

使用案例