Skip to main content

multicc-sync

Two Claude accounts on one Mac, one session list. Sign out of the Claude desktop app and into another account and every Claude Code session disappears from the sidebar. Nothing was deleted: transcripts live in ~/.claude/projects and are shared, but the app keeps a separate list of sessions per account. mccsync makes both accounts list the same sessions, and keeps them in step afterwards: renames, archives and deletions made in one account carry over to the other.

It never touches transcripts, never reads tokens, and makes no network calls. Every write is preceded by a backup.

Install

uv tool install multicc-sync

Python 3.11 or newer. For the MCP server as well, install multicc-sync[mcp].

Use

Quit the Claude app, then:

mccsync

That is the whole update. The first run takes the union of both accounts; later runs carry across whatever changed on either side since the previous run, and say so entry by entry.

mccsync -n                  # show the plan, write nothing
mccsync list                # every account and what it lists
mccsync find "case study"   # locate a session in any account, with its transcript path
mccsync adopt               # list terminal-only sessions in the app (experimental)
mccsync restore             # put back the last backup

mccsync --help lists the rest, including --keep-deleted and --accounts A,B for machines with more than two accounts.

For agents, mccsync-mcp is a stdio MCP server with four tools: find_sessions, list_accounts, sync_sessions and terminal_only_sessions. Register it in Claude Code with claude mcp add multicc-sync -- mccsync-mcp. The repository carries a matching skill in skills/session-sync.

The app's session index is not a documented interface. This tool was written against Claude desktop 1.49585.0 on macOS and checks the directory layout before every run; if the app changes it, mccsync stops rather than guesses. Windows and Linux paths are present but untested.

MIT license.

Metadata

Release files for multicc-sync 1.0.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for multicc-sync 1.0.1
File Size Uploaded Provenance
multicc_sync-1.0.1.tar.gz 19.1 kB With provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for multicc-sync 1.0.1
File Interpreter ABI Platform
multicc_sync-1.0.1-py3-none-any.whl Python 3 none any Details

Total release size: 38.5 kB

Release files / multicc_sync-1.0.1.tar.gz

Download URL multicc_sync-1.0.1.tar.gz
Size 19.1 kB
Tags Source
SHA-256 checksum
How to use checksums
9c711a52ae1083d8fea368485897fcde3da19878feb07a26630bef22acc5db96
BLAKE2b-256 checksum
How to use checksums
c9d85065a1af45703dc921c4a96e49cb3982a6e0129bbf878a19351a0a02345a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 10, 2026.

Transparency log

Release files / multicc_sync-1.0.1-py3-none-any.whl

Download URL multicc_sync-1.0.1-py3-none-any.whl
Size 19.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
9d55f1387e4b8a8b3447ba26b6e5094fda26b25662c6343fed0da1e283c47c9d
BLAKE2b-256 checksum
How to use checksums
30deddceeedcfc3e1ec34b6290140204b4d5f92cacd87df963eac62c635aaa99
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 10, 2026.

Transparency log

Security for multicc-sync 1.0.1

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for multicc_sync-1.0.1.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 10, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

1.0.1 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page