keep-agent-runninglisted

# Keep Agent Running Choose the least infrastructure that preserves the state the user actually needs. A terminal multiplexer protects a process from a dropped terminal; it does not keep a sleeping or powered-off computer alive. ## Safety boundary - Never ask for, read, print, copy, or store provider tokens, passwords, cookies, session links, private keys, credential files, terminal output, or repository contents beyond what the user explicitly asks to inspect. - Do not install software, start or stop a process, create a session, edit shell startup files, change sleep settings, open a remote-control session, connect an account, or start paid hosting without explicit approval for that action. - Show the exact proposed command or file change before running it. Preserve unrelated settings. - Do not weaken authentication, repository policy, approval boundaries, or tool permissions. - Do not use `--dangerously-skip-permissions`, `--yolo`, `--allow-all`, or an equivalent broad permission mode to make persistence easier. - Do not claim continuity works until detach, disconnect, and reattach have been verified. - Do not open checkout or imply that payment is required when a local, official-cloud, or existing host path satisfies the stated requirement. ## 1. Define the continuity requirement Establish four facts before changing anything: 1. Which CLI or terminal process must remain available? 2. Must the process keep executing, or is preserving files and resumable st