Does Claude Code sync history between computers?

No. Sessions are saved locally in ~/.claude/projects on each machine. You can move one by copying its transcript file and resuming it by path.

Can I continue a Claude Code session from my phone?

Yes, with Remote Control: start it with claude --remote-control or /remote-control, then open claude.ai/code or the Claude app. The session keeps running on your computer.

Does the Claude desktop app show my CLI sessions?

Each keeps its own session list. Inside the desktop app, /resume lists CLI sessions, and /desktop in the CLI moves a session into the app.

How do I move a Claude Code session to another machine?

Copy ~/.claude/projects/ / .jsonl to the other machine, then run claude --resume /path/to/ .jsonl from the project folder there.

Using Claude Code sessions across devices (laptop, desktop app, phone, web)

What moves between machines and what doesn't. Remote Control, cloud sessions, teleport, the desktop app, and how to move a session to another computer by hand.

Claude Code keeps your sessions on the machine where they ran. There's no automatic sync between computers, and the CLI, desktop app and web each keep their own lists. Here's what does move, and how.

Phone or browser: Remote Control

Remote Control lets you drive a session running on your computer from claude.ai/code or the Claude mobile app. The session keeps running locally; the phone is a window into it.

claude --remote-control

Or run /remote-control (or /rc) inside an existing session. It works on Pro, Max, Team and Enterprise plans, not with an API key, and on Team and Enterprise an owner has to turn it on.

Cloud sessions and teleport

claude --cloud "task" starts a session that runs in Anthropic's cloud. To pull a cloud session into your terminal:

claude --teleport <session-id>

This needs a clean git state and the same account. The handoff is one way: the teleported copy lives locally from then on, and claude --resume doesn't list cloud sessions.

The desktop app

The desktop app and the CLI each keep their own session list. To move between them:

/desktop (or /app) in the CLI hands the current session to the desktop app, on macOS or x64 Windows with a subscription.
Inside the desktop app, /resume can list CLI sessions.

Full two-way sync is an open feature request, anthropics/claude-code#28791.

Another computer: move the file

Every session is one file. To continue one on a different machine:

On the first machine, find it among recent sessions: find ~/.claude/projects -name '*.jsonl' -mtime -2
Copy that .jsonl file to the other machine, any folder.
On the other machine, from the project's folder, resume it by path:

claude --resume /path/to/<session-id>.jsonl

Don't copy the same session into two project folders on one machine. When the same ID exists twice, claude --resume <id> refuses to guess and reports it as not found.

Some people share the whole ~/.claude folder between machines by pointing CLAUDE_CONFIG_DIR at a synced folder. It can work, but two machines writing to the same files at once is risky, and each app still shows only its own sessions.

What stays on one machine regardless

Your prompt history (~/.claude/history.jsonl), memory, and settings are per machine unless you move them too. If you work across two computers, the simplest habit is to finish a thread on the machine where it started, or end the session with a short summary ("what's done, what's left") that you can paste into a new session anywhere.

Shabash builds that summary for every thread automatically, from your sessions and commits, so picking work back up doesn't depend on which machine you're on.