Feature request: Sync ~/.claude/ setup (skills, plugins, MCP, statusline) across machines via Anthropic account

Resolved 💬 2 comments Opened Jun 8, 2026 by lkzppm Closed Jul 15, 2026

Problem

Claude Code is an essential part of my daily development workflow. The friction I keep hitting: when I switch machines, I lose my local Claude Code setup. Everything under ~/.claude/skills/, plugins, MCP server config, status-line, and other customizations — is per-machine, and there's no built-in way to carry it with me.

Today there is no first-class way to sync these settings through an Anthropic account, so each new machine starts from scratch.

What I want

A built-in way to sync the ~/.claude/ environment (skills, plugins, MCP servers, statusline, settings) across machines — ideally tied to the Anthropic account, so signing in on a new machine restores my setup.

Workaround I built

To cope, I built a small repo ("bebop") that clones and restores my ~/.claude/ environment on any machine. It works, but it's a manual workaround for something that feels like it should be native.

Secondary friction: skill naming for primitive commands

The plugin/skill naming pattern /<plugin_name>:<skill_name> works well for structured extensions, but feels awkward for the more primitive, command-like skills I use a lot — e.g. /commit and /merge. A lighter-weight path for simple, command-style skills (without forcing a plugin namespace) would be a nice improvement.

Why it matters

For people who use Claude Code heavily and move between machines, portable and consistent setup makes a real difference to productivity. A native sync story would remove a recurring papercut.

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗