Launching today
GitHits beta 0.9
Give your AI coding agent access to open-source code
57 followers
Give your AI coding agent access to open-source code
57 followers
GitHits gives coding agents access to the open-source code your app depends on. Get real implementation examples, dependency source navigation, package inspection and documentation. Agents can grep and read your codebase. They can't grep and read the open-source code your app depends on. That's where they start guessing, retrying, and looping. GitHits builds a version-aware index on demand. Agents can search, navigate, and inspect the code behind their dependencies. CLI: npx githits@latest init
Interactive
Free
Launch Team / Built With
GitHits beta 0.9
Hi Product Hunt! 👋
I’m Olli-Pekka, one of the co-founders of GitHits.
I've been a member of the open-source community for 15 years. I created opencv-python, which got 100M+ downloads while I maintained it as a side hustle. Fun fact: I’m from 🇫🇮, just like Linus Torvalds. 🙂
I noticed I kept giving the same advice to colleagues and friends when the docs were missing something. My go-to hack was simple: use GitHub search to find code that already solves the problem. It’s powerful, even though it only returns raw results rather than the answer in context.
I started building GitHits to bring that workflow to coding agents.
GitHits complements tools like Claude Code, Codex, Cursor, and other AI coding agents.
Those agents are great at navigating your local codebase. They can grep, search, and read files to understand how your application works.
The problem is that modern software doesn't stop at the repository boundary.
A large part of the system lives in frameworks, libraries, SDKs, and other open-source dependencies. Agents can usually see where your code calls into those dependencies, but they often can't navigate and inspect them in the same way. And even when an agent reads the docs, they only tell it what to call, not how it actually behaves. For that, you need the source.
GitHits gives agents access to:
Code examples based on real implementations from repositories, issues, discussions, and pull requests, linked back to the implementation code
Code navigation across packages and repositories: search, grep, file listing, and exact line reads without cloning
Package inspection for dependencies, vulnerabilities, changelogs, and upgrade changes
Documentation access across hosted docs and repository-backed docs
GitHits does this by building a version-aware index of open-source code on demand, usually in 10-20 seconds for an average repository.
GitHits is useful when an agent reaches the limits of the local repository.
That might happen during planning and research, when it needs to understand how a dependency works, what changed between versions, or how something has been implemented elsewhere. It also happens during implementation, when the agent starts retrying variations and exploring dead ends because the answer isn't in the local repository.
As developers, that's usually the point where we leave our own repository and start reading somebody else's.
What users say about GitHits:
Onni: Helping Claude Code to find undocumented APIs from the code
Rob: had a problem in my openusage v2 app - boom, perfect fix without guesses
Forever free tier available.
No trial period. Just create your account and connect your agent to GitHits.
Launch day special.
Everyone who signs up today gets 3x credits for 6 months. No strings, just more GitHits.
Setup is one command:
It installs the CLI and connects GitHits to Claude Code, Codex, Cursor, or any MCP-compatible agent. Or sign up using this link.
If you’re already using GitHits, let me know what you use it for, and how we can make GitHits even better.
We look forward to your brutally honest feedback and sincerely appreciate the support!
GitHits beta 0.9
Hi Product Hunt! 👋
I'm Juha, co-founder and chief architect of GitHits. I'm responsible for the indexing engine underneath, so I want to talk about the part you don't see.
The question I get more than any other is some version of this: my coding agent can already clone a repo, grep it, and search GitHub, so what is GitHits actually adding?
It's a fair question, and the honest answer is that scraping GitHub gives your agent raw results, not understanding. It clones whatever is at the top of the default branch and greps one repo at a time, treating code as text with no sense of what is worth trusting. And here's the part that surprises a lot of people: GitHub's own code search only covers a repository's default branch, so the older version you actually depend on usually isn't even searchable. That's fine for a quick lookup, but it falls apart the moment the problem gets specific.
What GitHits does instead is build a real, version-aware index. We fetch the actual source, parse it, turn it into structure, and keep that structure version by version, so your agent reads from something we already built rather than scraping and guessing in the moment.
People are usually surprised how much work that is. One small example: just figuring out which commit a version like 1.2.3 actually points to. There's no standard for how projects tag releases, so the part of our indexer whose only job is that is more than 700 lines, and we've rewritten it six times as we keep hitting new conventions in the wild. And that's before we've parsed a single line of the actual code.
And it isn't only code. We index documentation the same way, version by version, and combine it with the rest so your agent grounds itself in a balanced mix of code, tests, examples, and docs, instead of one slice it has to guess from.
I wrote up the full under-the-hood walkthrough here if you want the long version: https://githits.com/blog/what-it-actually-takes-to-index-open-source/
The best way to judge it is to just test it out. Setup is one command:
It connects GitHits to Claude Code, Codex, Cursor, or any MCP-compatible agent. Or sign up here: https://app.githits.com/signup
I built the indexing engine, so I'd genuinely love to hear where it works or breaks for you. Brutally honest feedback is the most useful kind.
This app is seriously helpful and turns your coding agent in a top tier senior engineer. When I am introducing a new pattern or library in my code, I always think to find real battle tested implementations first from GitHits. Eventually you realize just letting a coding agent vibe out consequential and high leverage code is just plain dumb and irresponsible.
GitHits beta 0.9
Thanks,@lukeotwell! Let us know how we could make GitHits even better!
Works great, I've been using Githits to explore implementation details from different libraries to ground my coding agent with real world examples. It's cool to point your coding agent towards an open source reference implementation that you know has already implemented what you want to implement.
Toolhouse
Congrats!
GitHits beta 0.9
Thanks@orliesaurus! Appreciate your support!