Manage repository indexing
When Air Context indexing is allowed for your organization, you can control indexing for each individual repository. Each row in the list of repositories has a Status that reflects the repository's current indexing state and a menu of actions available for that state. A repository that is indexed both by JetBrains Central and on demand has a row on each tab, and the two rows have independent statuses and are managed independently.
A repository can have one of the following statuses in the Status column:
Status | Description |
|---|---|
Indexed | The repository has been indexed successfully. Repositories indexed by JetBrains Central are re-indexed periodically. Repositories indexed on demand are re-indexed only when the Air Context CLI is run on them again, so the Last indexed column shows No periodic indexing, and the date can be much older. |
Indexing | Initial indexing of a repository that has not been indexed yet is in progress. This status does not apply to subsequent periodic re-indexing when an index already exists: the previous status (such as Indexed) is kept instead. |
Deleting | The repository's indexes and all associated data are being removed, for example, after an admin deletes the index of the repository or deletes the remaining indexes after blocking indexing. |
Not indexed | The repository is not indexed. On the Indexing by JetBrains Central tab, you can start indexing directly from JetBrains Central Console. On the On-demand indexing tab, the Last indexed column shows Never and Run on demand: indexing can't be started from JetBrains Central Console and must be triggered by running the Air Context CLI. |
Restricted | An admin has restricted indexing for this repository specifically, independently of the organization-wide settings. The existing index, if any, is kept until you delete it. The admin can allow indexing for the repository again at any time. |
Failed | The initial indexing failed, and no index is available. On the Indexing by JetBrains Central tab, you can start indexing again from JetBrains Central Console; on the On-demand indexing tab, run the Air Context CLI again. |
Reindexing failed | A re-indexing attempt failed, but the previous index is still available. The Last indexed column shows the date of the last successful indexing, marked Last successful index. On the Indexing by JetBrains Central tab, you can start indexing again from JetBrains Central Console; on the On-demand indexing tab, run the Air Context CLI again. |
The actions available for individual repositories in JetBrains Central Console are listed below.
Restrict indexing for a repository
You can restrict indexing for a single repository on either tab. Restricting a repository prevents it from being indexed again. Its existing index is kept until you delete it.
In the sidebar, under Integrations, select Air Context.
If you don't see this page, your role doesn't have the necessary permissions.
In the list of repositories, in the repository's row, click
and select Restrict. A confirmation dialog is displayed.
Confirm that you want to restrict indexing.
The repository's status changes to Restricted.
Delete the index of a repository
You can delete the index of a single repository on either tab, whether indexing of the repository is allowed or restricted. Deleting the index does not change whether the repository can be indexed again.
In the sidebar, under Integrations, select Air Context.
If you don't see this page, your role doesn't have the necessary permissions.
In the row of the repository, click
and select Delete index. A confirmation dialog is displayed.
Confirm the deletion.
Deleting the index may take some time; until it is done, the repository shows the Deleting status. AI agents lose the context the index provided.
Allow indexing for a repository
When you allow indexing for a restricted repository, the restriction is lifted, but indexing does not start automatically. Repositories on the Indexing by JetBrains Central tab are indexed when you start indexing them; repositories on the On-demand indexing tab are indexed after their indexing is triggered through the Air Context CLI. On the On-demand indexing tab, the action is available only while on-demand indexing is allowed in the Settings pane.
In the sidebar, under Integrations, select Air Context.
If you don't see this page, your role doesn't have the necessary permissions.
In the row of the restricted repository, click
and select Allow. The repository is no longer Restricted. If it has no index, its status is Not indexed.
Trigger indexing for a repository
On the Indexing by JetBrains Central tab, you can trigger indexing for a repository that is not indexed yet.
In the sidebar, under Integrations, select Air Context.
If you don't see this page, your role doesn't have the necessary permissions.
In the row of a repository with the Not indexed status, click
and select Start indexing. Indexing starts without a confirmation, and the repository's status changes to Indexing.
Restart failed indexing
If indexing of a repository fails, you can start it again.
In the sidebar, under Integrations, select Air Context.
If you don't see this page, your role doesn't have the necessary permissions.
In the row of a repository with the Failed or Reindexing failed status, click the retry button next to the status.
Indexing starts again. A repository with the Failed status changes to Indexing; a repository with the Reindexing failed status keeps its previous index available until the new one is ready.
Manage indexing for multiple repositories
Instead of managing repositories one by one, you can select several repositories on a tab and apply the same action to all of them at once.
In the sidebar, under Integrations, select Air Context.
If you don't see this page, your role doesn't have the necessary permissions.
In the list of repositories, select the checkboxes next to the repositories you want to manage.
In the toolbar that appears at the bottom of the page, click the action to apply to the selected repositories. The toolbar offers only the actions that are available for the selected repositories.
If the action deletes existing indexes, a confirmation dialog is displayed. Confirm it to proceed.