We just pushed a big update: GitHits now does a lot more than code examples.

GitHits used to provide grounded examples of how something has been done before. Now it can also be used for more fine-grained discovery across code and documentation.

To install:

npx githits@latest init

That one command detects your tools, walks you through login if you need an account, and configures the MCP server to work with your agent harnesses. No waitlist. Anyone can sign up now, either from the CLI or from githits.com.

From 3 tools to 14

Your agent now gets 14 tools instead of 3. All new tools ship through the GitHits CLI.

The previous code example toolset included:

`get_example`

Natural-language query that returns a code example sourced from global open source. It supports 800+ languages.

New in this release: the query can be made without providing a language. GitHits selects a language based on the input and the sources.

`search_language`

Discover supported languages for get_example and their canonical names.

`feedback`

Submit thumbs up or down for an example or for a session. It also supports optional text feedback and tool name parameters.

Code Navigation consists of search and inspection tools.

Code and Documentation Search for Open Source

Seven new tools help agents search, grep, list, and read code and docs in any open-source package.

search: Search across code, docs, and symbols in any package or GitHub repo. Supports discovery syntax with AND/OR, qualifiers such as kind:, category:, path:, and lang:, and scoped targets such as npm:react or https://github.com/org/repo.
code_grep: Deterministic text grep over indexed source files. Literal or regex, scoped by path, globs, or extensions. Matches chain directly into code_read.
code_files: List files in any indexed dependency or repo. Filter by path prefix, globs, extensions, language, or file intent.
code_read: Read source files directly. Your agent can jump to exact line ranges from search or grep results. No cloning required.
docs_list: List available documentation pages for a package, including hosted and repo-backed docs.
docs_read: Read a single doc page by pageId.
search_status: Poll asynchronous indexing or search progress when an index is still being built.

GitHits indexes open-source packages quickly, around 10 seconds for average repos and 2-5 minutes for very large repos such as the Linux kernel, and makes code accessible to agents with sub-second queries.

Supported languages include Bash, C#, C++, CSS, Dart, Elixir, Erlang, Go, Java, JavaScript, Kotlin, Lua, Markdown, PHP, Proto, Python, R, Ruby, Rust, Scala, SCSS, Swift, TypeScript, and Zig. If you have a suggestion for what we should add next, let us know.

Package Inspection

Four new tools inspect package metadata, dependencies, vulnerabilities, and changes.

pkg_info: Package overview, including version, license, downloads, stars, and recent changes.
pkg_deps: Dependency graph analysis with transitive resolution and conflict detection.
pkg_vulns: Known vulnerability checks with severity filtering.
pkg_changelog: Release notes, newest-first, with range queries.

Package Inspection supports 11 registries: npm, PyPI, Hex, Crates, vcpkg, Zig, NuGet, Maven, Packagist, RubyGems, and Go. If you have a suggestion for what we should add next, let us know.

Why it matters

Before this update, GitHits answered one question for your agent: “How has this been done before?” The agent got real implementations distilled from open-source code.

That worked for common patterns. It left a gap when the answer required understanding how a package actually works internally: which functions exist, which calls what, and how a specific version handles an edge case.

For that, your agent fell back on web searches and GitHub reads, usually pulling code from main instead of the version you had installed. That is how you get invented APIs, confidently wrong fixes, and retry loops.

This update closes that gap. Your agent can now navigate any indexed package’s source on demand: read source files at exact line ranges, grep across a dependency, inspect transitive deps, check vulnerabilities, and follow changelogs. Correctly versioned against what you have installed. No cloning required.

Together with the existing example pipeline, your agent now has both halves of the picture: how something has been done before, and how the code you are working with actually works.

Feedback is welcome. Open an issue on GitHub or drop a message in the GitHits Community Group.

Try it out

Ask your agent to use GitHits to explore https://github.com/postgres/postgres and explain how the query planner selects join strategies. It will search the codebase, read the relevant source files, and walk you through the answer without cloning anything.

What’s coming next

Some of the features we are building:

symbol_callees: Provide a call graph for a symbol, allowing agents to quickly understand flow through functions across packages.
version_diff: Let agents see what really changed between versions, not just what is written in changelogs.

Which of these would bring the most value for you? Or something else? Tell us.

We are also working on a baseline skill template. Several of you have asked for a starter skill that teaches agents how to use GitHits tools without writing your own prompt instructions.

GitHits CLI Launch: 14 Tools for Agentic Code Search & Package Navigation