[FEATURE] Cloud-Sync for User-Scoped Claude Code Configuration (~/.claude/)

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Summary Currently, user-level Claude Code configurations — including custom subagents (~/.claude/agents/), slash commands (~/.claude/commands/), skills (~/.claude/skills/), and memory (~/.claude/agent-memory/) — are stored locally on each machine. There is no mechanism to synchronize these configurations across multiple machines or environments tied to a user's Anthropic account.
Problem Statement
Modern developers frequently work across multiple environments: personal laptops, work machines, cloud VMs, Docker containers, and CI/CD environments. Every time a new environment is provisioned, the user must manually re-create or copy their personal Claude Code configuration. This creates friction, leads to inconsistent tooling, and makes the "user-level" scope feel less useful than it could be.
Proposed Solution
Introduce an optional cloud-sync feature for user-scoped Claude Code configuration, tied to the authenticated Anthropic account (similar to how VS Code or JetBrains sync settings via a cloud account).

Specifically:

• All files under ~/.claude/agents/, ~/.claude/commands/, ~/.claude/skills/, and ~/.claude/agent-memory/ should optionally sync to the user's Anthropic account
• Sync should trigger automatically on login (claude login) and periodically during active sessions
• A CLI flag or settings option to opt in/out: claude config set sync.user-scope true
• Conflict resolution strategy (e.g. last-write-wins or prompt on conflict)
• Local-only override still possible via a .nosync marker file per directory

Proposed Solution

Expected Behavior

1. User logs in on a new machine: claude login
2. Claude Code pulls their personal agents, commands, and skills from the cloud automatically
3. Any changes made locally are pushed on session end or on explicit claude sync
4. Works seamlessly across macOS, Linux, WSL, and cloud VMs

Why This Matters

• Reduces onboarding time on new machines from minutes to seconds
• Ensures consistent tooling across environments without dotfile workarounds
• Aligns with how developers already expect account-linked tools to behave (VS Code Settings Sync, JetBrains Sync, GitHub CLI auth)
• Increases the value of the "user scope" distinction vs. project scope — currently it feels underutilized because it doesn't actually follow the user

Alternative Solutions

Current Workaround
Manually maintaining a dotfiles repository and symlinking ~/.claude/ — functional but error-prone and not discoverable for less experienced users.
Impact
Medium effort, high value. Would significantly improve the experience for any developer working across more than one machine or provisioning cloud environments regularly.

Priority

High - Significant impact on productivity

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context