Meld

One shared Claude Code chat history across all of your accounts.

If you use Claude Code desktop with more than one account, each account keeps
its own separate session history on your Mac. Switch accounts and your recent
conversations seem to disappear. They are still on your machine — just stored
in a different account folder.

Meld fixes this. It finds every account's session folder, works out which
conversations are missing where, and copies them so every account sees the
same complete history. Everything happens locally on your Mac. Nothing is
uploaded anywhere, nothing is ever deleted (unless you opt in to delete syncing),
and every change can be undone.

Every conversation reaches every organization of every account: personal,
team, Max or any other plan, in any login. Start a chat on a team plan, hit
its limit, and carry on in your Max account.

Install

Recommended:

curl -fsSL https://meld.dpdns.org/install.sh | bash

With Homebrew:

brew install siddhjagani/tap/meld

On Windows (PowerShell, no administrator needed):

irm https://meld.dpdns.org/install.ps1 | iex

macOS (Apple Silicon and Intel) and Windows are supported.

Get started in three commands

meld doctor          # 1. confirm meld can see your session folders
meld sync --dry-run  # 2. preview exactly what would be copied
meld sync            # 3. bring every account up to date

That is the whole workflow. Run meld sync again any time; if there is
nothing to do, it says so and touches nothing.

Keep accounts in sync automatically

meld watch

Leave this running and meld will notice new conversations as they appear and
copy them across your accounts within a couple of seconds. Press Ctrl-C to
stop. Signing into a brand-new account later requires no setup — meld detects
the new account folder on its own and fills it with your existing history.

Updates and deletions follow you

New conversations are copied everywhere, and continued conversations are
updated everywhere (on by default). Only conversations are synced; per-account
files such as scheduled-tasks.json stay with their account.

Settings live in ~/.meld/config.toml (create it with meld config init):

propagate_updates = true      # continued chats are updated in every account
deleted_chats = "come_back"   # or "stay_deleted_here" / "delete_everywhere"

• Continued conversations (propagate_updates, on by default): the copy
  you actually continued replaces the older copies, so you can pick up where
  you left off after switching. Each account keeps its own account-bound
  details (that org's connectors, its own "usage limit reached" error).
  If Claude saves an old copy back over a newer one, meld restores the newer
  one instead of spreading the old one. Set it to false if you want meld to
  only ever add.
• Deleted conversations (deleted_chats):
  • "come_back" (default): a chat you delete comes back from the accounts
    that still have it. Nothing is ever deleted.
  • "stay_deleted_here": it stays deleted in the account and organization
    you deleted it in; every other account keeps it.
  • "delete_everywhere": it is deleted in every account, the same way
    Claude deletes it (a deleted_<chat> marker replaces the file).

Every copy that is replaced or deleted is backed up first; meld restore
puts it back.

Seeing synced chats without restarting Claude

Claude reads its chat list into memory when you sign in, so chats synced
while it is open don't show up by themselves. Any of these makes it reload:

• Switch account or organization in Claude. It saves, then reads the new
  account's list from disk, so with background sync on everything is
  already there.
• Close the Claude window (⌘W) and click its Dock icon. A new window
  re-reads the list and shows newly synced chats. A chat that was already
  open keeps the version Claude has in memory.
• meld sync --restart-claude quits Claude (so it saves first), syncs,
  and reopens it. This always gives you the exact latest state.

Run it in the background (macOS)

meld service install     # start background sync now and at every login
meld service status      # is it running?
meld service uninstall   # turn it off

This runs meld watch as a login item, restarts it if it stops, and logs to
~/Library/Logs/meld.log. While it runs, meld sync isn't needed (and
meld restore asks you to turn the service off first).

Check where things stand

meld status

Shows each account, how many conversations it has, whether anything is
pending, and any conflicts (see below). Add --json if you want
machine-readable output.

meld diff

Lists the exact files a sync would copy, and where they would go.

meld accounts

Meld cannot see your email address or organization name — Claude keeps those
behind an encrypted login token, and meld never touches that. Instead this
lists every account (and every organization inside it) with what's on disk:
how many conversations, when it was last active, and which projects it
worked on. Use it to tell your accounts apart, and to confirm meld found all
of them — including a single login that belongs to more than one
organization.

Undo a sync

Before meld writes anything, it saves a snapshot: of all your session
folders, or — when full sync replaces or deletes files — of exactly those
files. To go back:

meld restore              # undo the most recent change
meld restore --list       # see every snapshot
meld restore --snapshot <name>

Conversations created after the snapshot are kept. With full sync on, a
restored conversation becomes the newest version, so it spreads back to every
account, and a restored deleted conversation is un-deleted in every account.
The restore itself is backed up first, and it tells you how to undo it. You can take a
full snapshot of every account at any time with meld backup.

About conflicts

Occasionally the same conversation exists in two accounts with different
content — usually because it was continued separately in each. With
propagate_updates off, meld never guesses which version you want: both
copies stay exactly as they are, and the conflict is listed in meld status.
With it on (the default), the copy that was actually edited wins: meld remembers the version your
accounts last agreed on, so a copy that was only opened (Claude touches a chat
just by showing it) never overwrites a real edit. If two accounts were both
edited, or meld has no history for the chat yet and the modification times
tie, it stays a conflict. Likewise, a deletion never removes a copy that was
edited after the accounts last agreed; that chat is listed as a conflict. Nothing about a conflict blocks the rest
of your history from syncing.

Your safety, guaranteed by design

• Meld never deletes a file unless you set deleted_chats = "delete_everywhere". It only
  replaces a conversation with the copy you actually edited in another
  account (propagate_updates, on by default), and every replaced or deleted
  file is backed up first.
• A file that changed since meld looked at it is skipped, never clobbered.
• Every change can be undone with one command (meld restore).
• Files are written atomically, so an interruption (crash, power loss) can
  never leave a half-written conversation behind.
• Everything is local. Meld makes no network connections.

Where meld keeps its own files

Everything meld owns lives in one folder: ~/.meld (settings, its index,
and snapshots). Your conversations are never moved from their normal
location. Removing ~/.meld resets meld completely without touching any of
your chat history.

Settings (optional)

Meld works with zero configuration. If you want to change defaults — for
example, keep more snapshots — create a settings file and edit it:

meld config init     # creates ~/.meld/config.toml
meld config show     # view current settings

All commands

Uninstall

meld service uninstall     # if background sync is on
rm /usr/local/bin/meld     # or: brew uninstall meld
rm -rf ~/.meld             # optional: remove settings and snapshots

Your conversations are unaffected either way.