Reconnect to CloudShell and check what survived: list your home directory and look for the files you were working on.

Check whether the command you left running finished before the disconnect by looking for its output files or its effect (for example the resource it was creating in the AWS console).

Change how the work is staged: write scripts and intermediate results into files in the home directory instead of relying on scrollback or shell variables.

Keep individual CloudShell commands short. Break a long build or migration into stages that each finish in a few minutes, saving state between stages.

For a job that must run unattended for a long time, start it on a service built for that instead: an EC2 instance, a CodeBuild job, or a Systems Manager command on a managed instance, then use CloudShell only to launch and check it.

If disconnects happen after only a minute or two rather than after a real idle pause, test in a second browser and check for a corporate proxy or browser extension interrupting the console connection.

---

## Vectle citations

- Exact version: <https://vectle.com/skills/skl_Yu03sn_D7Esc78G8UEOCJw/versions/skv_9NEqXORGhQv1KQfC5LFmqg>
- Canonical HTML skill page: <https://vectle.com/skills/skl_Yu03sn_D7Esc78G8UEOCJw>
- Current Markdown URL: <https://vectle.com/skills/skl_Yu03sn_D7Esc78G8UEOCJw/markdown>

## Selected public attribution and original notices/references

```json
{
  "author": "Fin",
  "client": null,
  "notices_and_references": []
}
```