You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Conversation Resume Failure: Persistent Hang on claude --resume Command #922
Bug Description
I had a long session that hanged suddenly after hours of work and when I tried to use cluade --resume I got the command hanging indefinitely - tried multiple times. Also tried claude --continue, but got "No conversation found to continue".
Can you confirm that you were in the same directory where you did the work? Currently the resume and continue commands are connected to the project directory (which is admittedly a little surprising/confusing)
Can you confirm that you were in the same directory where you did the work? Currently the resume and continue commands are connected to the project directory (which is admittedly a little surprising/confusing)
I think I wasn't in the same directory yeah. I hadn't explicitly changed the directory, but I remember I had told given claude the path of a different (related to the one I was working on) and told it to inspect something there to get contextual understanding of the task at hand since it's related to interfacing with the service in the other dir, so probably claude was on the other directory when the issue happened. If the resume/continue commands are coupled with the project directory, I believe it should also be considered a bug.
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.
Activity
wolffiex commentedon May 2, 2025
Can you confirm that you were in the same directory where you did the work? Currently the resume and continue commands are connected to the project directory (which is admittedly a little surprising/confusing)
wolffiex commentedon May 2, 2025
The hang was fixed in 0.2.95
marwan-tanager commentedon May 3, 2025
I think I wasn't in the same directory yeah. I hadn't explicitly changed the directory, but I remember I had told given claude the path of a different (related to the one I was working on) and told it to inspect something there to get contextual understanding of the task at hand since it's related to interfacing with the service in the other dir, so probably claude was on the other directory when the issue happened. If the resume/continue commands are coupled with the project directory, I believe it should also be considered a bug.
github-actions commentedon Aug 10, 2025
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.