Equip your factory's agents to use open source right

Reusing a library takes more than installing it

Every app brings different requirements. Open-source libraries can supply capabilities it needs, but your agents still have to choose libraries that fit the app, integrate their APIs correctly, and account for their dependencies and version changes.

That knowledge is spread across source code, documentation, and package registries. Model training alone can't give agents a dependable picture of an unfamiliar library, a new release, or an older application's dependencies.

Build on open source with confidence

GitHits gives your agents the code, documentation, and package details to select, integrate, and update open-source components in the apps they build.

• Work beyond the model's familiar libraries. Agents can investigate unfamiliar projects and new releases to find capabilities an app needs.
• Check dependencies throughout development. Agents use the same interface to evaluate packages, implement and review integrations, debug failures, and prepare updates.
• Know why a component fits the app. Agents can check its API, license, dependency requirements, and known vulnerabilities before building on it.

Use it when building a new app, adding a feature, or updating an existing system—even when the library or release is missing from the model's training.

The developer workflow, carried out by agents

Developers have long relied on documentation, source code, and working examples to choose and use libraries. Your factory delegates that work to agents. To trust their decisions, you need to know they're checking accurate information for the versions the app actually uses.

For example, when an app needs PDF extraction, your agent can use GitHits to find how other projects parse PDFs, then evaluate a candidate parser's license and dependencies. It reads the chosen version's API and checks usage examples before wiring the parser into the app's upload flow.

If parsing fails, it can trace the error into the library. When the app needs a newer parser, it can inspect release changes before updating the integration. Your factory's agents use GitHits throughout the work to check how the library fits and behaves in the app they're building.

Build GitHits into your factory

Connect through MCP or the CLI, or embed the REST API in your planning, coding, review, and update steps. Control when agents retrieve information and how it enters their context, within your own product experience.

If your product runs or configures customers' agents, make GitHits available through MCP in their setup.