Skip to main content
The /migrate command tells Astro to automatically convert your agent from the old agent loop to the new loop. The new loop uses only iris (AI task) and output nodes, removing legacy node types like url, playwright_script, and api.

​
When to Migrate

Migrate if your agent was built before the new loop was introduced and contains any of these legacy node types:
  • url — standalone URL navigation nodes
  • playwright_script — raw Playwright script nodes
  • api — direct API call nodes
New agents built today use the new loop by default.

​
How to Use /migrate

Open Astro on your agent’s Builder page and type: 
/migrate
Astro will analyse your current agent and apply all necessary transformations automatically, then save a new draft.

​
What Gets Changed

Sets new_agent_loop: true in the agent’s config.yaml settings block.
Each url node is removed. Its target URL is merged into the nearest downstream iris node as a “go to <url>” instruction at the start of that node’s prompt.
Each playwright_script node is replaced by an iris node whose prompt describes the same action in the iris scripted-node format.
Each api node is removed. The nearest relevant iris node is updated with an instruction to call the API via bash instead.
On every iris node, all tools are removed except dom_browser_interaction, browser_run_code, and generate_totp_secret (only kept if that node genuinely needs it).
All uses of “routing” and “interrupting” are replaced with “hand off”.
Scratchpad read/write operations are replaced with output variable operations — for example, “place the result on the scratchpad” becomes “pass the result as an output variable”.
Outcome-selection logic (e.g. “hand off with outcome ‘success’ if X, ‘failure’ if Y”) is moved out of iris node instructions and into the corresponding output node’s instructions.md, with instructions_enabled: true set on that output node.
Any iris node using the query_context tool has that tool removed. The node is updated to read the value from the execution data variable directly, and the upstream node is updated to output that value explicitly.

​
After Migration

Once Astro saves the draft, review the changes in the Builder before publishing:
  • Confirm no url, playwright_script, or api nodes remain
  • Check that each iris node’s prompt accurately describes the intended behaviour
  • Verify that output nodes have the correct outcome-selection criteria in their instructions
  • Run a test execution to confirm the agent behaves as expected