Multi-Repo Context

Enterprise

Multi-Repo Context allows Jolt to reference multiple repositories at once. Unlike AI coding tools that are limited to a single repository, Jolt can understand and coordinate context across multiple private or public repos. This feature is only available on the Enterprise Plan.

How it works

Jolt's Multi-Repo Context support is built on top of HyperContext, which enables Jolt to understand and process code across multiple repositories simultaneously. You don't need to manually select context files, even when using multiple repos.

Multi-Repo Context is supported in the IDE extensions and web app

Working Repos and Context Repos

The Working Repo is the primary repository where you're actively making changes and modifications. When using Jolt IDE extensions, local changes are taken into account for the working repo.

Context Repos are additional repositories that provide supplementary context. You can pick up to two, and they are always treated as read-only. They can be repos connected to your team or public git repositories.

To use Multi-Repo Context, you need to select a repo from the Add Repos for Context dropdown under the main working repo.

You can also paste in a url for a public git repository to add it as a context repo by selecting Select a public repo.

Jolt will select the default branch of the repo. Y also select a specific branch or search for one per context repo.

Example use cases

Separate frontend and backend repos

Many teams maintain separate repositories for frontend and backend code. With Multi-Repo Context, you can:

• Develop frontend features while referencing the backend APIs they consume
• Ensure requests and responses match between the client and server
• Implement full-stack features with a complete understanding of both sides
• Trace data flow from database schemas to UI components
• Verify that API changes on the backend are properly handled by the frontend

This eliminates the constant context switching between repos and helps prevent integration issues before they occur.

Referencing OSS or public repos

When building on top of or integrating open source libraries, Multi-Repo Context allows you to:

• Reference the source code of dependencies to understand their internal workings
• Build extensions or plugins with deep knowledge of the parent project's architecture
• Debug issues that may originate in third-party code
• Implement features that require understanding both your code and the library's code
• Make informed decisions about how to properly use complex open source tools

Microservices split across repos

A microservices application may be split across multiple repositories, each containing a different service. Multi-Repo Context enables you to:

• Make changes to one service while understanding its interactions with dependent services
• Implement cross-service features that require coordinated changes
• Debug issues that span multiple services by giving Jolt visibility into the entire request flow
• Ensure API contracts are maintained when modifying service interfaces
• Understand how data flows through your distributed system

Jolt referencing multiple repositories to help build a new feature