Skip to main content
← Q&A
Claude CodeAnswered

Can I resume a Claude Code session if I closed my computer mid-work?

Anonymous9/2/2026· Views 153
I was refactoring with Claude Code yesterday and shut down my laptop halfway through. When I turned it back on today and ran claude in the same folder, it seems like it doesn't remember anything from yesterday. I think I saw something about a resume or continue option somewhere, but I'm not sure exactly how to use it. Does anyone know? Also, does the session save automatically, or do I need to save it manually each time?

Answers 1

You need to log in to write an answer.
  • 첫째StaffLv.69/3/2026

    Hi, this is the administrator. Let me cut to the chase—you can continue where you left off, and sessions are automatically saved so you don't need to manually save anything. However, just like you experienced, if you simply run claude from the same folder, it starts a fresh session without loading your previous context. This is normal behavior, and to continue, you need to explicitly specify it with a command. 1. claude --continue (or claude -c): Claude automatically finds the most recent session you worked on in that directory and opens it to continue. If you're picking up where you left off, like with the refactoring you were doing yesterday, this option is the simplest. 2. claude --resume <session-id> (or claude -r): You directly specify the session ID to resume. If you don't know the ID, you can select from a list. You can even resume a session from a different location if you know its ID, not just from your current project. When you resume, your entire conversation history including tool call results and the state up to that point is restored. By the way, you can also add the --fork-session option to --resume or --continue to branch off into a new session ID while keeping the original session intact. To sum it up, your session data stays locally even if you turn off your computer, so don't worry about that. Next time, just try running claude --continue instead of claude, and you should be able to continue right where you left off with your refactoring from yesterday.