The page and the run have separate lifecycles
Closing a tab, navigating elsewhere, or losing a temporary connection is different from explicitly stopping a run. The agent may continue processing after you leave, depending on the run state and service availability.
When you return, open the same run rather than starting a duplicate task. Check whether it completed, is still active, or needs your input before deciding what to do next.
Review completion before acting on results
Read the run's final response and any listed actions or errors. If the agent produced a file or changed a resource, verify that result in its destination before relying on it.
If you do not want the work to continue, stop the run from its controls. Starting a replacement while the first run is still active can duplicate external actions, consume additional resources, or produce conflicting outputs.