What survives what
The product’s core promise as one table: across quitting Farhelm, restarting a host’s supervisor, and rebooting a host, what happens to the session, its terminal contents, and the agent’s conversation. This is the canonical statement of those guarantees; other pages link here rather than restating them. Getting a stopped agent back is in Stop, restart, and resume. It will also cover container session lifecycle. Suspend preserves processes and memory. A host reboot stops the container and keeps its files. Farhelm attempts to start it again when its host is connected. The interrupted agent waits for you to choose Restart. And the exceptions to quitting Farhelm: once Farhelm’s connection to a sandbox session ends, Tensorlake’s 30-minute idle timeout freezes its processes until the sandbox is resumed; and on Tensorlake’s Usage Credits plan, a sandbox host suspends after 24 hours without a connection.