The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Claude Code “project memory” can mean three different things: persistent instruction files, Claude Code’s auto memory, or session transcripts. Treat them as separate items when moving to another computer or setup; there is no documented single command that transfers every artifact from 15 months of use.
- Instructions: project, user, or organization guidance in files such as
CLAUDE.mdandAGENTS.md. - Auto memory: Claude’s locally stored notes and patterns for a repository.
- Transcripts: local plain-text session history, which may matter if you need to resume or consult old conversations.
- Other agent configuration: settings you may be able to bring in through Claude Code’s supported import workflow.
Before copying anything, identify the source and destination setup
Record the Claude Code version, source and destination operating systems, provider or account setup, and any storage overrides. In particular, check whether CLAUDE_CONFIG_DIR or the autoMemoryDirectory setting changes the default locations. Repository naming and project configuration can also affect where state is stored. Anthropic documents these options, but not a universal filesystem recipe for every machine and account combination. Anthropic’s memory documentation describes the relevant settings and behavior.
![Claude AI for Beginners Bible: [5 in 1] The Ultimate Guide to Automate Your Work, Save Hours Every Week, and Use AI for Real-World Results](https://m.media-amazon.com/images/I/415+fSJacsL._SL160_.jpg)
Make a list of what you actually need on the destination: reusable project guidance, personal auto-memory notes, historical transcripts, or configuration from another coding agent. Moving only one category will not preserve the others.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Move instruction files deliberately
Instruction files are the right place for guidance that should be shared or reliably reapplied, such as project conventions, build commands, or coding standards. Put team guidance in the repository and version-control it where appropriate; user-level or organization-level instructions have different scopes.
#1 Best Overall
Claude Code can read AGENTS.md in place of CLAUDE.md. Discovery and precedence depend on the working-directory path: a higher-level CLAUDE.md can affect whether an AGENTS.md file is read by default. Do not blindly duplicate both files, since duplicate or conflicting instructions can produce confusing behavior. Verify which files the destination setup recognizes. Anthropic documents instruction-file discovery and precedence.
Preserve auto memory separately
Claude Code auto memory is distinct from instruction files. It stores learnings such as corrections and preferences, with a MEMORY.md index and topic-specific files that Claude can read when relevant. By default, each repository has an auto-memory directory under ~/.claude/projects/<project>/memory/. Worktrees and subdirectories within that repository share the memory, but it is not automatically shared between machines or cloud environments.
Use /memory to inspect, open, edit, or delete memory files and to check the configured location. If you choose to preserve these files manually, copy the repository’s memory directory to the corresponding destination location, accounting for any configured alternative directory or project-path differences. The documentation describes the default storage model, not a guarantee that a copied directory will map identically in every customized setup. Anthropic says auto memory loads its first 200 lines or 25 KB at session start; longer topic files may be read when needed. See the memory documentation.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesUse import for supported configuration from other coding agents
If you are moving configuration from another supported coding agent, Claude Code’s claude import command or the /import workflow can bring in supported settings, including instruction files, MCP servers, commands, subagents, and skills. The CLI reference documents --dry-run and --yes options; it says the command requires Claude Code v2.1.213 or later. Check the installed version and review the import preview before applying changes. Consult the CLI reference.
This is a cross-agent configuration import, not a documented migration of Claude Code’s own historical state. Do not assume it copies auto-memory files or session transcripts.
Handle transcripts as historical records
Claude Code stores local session transcripts as plain text under ~/.claude/projects/. They are not the same as concise memory notes or team instructions: transcripts preserve conversation history for reference or resumption. If transcripts matter to your migration, locate and back up the relevant project records separately, including any configured storage locations.
Anthropic documents a 30-day default for local transcript caching for commercial users, configurable with cleanupPeriodDays. That retention statement is specific to commercial users and local caching; it should not be generalized to every account type or treated as a guarantee that a transcript from 15 months ago still exists. Check what is present on the source machine before relying on it. Anthropic explains data usage and retention.
Verify the destination in a fresh session
- Open the intended repository on the destination machine and start a new Claude Code session.
- Run
/memoryto review the memory files and location available to that session. - Run
/contextto see which instruction files loaded. - Check for representative project-specific guidance and auto-memory content that you intended to preserve.
- If transcript preservation was part of the goal, confirm the relevant transcript is present and try resuming it using the available session workflow.
A successful fresh-session check shows that the expected context is available; it does not prove that every past conversation or local artifact was copied.
Quick Recap
Best Value
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
