Agent Version Control
Explore SeaChat's powerful agent duplication and replacement features, designed for creating and managing different versions of your AI agents. Perfect for prototyping, testing, and smoothly transitioning from development to production.
Agent Duplication
๐What is duplicated?
When an agent is duplicated or replaced, the agent’s basic info, advanced settings, knowledge base, and widget are concerned. Channels cannot be duplicated or replaced.
Agent duplication is a feature that allows you to create a new agent based on an existing one. This is useful when you want to create a new agent with similar settings as an existing one.
To duplicate an agent, click on the Agent Duplicate button located next to the agent you want to duplicate in Agents under Workspace. This will create a new agent called {Agent Name} (COPY) with the same settings as the original agent. You can then modify the settings by clicking on Edit or by going to Agent Information.
Duplicate Agent Button
This feature is very powerful for agent editors when prototyping new agent settings and separating development and production agents for testing and optimization.
This process might take some time depending on the complexity of the agent. Once you see the success message, you can start training your agent. Everything is set up, including the available knowledge base and agent information.
Duplication Confirmation
For users with integrations or channels connected to the original agent, you will need to update the integration to include the new agent copy since the agent copy is still a new agent.
Agent Replacement
๐What is replaced?
When an agent is duplicated or replaced, the agent’s basic info, advanced settings, knowledge base, and widget are concerned. Channels cannot be duplicated or replaced.
The agent replacement feature provides an efficient way to manage different versions of your agent.
This is particularly useful when you want to develop an existing agent without affecting the original version. By using this feature, agent editors can make changes to a copy of the original agent rather than modifying the original agent directly.
Agent Replacement
A common use case might look like this:
- Duplicate the original Agent A and name the copy Agent B (Agent A Copy).
- Add new features to Agent B and test them.
- Once development is complete, replace Agent A with Agent B.
- Now, the new agent is running in production with the original settings from Agent A and the new features implemented in Agent B.
Agent Replacement Workflow
By following this process, you can keep the original agent running in production while developing and testing a new version of the agent.