Getting Started

Claude Remote Config is a Claude Code plugin plus a small CLI. Inside Claude Code, the plugin appears as remote config. It syncs a shared .claude/ tree from a git repository into generated, gitignored Claude Code paths in each project.

claude plugin marketplace add mcmanussliam/claude-remote-config
claude plugin install remote-config@mcmanussliam

claude --plugin-dir /path/to/claude-remote-config

/remote-config setup --remote git@example.com:your-org/claude-config.git

Project Manifest

The project manifest selects the remote, optional ref, generated output types, and tags:

{
  "remote": "git@example.com:your-org/claude-config.git",
  "ref": "v1.0.0",
  "output": {
    "rules": true,
    "commands": false,
    "skills": false,
    "settingsLocal": false,
    "hooksLocal": false
  },
  "tags": []
}

remote is required. ref is optional; tags or commit SHAs are best for reproducible rollouts.

output is optional. Defaults are:

{
  "rules": true,
  "commands": false,
  "skills": false,
  "settingsLocal": false,
  "hooksLocal": false
}

If tags is empty, every remote directory that passes its file requirements is included. If tags contains values, tagged directories must match at least one project tag. Untagged directories are always included when their file requirements pass.

Generated Paths

Generated paths are owned by this plugin and should normally stay gitignored:

.claude/rules/remote/
.claude/commands/remote/
.claude/skills/remote-*/
.claude/settings.local.json
.claude/hooks.local.json
.claude-remote-config/cache/

The .gitignore block also reserves .claude/mcp.local.json and .claude/agents.local/ for generated local Claude Code config. The current implementation does not write those paths.