# Agent Configuration The Agent Configuration page allows URL administrators to control which object types each agent can operate on within a URL. This provides fine-grained control over agent behaviour. > **Note:** Agent configuration is only available for URLs that have LLM Agents enabled. The **Agents** link will only appear on the URL home page and in the URL breadcrumbs if agents are enabled for the URL. ## Accessing Agent Configuration Navigate to the URL home page and click the **Agents** card. This requires the **Manage Agent Configuration** permission. ## Agent List The agent list page shows all configurable agents with their current configuration: | Column | Description | | --- | --- | | **Agent** | The name of the agent. Click the name to edit its configuration. | | **Description** | A brief description of what the agent does. | | **Configured Object Types** | The object types the agent is configured to work with. If no object types are selected, the agent will not activate for any object type. | ## Editing Agent Configuration Click an agent name or the **Edit** button to open the configuration page for that agent. The edit page displays all object definitions available in the URL as a list of checkboxes. Select the object types that the agent should work with and click **Save**. > **Important:** If no object types are selected, the agent will not activate for any object type within the URL. This effectively disables the agent for this URL. ## Agent Action Hooks Agent action hooks allow you to automatically run [actions](../urls/actions/index.html.md#actions) when an agent completes a review. For example, after the Spec Review agent finishes reviewing an object, a hook can automatically add a label such as "Agent Reviewed" to the object. Only actions with the **Agent** [action type](../urls/actions/index.html.md#action-type) can be used as hooks. User and Auto actions will not appear in the hooks configuration. To create an action for use as a hook: 1. Create an action with the Action Type set to **Agent action**. 2. Set the action's object type to match the object type the agent reviews. 3. Configure the action's operations (e.g. add label, send email). 4. On the agent configuration edit page, select the action under the appropriate hook trigger. Hook triggers and exported variables vary by agent. See the [Agents Catalog](agents_catalog.html.md) for the hooks available on each agent and the variables they export for use in action preconditions. A hook action's precondition must result in True or False, and may only use the variables exported by the hooks the action is selected for. Variables are True/False, numbers or text. Compare numbers and text explicitly, for example `agent("error_count") > 0` or `agent("reason") != ""`, because `agent("reason") or agent("error")` results in text rather than True or False. Saving the agent configuration, or an action that is already selected under a hook, reports any precondition that breaks these rules and saves nothing. ## Permission To manage agent configuration, a user must have the **Manage Agent Configuration** URL permission. This permission can be assigned via the URL [Teams](../urls/url_teams.html.md#url-teams) page.