/new already released the old native session through the chat-close
release path, but two gaps let the replaced session stay alive, and the
client told the operator it could still be resumed in a terminal:
- Claude Code: ReleaseSession only closed a host this server was
attached to. A host registered for the session but not attached (a
failed reattach, or one left by an earlier server) kept running. It is
now asked to close over its socket and killed as a fallback.
- Codex: ReleaseSession only interrupted an active turn. It now also
sends thread/unsubscribe so the App Server unloads the thread; a later
prompt reloads it through the existing "thread not found" resume path.
- The /new notice now says the previous session was stopped.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A pipelines-claude-host process owns each claude -p CLI and its pipes,
spools its stream-json output with offsets and serves a private Unix
socket. The server detaches on shutdown and reattaches on start,
replaying the spool to rebuild turns, approvals, questions, background
tasks and the live model. Explicit close, idle release and CLI exit stop
the host; a crashed host falls back to --resume with a notice.