Codepit Back to codepit.app
GUIDES

The same Claude Code chat on two computers

Claude Code saves each chat as a file on the computer that ran it, so your other computer does not know about it. There are ways around that, and they differ in what comes along: the chat, or the chat and your code.

With Claude Code alone

  • Steer it from afar. Run /remote-control in a session, and a browser on your other computer can follow it and write to it at claude.ai/code. The chat stays on the first computer, which has to stay on with Claude Code running. It needs a Claude plan, not an API key.
  • Copy the file. Chats are kept in ~/.claude/projects/<project>/<session-id>.jsonl. Copy one over and open it with claude --resume <path-to-the-file>. Your unfinished code does not come along, so you carry that over yourself. The docs warn that the format of these files can change between versions, so keep both computers on the same one.

In Codepit

  • One home for each chat. Every chat lives on one computer and says which. On the other one it is a window: live while that computer is on, its last copy to read while it sleeps.
  • Move it with your code. Move to sends a chat over with your unfinished code, and Take over here brings it to you. It travels through a private repo on your own GitHub, and only when you turn that on.
  • Watch it live. Allow your other computer once in Settings › Computers, and its chats show in your chat tree with what each one is doing. Open one to watch it and write to it. This goes through codepit.app, sealed with keys only your computers have, so the server in between cannot read it.
  • Run a sub-chat over there. A sub-chat can run on your other computer with your code as it is, unsaved files too, in a copy of its own. Bring its changes here puts what it made into Review.

It works between Windows and macOS. The privacy page says exactly what goes where.

More guides

What this page says about Claude Code was checked against its documentation on 3 November 2026.