Description
The /exit command sometimes does not close the terminal application. I have to press Ctrl+C to actually exit. I waited several seconds, sometimes over 10 seconds, before resorting to force-killing it.
Environment
- CommandCode version:
0.30.1
- OS: Windows (win32-x64)
- Node.js: v22.17.0
- Installation: npm install -g command-code
Steps to Reproduce
- Start
command-code
- Use it normally (chat, code generation, etc.)
- Type
/exit and press Enter
- Expected: Application closes and returns to the shell prompt
- Actual: Application hangs. The terminal stays open and I have to press
Ctrl+C to regain control
Notes
- I did not explicitly configure any MCP servers — this is a plain install with default config
- The hang is not consistent — sometimes
/exit works, sometimes it doesn't
- Waited up to 10+ seconds before force-killing with Ctrl+C
Possibly Related
Description
The
/exitcommand sometimes does not close the terminal application. I have to pressCtrl+Cto actually exit. I waited several seconds, sometimes over 10 seconds, before resorting to force-killing it.Environment
0.30.1Steps to Reproduce
command-code/exitand press EnterCtrl+Cto regain controlNotes
/exitworks, sometimes it doesn'tPossibly Related
/exithangs when MCP servers are connected (processes not cleaned up). Could be the same root cause if Command Code spawns default MCP processes, or a separate issue.