What Happens to Your Data and Sessions?

Your files live on the computer’s disk; your running agents and commands live in processes. An action can preserve the disk while still ending the processes.

Compare the effects

Action	Files and local memory	Running work
Close browser / disconnect	Remain on disk	Can continue in the managed agent Herdr session.
Restart	Remain on disk	Interrupted; processes must start again.
Stop	Remain while the computer is retained	Stops with the computer.
Upgrade plan	Intended to preserve the disk	Can be interrupted by the required restart.
Restore backup	Replaced by the backup’s point-in-time state	Not restored as live processes.
Reset computer	Removed during Ubuntu reinstallation	Ends.
Delete computer	Removed with the computer	Ends.

The admin web terminal is an ordinary shell, so it does not have the managed agent session’s disconnect behavior.

Saved conversation versus running session

An AI tool may save a conversation that you can resume after its process ends. This is different from reconnecting to a still-running process, and it depends on the provider tool.

Shared memory can preserve selected context, but it does not contain your complete repository or restore a process.

Before a disruptive action

Save your edits, record progress, and copy important data outside the computer. Check that you have included uncommitted files, databases, configuration, and memory exports where needed.

A Git push protects only the content actually committed and pushed; it does not automatically include ignored or local-only data.

Read backup limits, backup restore, and computer reset.