rig queue create --return-route auto gives the conversation you hand work over from an address, so a seat's prompt that isn't a choice dialog comes back to it as a task; it arrives on that conversation's next turn, and arrival isn't guaranteed.
Hand a goal over with a return route: rig queue create --return-route auto gives your conversation an address, and every handoff carries it (--return-route self from a session that joined the team). When routed work is held at a seat's prompt, or waits on it, a prompt that isn't a choice dialog is sent to that address as a task. Choice prompts, a prompt already with the gateway, and a route that can't be used (another host's, two that disagree, or a relay that couldn't be made) keep their existing path. The rigs skill teaches this; without --return-route, nothing changes.
- Pull request
- #3318
- Release
- OpenRig 0.7.18 release notes