/exit command outputs 'Catch you later\!' but process does not terminate

Summary

The /exit slash command is acknowledged (prints "Catch you later\!") but the Claude Code process does not shut down. The session remains alive and responsive to further input after an arbitrary delay.

Reproduction

1. Run a session with multiple tool calls (this instance had ~50+ tool invocations including Bash, Read, Edit, Write, Grep, Glob, and Task agent launches).
2. Issue /exit.
3. Observe "Catch you later\!" output appears immediately.
4. Process does not terminate. After some seconds, Claude Code remains interactive and continues to respond to input as if /exit was never issued.

Environment

• Platform: Linux 6.5.0-17-generic
• Working directory: git repo with ~200+ untracked files in status

What the debug logs show

• Session debug files exist in ~/.claude/debug/ keyed by UUID.
• The 128-byte stub files contain sparse single-line debug output (e.g. Failed to check enabledPlatforms: TypeError: undefined is not an object (evaluating 'l7.join')).
• The large file for this session is the conversation transcript, not process lifecycle events.
• No shutdown/exit/terminate events are logged anywhere accessible.

Expected behaviour

Process should exit after printing "Catch you later\!".

Actual behaviour

Process remains alive and interactive. The exit command was fully processed at the command-parsing level but the process shutdown did not follow through.

Notes

• The /exit output confirms the command was recognized — the hang is in the shutdown path after the command handler returns, not in command recognition.
• Unclear whether this is a cleanup/hook timeout (e.g. a pre-exit hook or background agent blocking), or a signal-handling issue.
• The session had background agents and multiple subprocesses spawned via the Task tool, which may be relevant if shutdown waits on those.