Help Center/ CodeArts Agent/ User Guide (Console)/ Agent Settings/ Repository Index Management
Updated on 2026-09-17 GMT+08:00
View PDF
Share

Repository Index Management

Repository indexes help you quickly search and retrieve relevant information within your repositories. You can create and delete cloud indexes on the console. The created indexes can be synchronized to the CodeArts Agent client.

CodeArts Agent supports two types of indexes: local indexes (created on the client) and cloud indexes (created on the console).

This section describes how enterprise members manage cloud indexes on the console. For details about how to manage local indexes on the client, see Repository Index.

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

Package Edition

Description

Language

-

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

Seats

-

Only accounts with enabled seats can create and delete the cloud indexes.

Total number of code files

Free

Up to 5,000 code files can be indexed.

Basic

Up to 50,000 code files can be indexed.

Professional

Up to 100,000 code files can be indexed.

Functions

Free

Only user-level cloud repository indexes can be created.

Basic/Professional

Cloud repository indexes of the enterprise, team, and user levels can be created.

Creating Cloud Indexes

You can use repository indexes to build a vector index, enabling intelligent, feature-level retrieval and precise matching based on code semantics.

  1. Log in to the CodeArts Agent console as an enterprise member or administrator.
  2. Choose Agent Settings > Repository Index.
  3. Click Create Repository and set basic index information.

    Table 3 Repository index parameters

    Parameter

    Description

    Visible To

    Visible scope of the repository index.

    • Private: available only to members themselves.
    • Team: available only to team members and created by the enterprise administrator, team administrator, or team members.
    • Enterprise: available to all enterprise members and created by the enterprise administrator, team administrator, enterprise members, or team members.

    Available Team

    This parameter is displayed only when Applied To is set to Team.

    Enterprise administrators can view all teams but can select only one, while team administrators can only view and select the team they belong to.

    code source

    Source of the code repository that you want to index.

    • Git: a general Git repository.
    • GitHub: a GitHub repository, which can be a public repository or an authorized private repository.

    Authorization Method

    Select a service endpoint from the drop-down list. The endpoint corresponds to the connection information of the GitHub or Git repository.

    If no service endpoint has been created, click creation to create one by referring to Table 4.

    Language

    This parameter is displayed only when code source is set to Git.

    Select a language from the drop-down list.

    Default Branch

    This parameter is displayed only when code source is set to Git.

    Enter the branch name of a Git repository. The branch name can contain a maximum of 200 characters.
    Table 4 Service endpoint parameters

    Parameter

    Description

    Connection Name

    Name of the custom repository to be connected.

    Naming rules: The name can contain letters, digits, underscores (_), and hyphens (-), but cannot start with an underscore.

    Git URL

    This parameter is displayed only when Code Source is set to Git.

    HTTPS access address of the Git repository

    User Name

    This parameter is displayed only when code source is set to Git.

    User name for HTTPS authentication of the Git repository.

    Password or Access Token

    This parameter is displayed only when code source is set to Git.

    Password or access token for HTTPS authentication of the Git repository.

    Access Token

    This parameter is displayed only when code source is set to Github.

    Access token for HTTPS authentication of the GitHub repository.

  4. If you set code source to Git, click OK to create the repository index. If code source is set to GitHub, click Next, select your repository and language, and click OK.

    When its status changes from parsing to parsing completed, the code has been successfully parsed and the index has been successfully created.

  5. Open the client and navigate to the target repository project. The system will automatically synchronize the repository index from the cloud.

    When the progress reaches 100%, the repository index has been synchronized.

  6. Verify that the index has been successfully created.

    Describe your requirements in natural language. The system invokes the CodeSemanticSearch tool to perform in-depth code search based on natural language semantics, breaking through keyword restrictions.

    How is request status processing implemented?

Deleting Cloud Indexes

Table 5 shows the operation permissions of different roles to delete repository indexes.

Table 5 Scope of repository indexes that can be deleted by different roles

Role

Enterprise-Level Repository Index

Team-Level Repository Index

User-Level Repository Index

Enterprise administrator

All repository indexes

All repository indexes

All repository indexes

Team administrator

All repository indexes created by the user

All repository indexes created by a team administrator and team members

All repository indexes created by the user

Team member

All repository indexes created by the user

All repository indexes created by the user

All repository indexes created by the user

Enterprise member

All repository indexes created by the user

No operation permissions.

All repository indexes created by the user
Table 6 Repository index management on the console

Operation

Procedure

Delete a specified repository index.

When there are only several indexes, you can delete them one by one.

  1. On the Repository Index page, locate the target index, and click Delete in the Operation column. The Delete Repository Index dialog box is displayed.
  2. Enter DELETE or click Autofill, and then click OK to delete the index.
    The target index cannot be found on the Repository Index page, indicating that the deletion is successful.
    CAUTION:

    The deleted index cannot be restored. Exercise caution when performing this operation.

Delete the repository indexes in a batch.

If there are many indexes, you can delete them in batches.

  1. Select the target indexes and click Batch Delete in the upper right corner. The Delete Repository Index dialog box is displayed.
  2. Enter DELETE or click Autofill, and then click OK to delete the selected indexes.

    The target index cannot be found on the Repository Index page, indicating that the deletion is successful.

    CAUTION:

    The deleted index cannot be restored. Exercise caution when performing this operation.
Parent Topic: Agent Settings