Overview
Agents created directly inside workflows are moving to the AI Agent hub. Until migrated, legacy agents remain functional but are read-only and cannot be edited. Workflows that still contain legacy agents display a banner indicating that migration is required.
How to use
Review agents flagged for migration
When the AI Agent hub is enabled, a banner appears at the top of the Workflows page listing the number of agents and workflows that require migration.
Open the migration list: Click Review in the banner to open a panel listing all agents flagged for migration, along with the workflow each agent belongs to.
Open a workflow: Select a workflow from the list to open it on the canvas.
Migrate an agent manually
Legacy agents on the canvas are marked with a Legacy label and an orange warning badge. Clicking a legacy agent opens its configuration in read-only mode.
Select the legacy agent: Click the agent step on the canvas. The configuration panel opens showing the agent's instructions, toolbox, and execution log: all read-only.
Start migration: Click Duplicate. A new browser tab opens with a pre-filled copy of the agent in the AI Agent hub.
Review the configuration: Check the migrated instructions, tools, and settings. Make any adjustments needed.
Publish: Click Save, then Publish to publish the agent and make it available in workflows.
Return to the canvas: Go back to the original workflow tab.
Swap the agent: Remove the legacy agent step from the canvas, then add the newly published agent from the Published agents panel.
Repeat: Repeat for any remaining legacy agents in the workflow.
The workflow banner disappears once all legacy agents have been removed from the canvas.
Migrate using Socrates Builder
Socrates Builder can handle the migration end-to-end. It creates a new agent in the hub, replaces the legacy operator in the workflow, and publishes, with your confirmation at each step.
Open Socrates Builder: Click Socrates at the top of the left sidebar, then select Builder from the agent picker. This gives it the elevated permissions the migration requires.
Create the agent in the hub: Send this prompt, replacing the placeholder with your workflow name. Socrates will locate the legacy operator, create a new agent in the hub from its configuration, and ask you to review and confirm the parameter names, data types, and any other settings before proceeding.
In the workflow "<Replace_with_your_workflow_name>" there is a legacy HyperAgent operator called "<Replace_with_the_Legacy_AI_Operator_Name>".Your task is, first, to create a new AI Agent in the Agents hub from this Legacy HyperAgent operator, and then modify the workflow, replacing the legacy HyperAgent with the new AI Agent you created in the Agents hub.Confirm and publish: Socrates will ask for your confirmation before replacing each instance of the legacy operator and before publishing each updated workflow. Review the changes and approve to continue.
Verify: Once migration is complete, send this prompt to check whether any legacy operators remain in the workspace. If Socrates finds remaining instances, repeat the process for each one.
Check if the Legacy HyperAgent operator named "<Replace_with_the_Legacy_AI_Operator_Name>" is being used in any other workflow in my workspace. If so, replace that legacy agent with the new agent you created in the Agents hub.
Legacy agent configuration
Legacy agents that have not been migrated remain on the canvas and continue to run, but their configuration is read-only. No edits can be made to a legacy agent's instructions, toolbox, or settings.
The configuration panel has three tabs:
Instructions: Shows the agent's role, instructions, and output schema. Read-only.
Toolbox: Shows the tools connected to the agent. Read-only.
Execution log: Shows the run history for the agent, including inputs, outputs, and action flow.
To make changes to a legacy agent, complete the migration steps above and edit the published copy in the AI Agent hub or via Socrates.