Global Sync - Clarify Intended Behavior

[sheldonhull]

Context

Upgraded from 3.x to latest. I use rulesync primarily for global sync: distributing rules, skills, and an agents file from a single source repo to multiple tool locations.

Setup

Source repo contains:

• Global rules (some with root: true and target-specific tweaks, e.g. targets: [claudecode] + root: true alongside targets: [opencode] + root: true)
• Global skills (replacing commands, since Claude merged that feature)
• Global agents file

I tested two paths:

Set the JSON config to default to global.
Run generate per target individually.

Observed behavior (different from 3.x)

Global rules no longer copy to ~/.claude/ or $HOME/.github-instructions.
root: true combined with per-target targets no longer produces target-specific rule variants.

Expected behavior

Run a single sync command against my source repo and distribute rules + skills to every configured destination. Equivalent to a task sync wrapper that calls rulesync and outputs everything where it belongs.

Question

The config table documents many global options, but the README still states "Only Claude Code is supported for global mode commands." Which is accurate?

Specifically:

• Does global sync intend to support writing rules to all target tool locations (Claude, OpenCode, etc.)?
• Is root: true + per-target targets a supported pattern for target-specific global rules, as this worked in earlier versions and not certain if was unintentional or intended behavior.

[tmak]

This is related to #1240

[cm-dyoshikawa]

@sheldonhull Thank you for your feedback.

Only Claude Code is supported for global mode commands.

is incorrect. Multiple agent global configs should be supported.