To continue Claude Code work on another computer, distinguish moving the project from resuming the old conversation. A repository clone can bring tracked code and instructions; it does not automatically bring machine settings, credentials, or locally saved session history. On a remote Mac, verify each separately before continuing work.
Use a small authorized project for the first migration. Keep the original copy available until the remote copy has passed the checks you actually rely on. This guide proposes a migration procedure; it does not claim that Agent.Space automatically transfers your laptop's files, credentials, or existing conversations.
Decide whether to move the work or reach the existing session
If you only want to use a different screen, you may not need to migrate anything. An eligible Remote Control setup can keep execution on the original computer. Follow the Remote Control guide for that case. The steps below are for moving execution to another computer.
Anthropic's memory documentation distinguishes project instructions from other memory and configuration. Check which files your own workflow depends on instead of treating one copied folder as a complete setup.
Record the starting state before moving files
Identify the project directory, current branch, last saved revision, and unfinished work. If the project uses Git, its version-history tool, check for both modified files and new files that have not been added. A fresh clone will not include changes that exist only on your laptop.
In the project directory, these read-only commands help record the baseline:
The first reports changed and untracked files, the second the current branch, and the third the current commit. They do not back up files. Save changes using your team's normal branch and backup process. Do not make a broad commit of everything just to transfer it: local configuration can contain credentials or unrelated material.
Also record the command you normally use to check the project and whether it currently passes. If the local project already fails a test, that is useful evidence when comparing the remote environment. Otherwise an old failure can look like a migration problem.
Transfer the project, not your entire user account
Use the repository's approved access method to obtain a remote copy, or transfer an authorized project folder through your chosen secure file-transfer method. Verify that the intended revision and necessary unfinished work arrived.
Keep secrets separate. Do not copy an entire home directory, browser profile, or saved login folder as a shortcut. Arrange repository and package-registry access explicitly on the destination. A development configuration file may be necessary; its secret values should follow your organization's credential process.
If you are renting a Dedicated Mac, complete the machine acceptance checks before introducing private files. Confirm the assigned machine and access controls rather than relying on a familiar desktop wallpaper or folder name.
Recreate the dependencies on the destination
Follow the project's documented runtime versions and installation instructions. A dependency folder built on another operating system or architecture may not be usable on the Mac. Prefer the project's normal installation process over copying generated folders without checking them.
Verify the working directory, required runtime, and permitted configuration. Run an existing non-destructive project check before asking Claude to change code. If it fails, record the error and resolve the environment issue first.
For an application with a visual interface, also establish how you will open its preview. A development server running on the remote machine does not automatically appear at the same address on your laptop. Use an approved preview or desktop-access method; do not expose the server publicly just to make the migration easier.
Confirm the account independently of the files
An installed Claude Code client and a copied project do not establish a valid sign-in. Follow the official authentication guidance for the approved route on this machine. Confirm who pays before making a model request; do not paste credentials into the project brief.
For Agent.Space, confirm which computer and agent route you selected. The Claude Code product guide explains that workflow. Rental cost and model usage are separate checks, and relocating files does not change provider account eligibility.
Will the old conversation appear on the new Mac?
Not just because you cloned the repository. The official session guide describes CLI conversations as locally saved transcripts. Resuming a transcript restores conversation state; it does not move project files or restart an interrupted command on the new computer.
If exact history is essential, preserve the original transcript and consult the official resume instructions for your client and version. Check paths, required tools, and the resulting permissions before continuing. This guide does not provide an automatic transcript-transfer tool or promise that every client shares one history.
If you mainly need to keep working on the project, a reviewed handoff is often the simpler starting point. Keep the original history available for reference rather than pretending that a summary contains every earlier detail.
Move the task context explicitly
The previous conversation may not follow the project into a new interface. Rather than assuming it did, prepare a short handoff with the goal, completed work, constraints, and next verification step.
For example, adapt this request to your project:
Read the repository instructions and explain the current project structure. Confirm the working directory and the files relevant to the sign-in form. Do not edit, install, or deploy. Identify the existing check we should run before making a change, and report any missing prerequisites.
Then provide a brief account of earlier decisions and outstanding work. Include file paths and revision references where useful, but never passwords or private access tokens. Have Claude explain its understanding before giving it a change task.
The first-project guide provides a reusable pattern for defining a small task and inspecting its result.
Switch over only after a visible check
Choose one small change on an isolated branch or project copy. Inspect the difference, run the relevant check, and confirm the result is saved in your approved repository or backup system.
Avoid editing the same branch on both machines during this first test. If migration fails, you should be able to return to the preserved local copy without reconstructing missing work. Once the remote setup is accepted, decide which copy owns active work and how results return to the team.
Before ending a rental, export the files and results you need and follow the service's access-removal process. A rented development machine is not your only backup.
Make the first remote task deliberately small
The first success is not a large autonomous rewrite. It is the correct project, a known account, a working check, and a saved result you can inspect. If you still need the execution machine, review the Dedicated Mac configuration against those requirements. If you already have it, use the read-only handoff above before your first edit.