> For the complete documentation index, see [llms.txt](https://docs.aviator.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aviator.co/runbooks/concepts/working-with-large-codebases.md).

# Working with large codebases

Handling enterprise-scale repositories requires specific strategies and optimizations.

## Code Analysis Strategy

### **Intelligent Searching**

* Agents download code to remote servers
* Use reference-based searching for efficiency
* Progressive analysis from entry points

### **Token Optimization**

* Focus on relevant code sections
* Incremental context building
* Caching of analysis results

## Performance Considerations

```
Repository Size    Recommended Approach
──────────────    ───────────────────
< 100K LOC        Standard analysis
100K-1M LOC       Targeted search patterns
> 1M LOC          Modular execution strategy
```

## Large Codebase Best Practices

1. **Divide and Conquer**
   * Break transformations into smaller Runbooks
   * Focus on specific modules or packages
   * Use incremental rollout strategy
2. **Context Management**
   * Carefully curate relevant documentation
   * Use MCP for external context
   * Limit scope to necessary files
3. **Resource Planning**
   * Monitor token usage trends
   * Scale agent containers as needed
   * Use caching effectively


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.aviator.co/runbooks/concepts/working-with-large-codebases.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.