Stop the run as a whole
An agent can start subagents to handle parts of a task. When the parent agent is stopped, IaGenify propagates the stop signal to its children so they do not continue working as detached tasks. This is useful when the request has changed, the run is taking an unwanted direction, or you need to halt activity promptly.
The stop signal also aborts the active controller where possible. An operation that has already changed an external service may not be reversible simply because the run is stopped. Review which tool calls completed before stopping and check their results before deciding whether a follow-up or cleanup is needed.
Restart with a clear handoff
After stopping, inspect the conversation and any completed tool results to understand what was finished. If you want to continue, start or resume with a precise request that says what to keep, what remains, and any new constraints. Do not assume a stopped run completed its final response or finished every tool call it had planned.
If the run was stopped because a permission request or tool operation looked wrong, correct the underlying instructions or target before trying again. A fresh run can still repeat completed external work if you do not explain what already happened. Include relevant outcomes while avoiding passwords, tokens, and other private credentials.