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. |
Available on |
Where the agent is available on this URL. Most agents, including the Edit Check, Test Case and Custom Function creators and the Custom Function Reviewer, can be opened from the agent menu whatever object types are selected, and the column says on which pages. For Specification Review it is the object types selected in its configuration, and Nowhere when none are selected or it has never been configured on the URL. |
Actions |
The actions the agent's hooks run. |
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
The object types selected decide on which object pages an agent offers its help. For Specification Review they are also the only place it can be used: with none selected, it is not available anywhere on the URL. The Edit Check, Test Case and Custom Function creators can always be opened from the agent menu, and with none selected they offer their help on every object type.
Agent Action Hooks
Agent action hooks allow you to automatically run 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 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:
Create an action with the Action Type set to Agent action.
Set the action's object type to match the object type the agent reviews.
Configure the action's operations (e.g. add label, send email).
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 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 page.