Press m for madewithlove A madewithlove developer documented splitting a single ~/.claude folder into three separate Claude Code accounts — personal at ~/.claude, madewithlove at ~/.claude-mwl, and a client seat at ~/.claude-client — by pointing the CLAUDE_CONFIG_DIR environment variable at each folder, an approach Anthropic recommends in its official docs and GitHub issue responses. Before moving anything, the developer deleted all but 8 of more than 70 sessions, cutting ~/.claude from roughly 300 MB to 155 MB. The write-up flags four pitfalls: macOS Keychain entries hash the exact config folder path (so ~/.claude-mwl and ~/.claude-mwl/ are different logins), the default account's .claude.json lives outside ~/.claude at ~/.claude.json, plugin files installed_plugins.json and known_marketplaces.json store absolute paths that need a sed fix, and users must log out before logging in again. These days, typing claude asks me a question first: personal, madewithlove or client? I press m , and I'm on the madewithlove account. Until recently, there was no question to answer. For months, everything lived in one ~/.claude folder, on the madewithlove account. It held madewithlove work, work for two clients only one of them provides a Claude account and, for some reason, my fitness notes. Then things changed. One of those clients gave me my own seat in their Claude organisation, and I wanted to use my personal account in the terminal too, not just on claude.ai, for anything outside work. Three accounts, one Mac, and one folder that had no idea any of this was happening. Others have been here before. Earlier in the year, Mike wrote Running multiple Claude accounts without logging out https://madewithlove.com/blog/running-multiple-claude-accounts-without-logging-out/ . This starts with a clean slate. Mine didn't. My ~/.claude contained more than 70 sessions and almost 300 MB of history, memories, and plugins from work for three companies. This post is about getting all of that out of one folder. Why no tool Claude Code already supports multiple accounts. Point CLAUDE CONFIG DIR at a folder, and that folder gets its own login, settings, history and plugins. It's in the official docs, and Anthropic answered GitHub issues about this by recommending an alias per config folder. In Mike's article, Jean-Claude builds on the same idea, but it also shares skills, agents and plugins between accounts. I didn't want that. I wanted everything to stay separate, including the time-tracking skill that belongs to madewithlove. So I ended up with: | Account | Folder | Used for | |---|---|---| | personal | ~/.claude | Everything outside work | | madewithlove | ~/.claude-mwl | madewithlove, the other client | | client | ~/.claude-client | The client that gave me a seat | Moving out of ~/.claude I wanted plain claude to open my personal account by default, which meant moving madewithlove out, along with all its history, and letting personal start fresh in ~/.claude . Simple in theory. Of course, there were a few things to watch out for. Before moving anything, I deleted everything except the 8 sessions I still needed, so there was less to carry over. ~/.claude went from ~300 MB to 155 MB. Spring cleaning, in November. 1. The Keychain entry depends on the exact folder path. Claude Code stores each login in the macOS Keychain. The default account uses an entry called Claude Code-credentials . For any other config folder, it uses the same name with a hash derived from the folder path. For example, ~/.claude-mwl gets Claude Code-credentials-99898ee2 . That means ~/.claude-mwl and ~/.claude-mwl/ are two different logins. So, keep your paths consistent everywhere, or enjoy logging in twice. 2. The default account cheats. Each account also has a .claude.json file. It keeps track of things like which account you're logged in to, whether onboarding is complete, and, for each project folder, whether you trust it and which MCP servers it uses. When CLAUDE CONFIG DIR is set, this file lives inside that config folder. Without it, the file lives at ~/.claude.json , right next to ~/.claude . In other words, moving ~/.claude alone wouldn't have been enough. Half of its configuration would have stayed behind. The madewithlove account would have started like a fresh install with every folder untrusted, while personal started with madewithlove's leftovers. 3. Plugins remember their old locations. Two plugin files, plugins/installed plugins.json and plugins/known marketplaces.json , contain absolute paths. After moving the folder, those paths still pointed to ~/.claude , so madewithlove would have tried to load its plugins from my personal folder, where they obviously weren't. A quick sed fixed that. 4. Log out before logging in again. After moving everything, the default Keychain entry still contained the madewithlove login. Remember that the default entry doesn't have a hash and doesn't follow the config folder when you move it. A plain claude would have happily started a madewithlove session from what was supposed to be my personal folder. So, I ran claude auth logout and signed in again with my personal account. 5. Sessions can be moved between accounts. A Claude session consists of a few things: a transcript projects/