Deploying the agent
When you decide that an agent is ready for use by your team, you need to deploy it to move it from draft to live.
An agent in draft is under development and not yet available in channels like chat. Deploying the agent makes it live with the current set of functions that are used to ground its behavior.
After deployment, you can use the agent in the channels set up during its development. For more information, see Connecting to channels.
Before you begin
Make sure that your agent includes the required details, such as a name and description, before you deploy.
Deploying your agent
Click Deploy from the agent configuration page to view the Pre-deployment summary page. It includes a summary of its components, connection status, and deployment controls.
Pre-deployment summary configuration
This part shows the agent's key components in one place. You can review the selected model, uploaded files, linked tools, defined instructions, and any collaborators before you deploy.
| Section | Information displayed |
|---|---|
| Profile | Agent description and selected model |
| Knowledge | Uploaded district files |
| Tools | Associated tools and their connection status |
| Collaborators | List of collaborators (if any) |
| Behavior | Instructions expected by the agent |
A green checkmark appears next to each tool when its security schema matches the linked connection.
Connections
This part outlines the structure of the agent's active connections. Each column describes how the agent interacts with external systems and tools.
| Heading | Description |
|---|---|
| Server | A target server or an endpoint that is linked to the connection. |
| Associated tools | Tools that reply in this connection. Multiple tools can share one connection. |
| Live | Indicates whether the connection is active in the production environment. |
| Connection status | It shows whether the connection is established or broken. |
Connection validation
The deployment interface displays only connections to the live environment. It helps ensure that the agent is linked to production-ready systems and avoids confusion with draft configurations.
If a required tool is not connected, the Deploy button remains disabled. To continue, set up the missing connection by using the following steps.
Setting up a connection
Follow this procedure to configure a new connection for your agent, including authentication and credential settings.
-
Click Add connection +.
-
Enter the Connection ID.
-
Enter the Display name.
-
Click Save and continue.
-
To enable single sign-on, toggle Single sign-on (SSO) on.
-
Select an Authentication type:
- API Key
- Basic Auth
- Bearer Token
- Key Value Pair (only for Team credentials)
-
Enter the required details for the selected authentication type.
-
Choose a credential type:
- Member credentials: Each user can access the application by using their own credentials.
- Team credentials: All users access the application by using shared team credentials.
-
Click Add connection.
The connection appears in the table. To edit it, click the pencil icon
.
-
Click Deploy to complete the setup. You return to the agent configuration page.
After setup, the agent's status is indicated by a live icon
. Hover over the icon to see the deployment timestamp in your local time zone.
Undeploying the agent
The undeploy option is available when the agent is live. Selecting it opens a confirmation dialog that outlines the impact:
- Production instances are interrupted.
- Access to the live environment is restricted.
- The agent becomes unavailable to users.
After undeployment:
- The agent returns to the draft state.
- The interface updates immediately.
- The agent is removed from live search results.
Agents in the draft state do not appear in chat search results.
To undeploy an agent,
- Go to the agent configuration page.
- Click the overflow menu
.
- Select Undeploy.
- Click Undeploy to confirm.
What to do next
After you deploy the agent, your agent becomes available across all configured channels. For more information on using agents in watsonx Orchestrate chat, see Using agents in the watsonx Orchestrate chat.