Does Claude Sync Across Devices? Chats, Projects, and Files

Claude chats and Projects are tied to your account and are accessible from any device where you sign in to Claude.ai. Open a conversation on your phone, continue it on your laptop — the history is there. What does not follow you are local files, Claude Code project configurations, and MCP connections set up on a specific machine.

For work that moves across devices or across AI apps, a shared restart note outside any single chat means you pick up without re-explaining the context. fenbs keeps that note alongside the task, accessible from any device and readable by any connected AI assistant.

What follows your Claude account across devices

Sign in to Claude.ai on a new device and you see your complete conversation history, all your Projects with their files and instructions, your saved memories (if enabled on your plan), and your account preferences. None of this is device-specific.

The mobile app and the web interface share the same account data. A Project you set up in the browser is available in the phone app. A chat you started on your phone appears in the browser. The sync is account-level, not device-level.

Chat history and Projects

Chat history is stored in your account and syncs automatically. There is no manual step. Conversations you started weeks ago on one device are available on every other device where you are signed in.

Projects work the same way. The project name, instructions, and uploaded files are stored in your account. A project you configured on your desktop with a system prompt and reference documents is available from your phone. The context follows the account, not the device.

For anything that is not syncing as expected, see Claude projects not syncing across devices for specific troubleshooting steps.

What does not sync

Claude Code stores its context in local files — CLAUDE.md, AGENTS.md, and any project-level configuration files — that live in the repository on the machine you are working on. These do not sync through your Claude account. They follow the repository, which you manage through version control.

MCP server connections — the links to outside tools including fenbs — are set up per machine and per client application. A connection you approved on your laptop is not automatically available on your desktop or phone. Each new device or client needs its own authorization.

Browser-specific settings and data stored only in local storage are also machine-specific. These include some extension configurations and cached preferences that are not part of your account. API keys and developer credentials are stored locally wherever you placed them and do not transfer.

Setting up on a new device

To use Claude on a new device, sign in to Claude.ai. Your account data — chats, Projects, memories — loads automatically. For Claude Code, clone or pull your repository to the new machine and run the project setup steps there. The code and configuration files come through version control.

MCP connections need to be re-approved on each new device. Go to the Integration settings in the tool you want to connect — such as Claude Code or Claude Desktop — and follow the setup steps for each service. Authorizations are per device for security reasons: granting access on one machine does not extend that access to every machine you own. Keep an eye on which connections need renewal — tokens expire, and a connection that worked last month may need re-authorization.

Handing off work across devices

Because chats sync, you can start work on one device and continue on another — but the chat history alone does not tell the next session what state the work is in. A chat may contain hundreds of messages, and finding the current task status from that history takes time.

A short written restart note — what is approved, what is next, what is waiting — is faster than re-reading the chat. This is what Where we left off in fenbs captures: the current state in one or two sentences, readable from any device in seconds.

When Claude Code is involved

Claude Code works in a local project directory. Moving that work to a different machine means moving the repository — via version control — and re-running the setup steps on the new machine. The Claude account sync does not apply to Claude Code's local context files. See what is Claude Code for how its configuration works.

How to do this with fenbs

1. Create a free account and add the project you are working on across devices.
2. Connect Claude on each device you use over MCP from Integrations. Each connection is approved separately per device and client.
3. Ask the assistant to read the project context — including Rules and Where we left off — at the start of each session, wherever it happens.
4. Before you stop on one device, ask the assistant to save progress in fenbs. When you pick up on a different device, the saved state is the starting point.