How to use Claude Code with multiple repositories without losing context

How to use Claude Code with multiple repositories without losing context If you work across multiple repos — a frontend, a backend, a shared library — you already know the pain: Claude Code loses track of which project you're in, forgets the conventions from the other repo, and you spend half your session re-explaining things it already knew. Here's how to fix it. The core problem: Claude Code has one context window Claude Code doesn't have persistent memory across sessions or across repositories. When you open a new project, it starts fresh. When you switch from your API repo to your frontend repo mid-session, context from the first repo doesn't automatically transfer. This becomes a real problem when: Your API and frontend share types but live in different repos You need to make coordinated changes across both repos simultaneously Your backend conventions differ from your frontend conventions You're doing a migration that touches multiple codebases Solution 1: The shared CLAUDE.md st