Session/agent management should be opt-in: plain CLI sessions get entangled with background-job topology

A claude session on my machine ended up running as a managed "background job" with a self-re-waking loop attached — behaviour I never knowingly opted into. Getting back to an ordinary terminal session required: discovering the loop existed, disarming it, killing the managed process, and --resume-ing the transcript in the foreground CLI.

Claude used to be a program I run; it now behaves like a resident process-management system. Requests:

1. Sessions must be independent by default — no shared agent/job topology unless explicitly requested per session.
2. Any mechanism that re-wakes or prolongs a session (loops, schedules, background jobs) must be visibly opt-in, visibly listed, and trivially killable from the session itself.
3. A one-command "make this a plain foreground session again" escape hatch.

Filed without transcript deliberately: my sessions contain proprietary work, which is precisely why opaque session management is unacceptable.