Agents

The Agent Builder is where you manage the agents available in your AI Hub account. It lists the built-in agents alongside any custom agents you created. The built-in agents are Change Tone, Fix Spelling and Grammar, Improve Writing, Liferay Search, Make Longer, and Make Shorter. From this view you create new agents, edit and duplicate existing ones, delete the ones you no longer need, and set permissions that control who can work with them.

Open the Agent Builder from the left navigation in the AI Hub UI. Agents are scoped per account, so the list shows your account’s catalog, not the agents of other accounts.

For a step-by-step walkthrough that builds a custom translation agent from an existing one, see Building a Custom Agent.

Viewing the Agent List

Click Agent Builder in the AI Hub left navigation to open the list. The Agents tab shows every agent in your account, built-in and custom.

Each agent is active or inactive, and you can filter the list by status. Each row has an Actions menu whose options depend on the agent type:

• Built-in Liferay-managed agents are read-only. Their Actions menu offers only View and Duplicate.
• Custom agents support the full set: View, Duplicate, Activate or Deactivate, Delete, and Permissions.

Creating or Duplicating an Agent

Note

On the Activate subscription tier, agent creation is limited:

• You must duplicate an existing agent, then customize it.
• You can create up to five custom agents.

To create a custom agent, start from a new or duplicated definition, then complete the agent form:

1. Click New Agent to start from an empty definition.

   Alternatively, duplicate an existing agent. From its Actions menu, click Duplicate. This copies the agent’s definition into a new agent, giving you a working starting point to modify instead of configuring everything from scratch.

2. Define the agent. Begin by giving it a Title and Description.

3. Click View Workflow to build the agent’s logic.

4. Name the agent’s inputs and its output in Input Variables (a comma-separated list) and Output Variable. For example, enter an input named text; the workflow you build references these names.

5. Keep the prefilled External Reference Code or set your own; it identifies the agent to external systems.

6. Use the Enable Agent toggle to make the agent active.

7. Optionally, add data sources in the Assigned Sources field, and assign guardrails.

For the full walkthrough, including editing the agent’s workflow logic, see Building a Custom Agent.

Editing an Agent

Built-in agents are read-only, so you can edit only custom agents. Open a custom agent to change its details and logic:

1. From the agent’s Actions menu, click View.

2. Edit the agent’s Title and Description.

3. Click Save.

4. To change the agent’s logic, click View Workflow and edit its workflow nodes.

5. Click Update to save your workflow changes.

Activating, Deactivating, and Deleting an Agent

These actions apply only to custom agents; built-in agents can’t be deactivated or deleted. Use a custom agent’s Actions menu to manage its lifecycle:

• Click Activate to bring an inactive agent back into service.
• Click Deactivate to take an active agent out of service while keeping its definition.
• Click Delete to remove the agent entirely.

Setting Agent Permissions

Agent access has two layers:

1. Account roles grant permissions across all agents. Assign a built-in role such as AI Hub Agent Administrator, and users with that role can work with every agent, so you don’t have to grant access on each agent individually. For the full set of built-in account roles, see Account Administration.

   Agents are scoped to an account, so you can grant access through account roles and regular roles. Site roles don’t apply.

2. Per-agent permissions apply to a single custom agent and can restrict, not expand, what a user’s account role already grants. For example, if an account role grants update access on all agents, a per-agent setting can remove update access on one sensitive agent, but it cannot give update access to a user whose role does not already have it.

   Per-agent permissions are available on custom agents only. Each custom agent has a dedicated Permissions modal, which uses the standard Liferay permissions component, the same one used for pages, fragments, and other DXP entities. To open it, click Permissions in the agent’s Actions menu. The modal lists each role with checkboxes for the permissions you can grant: View, Update, Delete, Permissions, and Object Entry History. Only users who hold the Permissions action can open the modal, and changes take effect immediately when you save.

Related Topics

• Building a Custom Agent
• Using the AI Assistant