[Bug] Terminal Hangs When Using claude --continue Command

Found 3 possible duplicate issues:

1. https://github.com/anthropics/claude-code/issues/6939
2. https://github.com/anthropics/claude-code/issues/6844
3. https://github.com/anthropics/claude-code/issues/6878

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

A workaround that works for me is starting claude code without --continue and then using /resume

Same for me, version 1.0.105

A workaround that works for me is starting claude code without --continue and then using /resume

Are you sure this works?

> A workaround that works for me is starting claude code without --continue and then using /resume Are you sure this works?

100%

I didn't realise Claude had a slash command for resume.

--continue or --resume both freeze the terminal for me

Press ENTER after you do the command and the Claude Code UI loads. Then, the terminal should be responsive. Hopefully that will work for you.

Press ENTER after you do the command and the Claude Code UI loads. Then, the terminal should be responsive. Hopefully that will work for you.

it works, yes indeed need to press ENTER.
haha

It doesn't work. Claude UI does loads up but everything is frozen. No keypress works.

A workaround that works for me is starting claude code without --continue and then using /resume

This worked for me after trying rebooting and everything else ... started claude normally and used /resume and i was able to start the session again. else when i used --continue, though i can see the history, unable to select any of the options... very strange

Thank you @UsernameZer0 ! I was pulling my hair out trying to figure out why the terminal was just locking up all the time. Pressing ENTER immediately after the UI loads is the only thing that allows me to use Claude Code. Wow! That is not a great bug...

Never had that problem with version 1, but cannot resume (-r) nor continue (-c) sessions with all 2.0.* versions :( Today at: 2.0.13 (Claude Code)

Never had that problem with version 1, but cannot resume (-r) nor continue (-c) sessions with all 2.0.* versions :( Today at: 2.0.13 (Claude Code)

2.0 is working better actually mall you need to do is press 'Enter' once. And it works.

> Never had that problem with version 1, but cannot resume (-r) nor continue (-c) sessions with all 2.0.* versions :( Today at: 2.0.13 (Claude Code) 2.0 is working better actually mall you need to do is press 'Enter' once. And it works.

At I thought it maybe was an issue with vim-mode. But I just replicated it on a fresh convo in readline:
Windows 11 - Windows Terminal - PowerShell v7
Claude Code v2.0.13
Sonnet 4.5 · Claude Max

mkdir claudebugtest && cd claudebugtest
claude "Just trying to do some testing on a bug I've found in your client."
Press 1 to proceed and trust.
<Claude protests vehemently that it's an Anthropic AI Agent and has no "client" that could have bugs in the traditional sense> (very touchy, Claude. Meant no offence.)
/exit
claude --continue
Shows UI with everyting looking ready to continue the convo, but pressing Enter doesn't work. Double Ctrl-C doesn't kill. Hard freeze after which I have to close the Terminal and start again.

Just to be thorough, I ran the same test in conhost.exe. No change.

ETA: The claude process under Windows Terminal Host in TaskManager shows no activity. So it's not chewing on anything. Just stuck.

also seeing this error. replicated from clean claude install / no mcps on Windows 11/Claude. a quick hit of enter does bring it back after claude --contine which otherwise totally freezes. tried it through multiple terminals both using terminal and direct cmd.exe.

I just ran into this issue as well. No matter using --continue ---resume or after starting Claude then using /continue or /resume; it would hang. I found this issue arose because my previous chat session did not exit cleanly. I'm using PuTTy to connect to my VM and lost connection while in a session. I started a new conversation, had some interactions, closed the Claude session with /exit, then exited my terminal session. Upon logging back in, the --resume and /resume works just fine (note that the session I was hoping to get back to was lost. Again thinking because it was a lost connection). So it looks like the current issue might be related to how Claude handles an improperly closed session.

This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.

This issue has been automatically closed due to 60 days of inactivity. If you're still experiencing this issue, please open a new issue with updated information.

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.