# Agents > **Note:** > This feature is currently in preview and available for all organizations participating in the [Early Access Program (EAP)](ai-settings.html#eap). It may change and become a paid feature later. For more information, see [Plans and pricing](plans-and-pricing.html). The Agents page lists AI agents compatible with [Agent Client Protocol (ACP)](https://agentclientprotocol.com/get-started/introduction) and available in your organization. Whether an agent is available to users and service accounts is governed by [AI policies](ai-policies.html). The [default policy](ai-policies.html#default-policy) initially makes all agents from this list available to everyone with [AI access](ai-access.html), so agents work out of the box until you configure policies to restrict them. To control which agents are available to specific users and service accounts, configure the default policy or create a custom one. The Policies column in the Agents table shows which AI policies each agent is used in. By default, the Agents page includes ACP-compatible agents sourced automatically from the [global agent registry](https://agentclientprotocol.com/get-started/registry). This includes, among others, agents featured in [JetBrains IDEs](https://www.jetbrains.com.cn/en-us/help/ai-assistant/junie-agent.html) and [JetBrains Air](https://www.jetbrains.com.cn/en-us/help/air/supported-agents.html), such as Junie by JetBrains, Claude Agent, Codex, and Gemini CLI. If a new agent appears in the global registry, it is automatically added to the Agents table. These agents cannot be deleted from the list. Users can also add ACP-compatible agents locally in their IDEs if the relevant AI policy allows it. > **Note:** > Viewing the page requires the [View AI settings](roles.html#permissions_view_ai_settings) permission. Managing agents requires the [Manage AI settings](roles.html#permissions_manage_ai_settings) or [Manage organization](roles.html#permissions_manage_org) permission. ## Custom agents You can manually add custom ACP-compatible agents not listed in the global registry using a JSON configuration. Procedure: Add a custom agent 1. In the sidebar, under AI governance, select Agents. If you don't see this page, or the controls on this page are inactive, your role doesn't have the necessary [permissions](roles.html#permissions). 2. Click New custom agent. 3. In the Add custom agent dialog, paste or type the agent JSON configuration. For the full list of available fields, refer to [the ACP agent format reference](https://github.com/agentclientprotocol/registry/blob/main/FORMAT.md) and the [JSON schema](https://github.com/agentclientprotocol/registry/blob/main/agent.schema.json). > **Note:** > JetBrains Central Console validates only that `name` is present and, if `icon` is provided, that it is an `https://` URL or a `data:image/...` URI. All other fields are accepted as is. 4. Click Add. A success message appears in the lower right corner. The custom agent is now listed in the table. > **Warning:** > It is the org admin's responsibility to verify that the custom agent configuration is correct. JetBrains Central Console does not provide a way to check that the agent actually exists or that its configuration will work in [AI Assistant](https://www.jetbrains.com.cn/en-us/help/ai-assistant/about-ai-assistant.html). You can add a non-existent agent, an incorrect command, or unsupported options, but the configuration is still saved and listed in the Agents table. > > > > If the JSON configuration doesn't match what AI Assistant expects, the agent doesn't appear in the IDE, and no error is shown. If the configuration is accepted but the agent fails to start, an error is displayed in [AI Chat](https://www.jetbrains.com.cn/en-us/help/ai-assistant/ai-chat.html) when the user tries to use the agent. Procedure: Edit a custom agent 1. In the sidebar, under AI governance, select Agents. If you don't see this page, or the controls on this page are inactive, your role doesn't have the necessary [permissions](roles.html#permissions). 2. In the Agents table, find a custom agent you want to edit. 3. Click ![Ellipsis icon](images/union.svg) in the corresponding row and select Edit. 4. In the dialog, make the necessary changes to the JSON configuration. 5. Click Save. A success message appears in the lower right corner. > **Tip:** > To review a custom agent's configuration in read-only mode, click ![Ellipsis icon](images/union.svg) in the corresponding row and select View. Procedure: Delete a custom agent > **Warning:** > Deleting an agent used in an [AI policy](ai-policies-configure.html#agents-tab) will cause users and service accounts under that policy to lose access to the agent. To check which policies are affected, review the value in the Policies column of the Agents table. 1. In the sidebar, under AI governance, select Agents. If you don't see this page, or the controls on this page are inactive, your role doesn't have the necessary [permissions](roles.html#permissions). 2. In the Agents table, find a custom agent you want to delete. 3. Click ![Ellipsis icon](images/union.svg) in the corresponding row and select Delete…. 4. In the dialog, click Delete. A success message appears in the lower right corner. The agent is removed from the table and all the affected AI policies.