rulesync/Q/Which providers support global mode rules in rulesync?
Properties
- logseq-entity
- Logseq/Entity/Question
Which providers support global mode rules in rulesync?
AI Answer
- Answer/Official from rulesync global-mode docs
Short answer
Setup
- 1. Create a dedicated directory (e.g.
~/.aiglobal) - 2. Initialize rulesync in it
- 3. Edit
~/.aiglobal/rulesync.jsonc— in global mode onlyglobal,features,delete, andverboseare honoured; other keys are ignored.featuresaccepts"rules"and"commands". - 4. Edit
~/.aiglobal/.rulesync/rules/overview.md— only a singleroot: truefile per target is supported in global mode. - 5. Generate
- 1. Create a dedicated directory (e.g.
Which providers support global rules (from source)
- The authoritative list is
toolRuleFactoriesinrules-processor.ts, each entry withmeta.supportsGlobal. supportsGlobal: true—amp,antigravity-cli,antigravity-ide,augmentcode,claudecode,claudecode-legacy,cline,codexcli,copilot,copilotcli,deepagents,factorydroid,geminicli,goose,junie,kilo,opencode,pi,qwencode,rovodev,takt,vibe,devin,zed(24 total)supportsGlobal: false—agentsmd,antigravity,augmentcode-legacy,cursor,kiro,kiro-cli,kiro-ide,replit,roo,warp- The docs list only Claude Code, Copilot, and OpenCode — the source covers more. The filtered list is derived at runtime via
rulesProcessorToolTargetsGlobal.
- The authoritative list is
How global mode changes output paths
- When
global=true,getOutputRootsInLightOfGlobal()setsoutputRootto~(home directory). For Claude Code specifically,ClaudecodeRule.getSettablePaths({ global: true })emits to~/.claude/CLAUDE.md.
- When
Commands: Claude Code only