Jean Claude

JEAN-CLAUDE

A companion for managing Claude Code profiles and syncing configuration across machines

Why?

You've spent hours crafting the perfect CLAUDE.md. Your hooks are *chef's kiss*. Your settings are dialed in just right.

Then you sit down at another machine and... nothing. Back to square one. Or you need separate configs for your work and personal Claude accounts, but maintaining them is a pain.

Jean-Claude fixes that. It manages multiple Claude Code profiles and optionally syncs everything across machines via Git. Works on macOS, Linux, and Windows.

Quick Start

Profiles

Profiles let you run multiple Claude Code configurations side by side — one for your Teams account at work, another for your personal Max subscription, and so on.

How profiles work

Your main ~/.claude/ stays the source of truth. Profile directories (~/.claude-/) are lightweight — they link back to your shared files:

Windows: Profile directories use hardlinks (files) and junctions (directories). No Developer Mode or admin privileges required.

During profile creation, you're prompted whether to share CLAUDE.md and statusline.sh (statusline.ps1 on Windows) or keep them independent per profile. You can also use flags:

Change a setting or add a hook in your main config, and all profiles see it immediately.

Profiles work independently of syncing — you can use them without setting up Git.

Syncing

Syncing is optional and uses Git to keep your default config and profiles in sync across machines.

What gets synced?

- CLAUDE.md — Your custom instructions
- settings.json — Your preferences
- hooks/ — Your automation scripts
- skills/ — Your custom skills
- agents/ — Your custom agents
- keybindings.json — Your keyboard shortcuts
- statusline.sh / statusline.ps1 — Your statusline…