Claude Sessions, Offline and Online: Keep Working Even If You Lose Your Laptop
Set up Claude so your work lives in two places at once: locally on your machine and in the cloud. Pick up the same project from your phone, a borrowed laptop, or a fresh install, with nothing lost.
The fear nobody plans for
Your laptop has everything. The project, the half-finished build, the conversation with Claude where you finally got the layout right. Then the laptop is gone: stolen at a conference, dead on the floor, left in a taxi. And suddenly the work is gone with it.
Most designers run Claude in exactly one place, on one machine, with the work living only on that disk. That is a single point of failure. The fix is to set things up so your work lives in two places at once, local and cloud, and you can pick it up from either.
The goal is not to choose between local and cloud. It is to have both, so losing one never means losing the work.
What you need
All free to start.
On your machine, plus access to Claude in a browser.
The bridge that lets cloud sessions reach your work.
Already on most Macs. The thing that snapshots and syncs your files.
Optional, but it is what turns a stolen-laptop panic into a shrug.
The two kinds of session
Local sessions
A local session runs Claude Code on your own computer, in the terminal, the desktop app, or your IDE. It works directly on the files on your disk. It is fast, it is private, and it is where most of your real building happens.
Its weakness is that it is tied to that one machine. The conversation and the uncommitted changes live there and nowhere else.
Cloud sessions
A cloud session runs in Anthropic’s infrastructure, not on your machine. You reach it from a browser or your phone. Instead of your local disk, it works on a copy of your project pulled from GitHub. You can start one from any device, anywhere, signed into your account.
Its weakness is that it only sees what you have pushed to GitHub. Whatever is sitting uncommitted on your laptop is invisible to it.
Local sessions see your disk. Cloud sessions see your GitHub. The thing that connects the two worlds is the habit of committing and pushing your work.
Git is the bridge (and it is simpler than it sounds)
You do not need to learn Git deeply. You need to understand one thing: Git takes snapshots of your project and can copy those snapshots to GitHub, where the cloud can reach them.
- Commit means “save a snapshot of the work right now.”
- Push means “send that snapshot up to GitHub.”
- Once it is on GitHub, any cloud session, on any device, can pull it down and keep working.
The work stops being trapped on your laptop the moment it is pushed. That is the whole trick. Everything else in this guide is just making that habit reliable.
Claude Code handles most of this for you. You can literally tell it “commit this and push to GitHub” and it will. The desktop app shows you commit indicators and diffs without you running a single command.
The setup: do this once, before you need it
Step 1: Put every real project in a Git repo on GitHub
When you start a project worth keeping, ask Claude Code to initialize Git and create a GitHub repository for it. Private is fine. The point is that the project now has a home that is not your laptop.
Step 2: Build the push habit
At the end of any meaningful work session, commit and push. You can ask Claude to do it: “commit what we did and push to GitHub.” Make it the last thing you do before you close the lid, the same way you would save a Figma file. If it is pushed, it is safe.
Step 3: Confirm you can reach it from the cloud
Open Claude in a browser. Start a cloud session pointed at your repo. Confirm it can see your latest work. Do this once while everything is fine, so you are not learning it for the first time in a crisis.
Step 4: Install Claude on your phone
Sign in on the mobile app. Now “I lost my laptop” becomes “I will start a cloud session from my phone on the train home.” The work is wherever you can sign in.
The conference save
Your laptop is stolen on day two of a conference. Because you pushed your work the night before, you open Claude on your phone, start a cloud session against your GitHub repo, and review the build over coffee. That evening you borrow a laptop, sign in, pull the repo, and keep going. You lost a laptop. You did not lose a single hour of work.
Working offline (the genuinely no-internet case)
Claude itself needs the internet, because the model lives in the cloud. But losing connection does not mean losing your ability to work.
- Your files and git history are fully local. You can read, edit, reorganize, and commit with no connection at all. When you reconnect, you push.
- Keep a small local model for grunt work. A model like Qwen running through Ollama sits entirely on your machine. It will not match Claude’s quality, but for renaming, reformatting, simple lookups, and rough drafts it works on a plane with the wifi off.
- Queue the Claude work. Note the things that need Claude’s quality, keep moving on everything that does not, and run the queue the moment you are back online.
Offline is not “no work.” It is “no Claude, yet.” Keep committing locally and keep a local model for the small stuff, and the only thing you are actually waiting on is the heavy reasoning.
Where each session type wins
- Deep building, fast iteration, private files: local session on your machine.
- Continuity, any device, a fallback when one machine is gone: cloud session against GitHub.
- Long unattended jobs that should run whether or not your laptop is open: a scheduled cloud routine, which runs remotely on its own.
- No internet: local files plus a local model, syncing back to Claude when you reconnect.
You are not picking one. You are making sure all of them are available before the day you need them.
Make it real tonight
Set up two-place continuity for one real project
-
Get the project onto GitHub
Open a project in Claude Code. Tell it to initialize Git if needed, create a private GitHub repository, commit the current state, and push. Do not do this by hand. Let Claude run it and confirm the push succeeded.
- The repository exists on GitHub and shows your latest files
- There are no uncommitted changes left behind on your disk
- You know the repository name and can find it again
-
Reach the same work from the cloud
Open Claude in a browser. Start a cloud session pointed at the repo you just pushed. Ask it to summarize the project so you can confirm it really sees your latest work, not an old version.
- The cloud session lists files and changes that match what you just pushed
- You understand that anything not pushed would have been missing here
- You could repeat this from a device that is not your main laptop
-
Rehearse the recovery
Sign into Claude on your phone. Open the same repo in a cloud session. You do not have to build anything. You just need to prove to yourself that if your laptop vanished right now, your work would still be one sign-in away.
- You reached your project from a second device with nothing copied across manually
- You have a clear last step in your routine: commit and push before closing the laptop
- The stolen-laptop scenario now feels like an inconvenience, not a disaster
What you learned
The bottom line
Working in one place on one machine feels fine right up until the machine is gone. Set things up so your work lives locally and in the cloud at the same time, with Git as the bridge between them, and the question “what if I lose my laptop” stops being scary. The answer becomes: I sign in somewhere else and keep going.
Done with this guide?
Mark it complete to track it on your dashboard.