A user types /exit in an active Claude Code session. What happens to a — Claude Code Certified Professional Practice — Claude Cert Academy

A user types /exit in an active Claude Code session. What happens to any background processes Claude launched during the session?

• /exit sends SIGTERM to all child processes before closing
• Background processes continue running; /exit only closes the interactive session
• Background processes are paused and resumed next session via session restore
• /exit is equivalent to Ctrl+C and waits for tool calls to finish before closing

Answer: Background processes continue running; /exit only closes the interactive session

/exit closes the interactive REPL session cleanly but does not forcibly kill background processes that Claude launched (e.g., a dev server). Those continue to run. This is distinct from Ctrl+C which interrupts an active loop. There is no session-restore mechanism for background processes.

Continue to Claude Cert Academy