LogoLogo
Sign inVisit bito.aiVideo Library
  • 👋Welcome to Bito
  • 🆕Getting started
  • 🛡️Privacy and security
  • 🤖AI Code Review Agent
    • Overview
    • Key features
    • Supported programming languages and tools
    • Install/run using Bito Cloud
      • Guide for GitHub
      • Guide for GitHub (Self-Managed)
      • Guide for GitLab
      • Guide for GitLab (Self-Managed)
      • Guide for Bitbucket
      • Integrate the AI Code Review Agent into the CI/CD pipeline
      • Create or customize an Agent instance
      • Clone an Agent instance
      • Delete unused Agent instances
    • Install/run as a self-hosted service
      • Prerequisites
      • CLI vs webhooks service
      • Install/run via CLI
      • Install/run via webhooks service
      • Install/run via GitHub Actions
      • Agent Configuration: bito-cra.properties File
    • Available commands
    • Chat with AI Code Review Agent
    • Implementing custom code review rules
    • Excluding files, folders, or branches with filters
    • Code review analytics
    • Agent settings
    • FAQs
  • Other Bito AI tools
    • IDE extension
      • Quick Overview
      • Installation guide
        • Installing on Visual Studio Code
        • Installing on JetBrain IDEs
        • Vim/Neovim Plugin
      • Upgrading Bito plugin
      • AI Chat in Bito
        • Keyboard shortcuts
        • Chat session history
        • Share chat session
        • Appearance settings
        • Open Bito in a new tab or window
        • Use cases and examples
      • Templates
        • Standard templates
        • Custom prompt templates
        • Diff view
      • AI that Understands Your Code
        • Overview
        • How it Works?
        • Available Keywords
        • Example Questions
        • How does Bito Understand My Code?
        • Using in Visual Studio Code
        • Using in JetBrains IDEs
        • Managing Index Size
        • FAQs
      • AI Code Completions
        • Overview
        • How it works?
        • Enable/disable settings
        • Accept/reject suggestions
        • Keyboard shortcuts
        • Supported programming languages
        • Use cases and examples
      • Basic/Advanced AI models
      • Wingman Coding Agent
        • Key features
        • Supported tools
        • Getting started
    • Bito CLI
      • Overview
      • Install or uninstall
      • Configuration
      • How to use?
      • Available commands
      • FAQs
    • Google Chrome extension
  • Help
    • 🧠Bito's AI stack
      • Embeddings
      • Vector databases
      • Indexing
      • Generative AI
      • Large Language Models (LLM)
      • LLM tokens
      • LLM parameters
      • Retrieval Augmented Generation (RAG)
      • Prompts
      • Prompt engineering
    • 👥Account and settings
      • Creating a Bito account
      • Workspace
      • Managing workspace members
      • Setting AI output language
      • Managing user access levels
      • Access key
    • 💳Billing and plans
      • Overview
      • Payment methods
      • Managing workspace plan
      • Pay for additional workspace members
      • Advanced AI requests usage
      • Billing history
      • Billing details
      • Security
      • Refund policy
      • Discounts
    • ⚒️Support and questions
      • Getting support
      • Troubleshooting
      • Is it GPT-4?
  • 🆕Changelog
  • External Links
    • Git
    • Github Issues
    • Github Discussions
    • Bito.ai
    • VS Code Marketplace
    • JetBrain Marketplace
Powered by GitBook
LogoLogo

Bito Inc. (c) 2025

On this page
  • What is Indexable Size?
  • Is there any limit on repository size?
  • What if a repo hits 120MB limit?
  • What is .bitoignore and how to use it?
  • Common .bitoignore Patterns
  • Negation ! (exclamation mark)
  • .bitoignore Examples
  • Exclude Files/Folders
  • Exclude Everything Except Specific Files

Was this helpful?

Export as PDF
  1. Other Bito AI tools
  2. IDE extension
  3. AI that Understands Your Code

Managing Index Size

Exclude unnecessary files and folders from repo to index faster!

PreviousUsing in JetBrains IDEsNextFAQs

Last updated 1 month ago

Was this helpful?

What is Indexable Size?

Indexable size is size of all code files, excluding following from the folder:

  • Directory/File based filtering

    • logs, node_modules, dist, target, bin, package-lock.json, data.json, build, .gradle, .idea, gradle, extension.js, vendor.js, ngsw.json, polyfills.js, ngsw-worker.js, runtime.js, runtime-main.js, service-worker.js, bundle.js, bundle.css

  • Extension based filtering

    • bin, exe, dll, log, aac, avif, bmp, cda, gif ,mp3, mp4, mpeg, weba, webm, webp, oga, ogv, png, jpeg, jpg, bmp, wpa, tif, tiff, svg, ico, wav, mov, avi, doc, docx, ppt, pptx, xls, xlsx, ods, odp, odt, pdf, epub, rar, tar, zip, vsix, 7z, bz, bz2, gzip, jar, war, gz, tgz, woff, woff2, eot, ttf, map, apk, app, ipa, lock, tmp, logs, gmo, pt

  • Hidden files are filtered i.e., files starting with "."

  • All Empty files are filtered.

  • All Binary files are also filtered.

Is there any limit on repository size?

For workspaces that have upgraded to Bito's Team Plan, we have set the indexable size limit to 120MB per repo. However, once we launch the "AI that Understands Your Code" feature for our Free Plan users, they will be restricted to repositories with an indexable size limit of 10MB.

Learn more about above and see which files and folders are excluded by default.

You can reduce your repo's indexable size by excluding certain files and folders from indexing using file and remain within the limit.

What if a repo hits 120MB limit?

If a repo hits 120MB limit, then the below error message will be displayed in the "Manage repos" tab and the repo's index status will be changed to "Not Indexed".

Sorry, we don’t currently support repos of this size. Please use .bitoignore to reduce the size of the repo you want Bito to index.

What is .bitoignore and how to use it?

There are two ways to use .bitoignore file:

  1. Create a .bitoignore file inside the folder where indexes created by Bito are stored. e.g. <user-home-directory>/.bito/localcodesearch/.bitoignore

    • On Windows, this path will be something like: C:\Users\<your username>\.bito\localcodesearch\.bitoignore

    • Note: The custom ignore rules you set in this .bitoignore file will be applied to all the repositories where you have enabled indexing.

  2. Create a .bitoignore file inside your repository's root folder.

If a .gitignore file is available in your repo then Bito will also use that to ignore files & folders from indexing process. Both .bitoignore and .gitignore files can work together without any issues.

At present, Bito considers only those .gitignore files that are placed in the project root directory and .bitoignore files that are placed either in <user-home-directory\.bito\localcodesearch> or <project-root-directory>

Changes to the .bitoignore file are taken into account at the beginning of the indexing process, not during or after the indexing itself.

Please note that any changes to the .bitoignore or .gitignore file will take a minimum of 3 to 5 minutes to trigger new indexing.

Common .bitoignore Patterns

Understanding these patterns/rules is crucial for effectively managing the files and directories that Bito indexes and excludes in your projects.

Sample Rule
Description

# this is a comment.

Any line that starts with a # symbol is considered as a comment and will not be processed.

*

(Wildcard character) Ignores all files

**

(Wildcard character) Match any number of directories.

todo.txt

Ignores a specific file named todo.txt

*.txt

Ignores all files ending with .txt

*.*

Ignores all files with any extension.

Engine/ or Engine/**

Ignores all files in the Engine directory and their subdirectories (contents).

subdirectory1/example.html

Ignore the file named example.html, specifically located in the directory named subdirectory1.

!contacts.txt

(Negation Rule) Explicitly tracks contacts.txt, even if all .txt files are ignored.

!Engine/Batch/Builds

(Negation Rule) Tracks the Builds directory inside Engine/Batch, overriding a broader exclusion.

!Engine/Batch/Builds/**

(Negation Rule) Tracks the Builds directory and all of its subdirectories inside Engine/Batch, overriding a broader exclusion.

!.java

(Negation Rule) Ensures that all .java files are included, overriding any previous ignore rules that might apply to them.

!subdirectory1/*.txt

(Negation Rule) Track files with the .txt extension located specifically in the subdirectory1 directory, even if other rules might otherwise ignore .txt files.

BitoUtil?.java

The ? (question mark) matches any single character in a filename or directory name.

Negation ! (exclamation mark)

When a pattern starts with ! it negates the pattern, meaning it explicitly includes files or directories that would otherwise be ignored. For example, have a look at this sample .bitoignore file:

Engine/**
!Engine/Build/BatchFiles/**

Here !Engine/Build/BatchFiles/** pattern includes all files in the Engine/Build/BatchFiles directory and its subdirectories, even though Engine/** pattern would ignore them.

Avoid Ambiguous Patterns: Negation patterns can become confusing when they potentially match multiple files. Target specific files or folders rather than using wildcards in negation patterns.

For example, it is better to use patterns like !Engine/Build/BatchFiles/script.bat instead of !Engine/Build/BatchFiles/**

.bitoignore Examples

Exclude Files/Folders

# Ignore specific file named "config.ini"
config.ini

# Ignore all files with a '.bak' extension
*.bak

# Ignore all files with a '.kunal' extension
*.kunal

# Exclude directories
backup
temp/
dist/vendor

Exclude Everything Except Specific Files

To exempt a file, ensure that the negation pattern ! appears afterward, thereby overriding any broader exclusions.

# Ignore all files except C++, header and python files
*
!*.cpp
!*.h
!*.py

To fix this issue, follow our instructions regarding and reduce your repo's size and bring it under the max limit of 120MB.

After that, you must and then restart the indexing by clicking on the "Start Indexing" button shown for the repo folder. You can also follow our step-by-step guides to and IDEs.

A .bitoignore file is a plain text file where each line contains a pattern or rules that tells Bito which files or directories to ignore and not index. In other words, it's a way to reduce your repo's indexable size. You can also see .

Therefore, to implement changes made to the .bitoignore file, you'll need to and then restart the indexing by clicking on the "Start Indexing" button shown for the repo folder. You can also follow our step-by-step guides to and IDEs.

indexable size
.bitoignore
how to use .bitoignore file
which files/folders are excluded by default
Start Indexing in Visual Studio Code
Start Indexing in JetBrains
Start Indexing in Visual Studio Code
Start Indexing in JetBrains
delete the index
delete the index