Check prerequisites
GitHits requires Node.js 20 or later. To check your version, run:If you need to install or upgrade Node.js, visit nodejs.org.
Run the hybrid CLI
From your terminal, run:This command:
- Detects supported AI coding tools installed on your machine
- Configures each detected tool with the GitHits MCP server
- Handles authentication automatically for common local setup
init supports automatic install for Claude Code, Cursor, Windsurf, VS Code / Copilot, Cline, Claude Desktop, Codex CLI, Pi, Gemini CLI, Google Antigravity, and OpenCode.If you use any MCP-capable client that supports remote servers, connect it to GitHits manually. See Manual remote MCP setup.
Use your agent
Open your AI coding tool and start a coding task as normal. Many agents call GitHits tools on their own when they need indexed source, docs, package metadata, or implementation examples.Some harnesses are more conservative. If the agent starts guessing or does not call GitHits, ask for it directly:For example, if you ask your agent to debug Express middleware behavior, it may search the indexed package and read the relevant source:The agent receives indexed source context and uses it to explain the dependency behavior before changing your code.
What’s next
- Learn where GitHits fits in an agentic coding workflow
- Learn how to trigger GitHits manually
- Review Automatic local MCP setup for the local MCP install path
- Add GitHits to any MCP-capable client that supports remote servers with Manual remote MCP setup
- Use GitHits through CLI-backed Skills if you prefer Skills over MCP tools
- Explore code navigation tools for source reading
- Explore documentation access tools for hosted and repo-backed docs
- Explore package inspection tools for vulnerabilities, dependencies, and changelogs
- Browse the code examples tools for prior art and implementation-pattern research