# Press m for madewithlove

> Source: <https://madewithlove.com/blog/press-m-for-madewithlove/>
> Published: 2026-11-16 09:55:00+00:00

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/<folder>/<id>.jsonl`), a subagent folder (next to the transcript), and checkpoints (`file-history/<id>/`). I copied the client's sessions into its own config folder, resumed them there and checked that they still remembered where I'd left off. Prompt history (the up-arrow kind) is one JSON line per prompt with the project folder in it, so `jq` split it by folder too. Folder trust and MCP approvals don't move, so expect a few "do you trust this folder?" questions.

**6. I want the same settings everywhere.** My `settings.json` contains my general Claude Code preferences. I don't want separate settings for every client or project, so I keep that file in my dotfiles. My usual Stow run links it into `~/.claude`. I added two more commands to link it into the other accounts:

```
stow -d ~/dotfiles/claude -t ~/.claude-mwl --no-folding .claude
stow -d ~/dotfiles/claude -t ~/.claude-client --no-folding .claude
```

There's also a Herdr integration in that settings file. It's a hook that runs whenever a session starts inside a Herdr pane, and tells Herdr which session is running there, so Herdr can resume it after a restart. The hook calls `~/.claude/hooks/herdr-agent-state.sh` using a fixed path. That means all three accounts can use the same script. Moving `~/.claude` also moved that script, though, so I had to put it back before starting any sessions. Otherwise, every session would have opened with a hook error.

One more small detail: Herdr's integration commands respect `CLAUDE_CONFIG_DIR`. So running `herdr integration status` from inside a madewithlove session checks `~/.claude-mwl`, not the default folder. That's why I run them from a plain terminal, where `CLAUDE_CONFIG_DIR` isn't set and they work on `~/.claude`.

## Which Claude are you?

Mike's approach gives every account its own command: `claude`, `claude-mwl`, `claude-client`. That works until you type `claude` in the other client's folder, out of habit, and start a work session using your personal account.

So now, `claude` asks first:

```
Account: [p]ersonal · [m]adewithlove · [c]lient (Enter = p)
```

One keypress, no need to confirm with Enter. Here's the whole thing from my `~/.zshrc`:

``` php
claude() {
  local dir d key def
  local -a hits
  if [[ ($1 == --resume || $1 == -r) && -n $2 ]]; then
    for d in $HOME/.claude-client $HOME/.claude-mwl $HOME/.claude; do
      hits=($d/projects/*/$2.jsonl(N))
      if (( $#hits )); then dir=$d; break; fi
    done
  fi
  [[ -z $dir && -n $CLAUDE_CONFIG_DIR && ! ( -t 0 && -t 1 ) ]] && dir=$CLAUDE_CONFIG_DIR
  if [[ -z $dir ]]; then
    [[ $PWD/ == $HOME/code/client/* ]] && def=c || def=p
    if [[ -t 0 && -t 1 ]]; then
      read -k 1 "key?Account: [p]ersonal · [m]adewithlove · [c]lient (Enter = $def) "
      [[ $key == $'\n' ]] && key=$def || print
    else
      key=$def
    fi
    case $key in
      p) dir=$HOME/.claude ;;
      m) dir=$HOME/.claude-mwl ;;
      c) dir=$HOME/.claude-client ;;
      *) print -u2 "Invalid key: '${(V)key}'"; return 1 ;;
    esac
  fi
  if [[ $dir == $HOME/.claude ]]; then
    env -u CLAUDE_CONFIG_DIR claude "$@"
  else
    CLAUDE_CONFIG_DIR=$dir command claude "$@"
  fi
}
alias claude-mwl='CLAUDE_CONFIG_DIR=$HOME/.claude-mwl command claude'
alias claude-client='CLAUDE_CONFIG_DIR=$HOME/.claude-client command claude'
```

In plain words, it follows three simple rules:

- **Resuming a session never asks.**`claude --resume <id>` looks for the session in every account and uses the one that owns it. This is particularly useful with Herdr. When Herdr restarts, it restores each pane by running exactly that command. It only knows the session ID, not which account owns it. The function figures that out, so every pane comes back using the correct account.
- **Everything else asks.** That covers new sessions,`-c` ,`auth` and pretty much every other subcommand. Pressing Enter chooses a sensible default: the client when I'm inside`~/code/client` , personal everywhere else.
- **No terminal, no questions.** When a script or another program runs`claude` , it doesn't wait for a keypress that will never come. It keeps the account already set in`CLAUDE_CONFIG_DIR` , or falls back to the default.

I also kept `claude-mwl` and `claude-client` as aliases. Sometimes you know exactly which account you want and don't need another question.

One caveat: it only accepts lowercase. Press `P` and you get "Invalid key: 'P'", which is its way of saying NO SHOUTING. If that happens to you a lot, maybe it's time to give your Caps Lock key a job.

## Things that surprised me

- **Claude copies your shell functions.** Claude Code takes a snapshot of your shell environment, including its functions, and uses that for its own commands. At first, my function ignored any account that was already set, so a madewithlove session running`claude plugin install` would have installed the plugin on my personal account. The`CLAUDE_CONFIG_DIR` check midway through the function fixes that.
- **Shared settings mean Claude can change your dotfiles.** Linking one`settings.json` into three folders means any account can change it. On a new account's first start, I picked a theme, and Claude Code saved`"theme": "auto"` into that file, which lives in my dotfiles repo. So a choice made in one account quietly applies to all three, and shows up in`git status` as a change I don't remember making.
- **Artifacts belong to an organisation.** I had published a page from a client session back when it was still running under my madewithlove account. After the move, Claude told me it could no longer follow comments on it, because "this Artifact is in another of your organisations". It suggested`/login` to fix that, but that would have logged the client folder into madewithlove. No thanks, so I'm republishing it from the client account.
- **Connectors are per account.** Harvest, Slack, Notion and other connectors belong to your claude.ai account, not your machine. So the client's Claude doesn't see madewithlove's connectors. That's exactly how I wanted things to work.
- [**Claude Desktop**](https://madewithlove.com/blog/the-claude-desktop-app-just-killed-fifteen-years-of-waiting-for-an-android-emulator-to-boot/) **is a separate story.** It reads the same settings files as the CLI, from`~/.claude` by default, but my function only runs in a terminal, so Desktop never sees it.

## Claude moved itself

I did the whole thing with Claude, in one session, with one rule: read-only. It researched the options, inspected my setup and wrote a [step-by-step checklist](https://madewithlove.com/blog/beyond-prompting-read-verify-implement-learn/). I then closed the session and ran everything myself, one block at a time. Once the migration was done, I brought it back with `claude --resume`. The function found it in its new home, and it audited its own move.

During the audit, it spotted a couple of settings that Claude Code and Herdr had quietly written into my dotfiles. It also caught the shell-function issue mentioned above in one last review, just before I committed everything.

Not bad for a tool that had just been evicted.

## The short version

- One `CLAUDE_CONFIG_DIR` per account. Write the paths the same way every time.
- Moving the default account means `~/.claude.json` too, plus the plugin paths and a logout.
- Let `claude --resume` find the right account, and let plain`claude` ask.

Now every session starts with the right account. Press `m` for madewithlove, `c` for the client, `p` for personal. Just not `P`.
