After a reply is interrupted, should I reconnect or ask again?
First confirm whether the original task is still running to avoid duplicate operations.
Distinguish between display disconnection and task stoppage first
The browser not continuing to display text does not necessarily mean the server or tool has stopped. Especially for Agent, a command may still be executing, or it may have completed but the result has not yet been displayed. Directly resending the execution request may cause duplicate work or repeated modifications.
First check the status of the original task and the last tool output, rather than immediately creating the same task again.
Prioritize restoring original task information
If the error area provides a reconnect option, you can use it first. If the environment is offline, you need to restore the corresponding computer; insufficient quota is not a network issue, reconnecting will not replenish quota.
If the original task was generating files, after restoring you can request a list of already generated files and their last status. Confirm which step is incomplete before continuing; even if the interface was once blank, do not let the agent immediately overwrite existing and possibly complete results.
- Keep the original task and check if it is still running or waiting for approval.
- Use the reconnect operation available on the page.
- Have the Agent check existing execution results and files before deciding whether to rerun.
When it is really necessary to restart
First record completed steps, target environment, and artifact locations, then only redo the remaining parts. When file writing is involved, check existing files first to avoid duplicate appending in an unknown state. Re-requesting may generate new usage; do not assume no consumption just because the previous output was not fully displayed. When troubleshooting, record errors without sensitive content and the time they occurred.