Configuration File

Configure what parts of your repository are indexed and how the repository is tagged using the .ai_config.toml file.

What is .ai_config.toml?

It’s an optional config file you add to the root of your repository, only one file per repository.

With .ai_config.toml you can:

• Decide which files should be included or excluded when indexing the repository.

• Add tags that describe the repository's content.

Why use a configuration file?

Using this file helps:

• Cut out noise (like test files, old folders, or logs).

• Make sure only the important parts of your codebase are used in Qodo Gen responses.

• Tag your repository with helpful labels so people can filter and find what they need more easily.

---

How to use the configuration file

Create a file called .ai_config.toml in the root folder of your repository.

You can use two optional sections: file_filters and tags.

file_filters (What to include or exclude)

This section tells Qodo Gen which files to include or ignore when indexing your repository.

Each list consists of file paths marked by quotes '', divided by commas ,.

Example:

[file_filters]
include = ['src/**/*.py', 'config/*.json']
exclude = ['tests/*', 'src/legacy/**']

What this does:

• ✅ Includes all Python files under src/ (including subdirectories), and all JSON files under config/.

• ❌ Excludes anything in the tests/ folder and everything under src/legacy/.

Notes:

• If you don’t use include, everything is included by default.

• If a file matches both include and exclude, it will be excluded.

Use this to focus on the parts of the repository that matter most and skip folders that add noise.

tags (Describe your repository)

This section enables you to label your repository with different attributes.

Tags help categorize and describe the repository's contents, which can help Qodo Gen in search and classification of files.

Each tag group consists of a key (representing the tag category) and a value, which can be a single tag or a list of tags associated with that category.

Example:

[tags]
project_type = "web_app"
languages = ["python", "javascript", "html", "css"]
framework = ["django", "react"]
team = ["frontend", "backend", "qa"]
environment = "production"

What this means:

• This repository is a web app.

• It uses Python, JavaScript, HTML, and CSS.

• It’s built with Django and React.

• It’s owned by the frontend, backend, and QA teams.

• It’s running in the production environment.

Tips:

• Tag names should be unique.

• Keep tag keys lowercase for consistency.

• Use tags that will help others (or yourself) filter codebases later.

• The repo’s full name (e.g. org-name/repo-name) is automatically added as a tag—you don’t need to add it manually.

Summary

Feature	What it does
file_filters	Choose what parts of your codebase get indexed
tags	Add searchable labels so your repo is easier to find/use

Adding a .ai_config.toml file is optional, but highly recommended for bigger projects or teams working with multiple repos.