> ## Documentation Index
> Fetch the complete documentation index at: https://docs.qoder.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Workspace index

> Check and update the code index for workspaces opened in Qoder.

Workspace indexing improves context understanding to help agents provide more accurate answers. When you first open a project, you can choose to create an index and configure automatic incremental updates for subsequent changes. Use `.gitignore` and `.qoderignore` to exclude files that do not need to be indexed. Cross-project indexing at the workspace level is also supported.

For data processing, workspace indexing uploads only the necessary code files, excluding configuration files, secrets, and other nonessential files, to generate vector data in the cloud. The uploaded code files are destroyed after vector generation. Only vector data is retained in the cloud.

An index improves retrieval across a repository; it does not replace opening and checking the source files used for a change. Exclude generated output, dependencies, logs, and sensitive local files so results stay focused on maintainable project content.

## Check a workspace

1. Open the user menu and select **Settings**, or use the Settings shortcut.
2. Under **Coding**, select **Workspace index**.
3. Select the workspace you want to inspect.
4. Check **Index status**.

When the status is **Not indexed**, select **Start indexing**. With **Automatic indexing** enabled, Qoder automatically creates and updates indexes for repositories with fewer than 10,000 files.

Under **Ignore files**, select **Manage ignore files** to edit `.qoderignore` in the workspace root. It follows `.gitignore` matching rules, and entries from `.gitignore` are excluded by default.

<a id="enterprise-indexing-policy" style={{ display: "block", scrollMarginTop: "8rem" }} />

### Enterprise indexing policies

Qoder CN public-cloud deployments support workspace indexing settings and enterprise indexing policies. When creating a local workspace, choose the initial indexing option offered by the interface; the choice is associated with the current account.

For enterprise accounts, review organization policy and the options available to you. Follow organizational requirements for managed options; a personal choice does not override organization policy.

Custom-domain and VPC deployments do not automatically use the public-cloud settings entry. Consult the relevant enterprise guidance for availability, policy options, and configuration.

## Exclude files from the index

Use one pattern per line in `.qoderignore`:

| Pattern             | Result                                       |
| ------------------- | -------------------------------------------- |
| `config.local.json` | Excludes one file.                           |
| `dist/`             | Excludes the entire directory.               |
| `*.log`             | Excludes files with the `.log` extension.    |
| `**/generated/`     | Excludes generated directories at any depth. |

Select **Save** after editing. Avoid excluding source directories merely to make indexing faster; excluded content cannot be retrieved through the workspace index.

## Confirm the result

After an update, return to a task in the same workspace and ask Qoder to locate a known symbol or recently changed file. Confirm that the answer cites the expected file rather than relying only on the status shown in Settings.

## Troubleshoot indexing

If indexing does not update as expected, first confirm that the workspace path is accessible. Then check whether `.gitignore` or `.qoderignore` excludes the file. Reopen the workspace tab in **Settings → Workspace index** and review the status. Repositories with 10,000 files or more are not automatically indexed by **Automatic indexing**; select the workspace and start indexing manually.