Help Center/ CodeArts Agent/ User Guide (IDE)/ Context/ Repository Indexing
Updated on 2026-09-17 GMT+08:00
View PDF
Share

Repository Indexing

You can build an index for your project to improve the speed and accuracy of AI-powered code search, making the results more aligned with your needs. You can also configure ignored files to specify the files to be excluded from indexing. Ignored files will be completely excluded from indexing to protect your sensitive data.

Indexing Modes

Two indexing modes are provided. Choose the one that best suits your workflow.

  • Local indexing: In this mode, the system builds a graph index locally by parsing local project code files, and precisely retrieving calls, dependencies, and inheritance between functions, classes, and files.
  • Cloud indexing: In this mode, the system builds a vector index, enabling intelligent, feature-level retrieval and precise matching based on code semantics. If you are using the free/basic/professional edition, ensure that your account has been assigned a seat. If not, cloud indexing will fail.
Table 1 Comparison of local and cloud indexing modes

Dimension

Local Indexing

Cloud Indexing

Storage location

Index files are stored locally (under .codegraph in the current project's root directory).

For the initial build, the complete index package is uploaded and stored in the cloud. Incremental indexes generated due to code changes are stored locally (under .codeartsdoer/.codebase in the current project's root directory).

Search capabilities

Search by keyword, symbol, and file name is supported.

Semantic understanding and repository-wide code logic analysis are supported.

Build rules
  • Projects with fewer than 50,000 files: Indexes are automatically built when the project is opened.
  • Projects with 50,000 or more files: Manual triggering is required for the first build.

Update rules

Automatic update upon file changes

Indexes are automatically updated when Auto Update is enabled and the number of repository files is less than 50,000. In other scenarios, manual operations are required.

Constraints

Table 2 Constraints

Category

Description

Language

Java, JavaScript, TypeScript, Go, ArkTS, C, C++, Python, Vue, and Lua.

Total number of indexed code files
  • Free edition: ≤ 5,000
  • Basic edition: ≤ 50,000
  • Professional edition: ≤ 100,000

Function
  • The creation of team and enterprise repository indexes in the cloud is supported only in the basic and professional editions.
  • Local indexes can be created only on Windows and Linux.

Building a Repository Index

  1. Log in to CodeArts Agent IDE as instructed in Quick Start.
  2. Click in the upper right corner of the page to access the global settings page of the IDE.
  3. Click Repository Index to view the index building result.

    If the page matches Figure 1, your project has fewer than 50,000 code files and the index has been built. If not, you can build a local index or cloud index as required.
    Figure 1 Index created

  4. Enter what you want to search for to view the code search results. 

    Find all calls to is_input_required in the repository, including cross-file call relationships.
    Figure 2 Viewing search results

Managing Repository Indexes

In addition to creating an index, you can also resume or delete it. For details, see Table 3.

Table 3 Managing repository indexes

Operation

Instruction

Pause cloud indexing

Click Pause to halt the indexing process at any time.

Resume cloud indexing

To resume a paused indexing process, click Resume Indexing.

Synchronize cloud updates

Click Update for incremental index update. The system checks for changes since the last update, indexes the added or modified code files, and skips unchanged files to save time.

Recreate cloud indexing

If you have deleted an index and want to rebuild it, click Create Index to begin a complete indexing process.

Delete a cloud index

To clear all current index data, click Delete Index.

In addition to deleting a repository index on the client, you can also perform the deletion on the console. For details, see Deleting Cloud Indexes.

Ignore files in the current directory

If you want to exclude any file in the current folder from being indexed, click Configure. Then, in .codebaseignore, specify the file name.
Parent Topic: Context