Sessions launched from the in-terminal session switcher run as background jobs; backgrounding should be an explicit toggle

I normally run multiple Claude Code sessions with one terminal window each. Today I tried the session switcher instead (left arrow, the list of sessions in the terminal) and launched a few sessions from there, planning to switch between them in a single window.

Every session started that way apparently runs as a background job. The model gets told the user may be away, that it should operate autonomously and not block on questions, and file edits get rejected until it isolates into a worktree. In my case it edited a GitHub issue and posted a comment under my account without checking with me first, because its instructions said to proceed on anything reversible. I was sitting right there the whole time, sending it messages mid-turn.

The switcher is a way to manage several sessions in one window instead of several windows. Nothing about opening a session that way means I stepped away, and I only found out about the mode change when the agent explained why it wasn't asking me anything. For interactive work this makes the switcher unusable, since the whole point of my workflow is making decisions together with the agent.

Backgrounding changes agent behavior enough that I'd expect it to be its own visible mode I toggle on and off, like plan mode, not something inferred from how the session was opened.

Possibly related: the switcher also listed sessions I had started in other terminal windows, which I didn't expect. I can file that separately if it's a different bug.

Version: 2.1.221, macOS 26.2.