The Workflow Step That Pages Another Agent — Addressing, Turns, and the Timeout That Doesn't Kill
Nov 1, 2026
5 min read
Every agent framework I’ve used can run a workflow where the steps are tool calls: hit an API, run a script, query a database. Almost none of them treat another agent as a first-class step. So this month I added one to Mule: forge_conversation, a workflow step type (Herd H3.2) where a mule job posts a message into a long-lived forge agent conversation, optionally waits for the turn to finish, and returns the assistant’s final text as the step output.