Supported Tools and Features
Rulesync supports both generation and import for All of the major AI coding tools:
| Tool | --targets | rules | ignore | mcp | commands | subagents | skills | hooks | permissions |
|---|---|---|---|---|---|---|---|---|---|
| AGENTS.md | agentsmd | ✅ | 🎮 | 🎮 | 🎮 | ||||
| AgentsSkills | agentsskills | ✅ 🌏 | |||||||
| Amp | amp | ✅ 🌏 | ✅ 🌏 | ✅ 🌏 | ✅ 🌏 | ||||
| Claude Code | claudecode | ✅ 🌏 | ✅ | ✅ 🌏 | ✅ 🌏 | ✅ 🌏 | ✅ 🌏 | ✅ 🌏 | ✅ 🌏 |
| Codex CLI | codexcli | ✅ 🌏 | ✅ 🌏 🔧 | 🌏 | ✅ 🌏 | ✅ 🌏 | ✅ 🌏 | ✅ 🌏 | |
| GitHub Copilot | copilot | ✅ 🌏 | ✅ | ✅ | ✅ 🌏 | ✅ 🌏 | ✅ | ||
| GitHub Copilot CLI | copilotcli | ✅ 🌏 | ✅ 🌏 | ✅ 🌏 | ✅ 🌏 | ✅ 🌏 | |||
| Goose | goose | ✅ 🌏 | ✅ | ✅ 🌏 | ✅ 🌏 | ✅ 🌏 | ✅ | ✅ 🌏 | 🌏 |
| Hermes Agent | hermesagent | ✅ | 🌏 | 🌏 | ✅ 🌏 | 🌏 | 🌏 | 🌏 | |
| Grok CLI | grokcli | ✅ 🌏 | ✅ 🌏 | ✅ 🌏 | ✅ 🌏 | 🌏 | |||
| Cursor | cursor | ✅ | ✅ | ✅ 🌏 | ✅ 🌏 | ✅ 🌏 | ✅ 🌏 | ✅ 🌏 | ✅ 🌏 |
| deepagents-cli | deepagents | ✅ 🌏 | ✅ 🌏 | ✅ 🌏 | ✅ 🌏 | 🌏 | |||
| Factory Droid | factorydroid | ✅ 🌏 | ✅ 🌏 | ✅ 🌏 | ✅ 🌏 | ✅ 🌏 | ✅ 🌏 | ✅ 🌏 | |
| OpenCode | opencode | ✅ 🌏 | ✅ 🌏 🔧 | ✅ 🌏 | ✅ 🌏 | ✅ 🌏 | ✅ 🌏 | ✅ 🌏 | |
| Cline | cline | ✅ 🌏 | ✅ | 🌏 | ✅ 🌏 | ✅ 🌏 | ✅ 🌏 | ✅ | |
| Kilo Code | kilo | ✅ 🌏 | ✅ | ✅ 🌏 | ✅ 🌏 | ✅ 🌏 | ✅ 🌏 | ✅ 🌏 | ✅ 🌏 |
| Roo Code | roo | ✅ 🌏 | ✅ | ✅ | ✅ | ✅ | ✅ 🌏 | ||
| Rovodev (Atlassian) | rovodev | ✅ 🌏 | 🌏 | ✅ 🌏 | ✅ 🌏 | ✅ 🌏 | 🌏 | ||
| Takt | takt | ✅ 🌏 | ✅ 🌏 | ✅ 🌏 | ✅ 🌏 | ✅ 🌏 | ✅ 🌏 | ||
| Vibe Code | vibe | ✅ 🌏 | ✅ | ✅ 🌏 | ✅ 🌏 | ✅ 🌏 | ✅ 🌏 | ✅ 🌏 | |
| Qwen Code | qwencode | ✅ 🌏 | ✅ | ✅ 🌏 🔧 | ✅ 🌏 | ✅ 🌏 | ✅ 🌏 | ✅ 🌏 | ✅ 🌏 |
| Reasonix | reasonix | ✅ 🌏 | ✅ 🌏 | ✅ 🌏 | ✅ 🌏 | ||||
| Kiro ⚠️ | kiro | ✅ 🌏 | ✅ | ✅ 🌏 | ✅ | ✅ | ✅ | ✅ | ✅ |
| Kiro CLI | kiro-cli | ✅ 🌏 | ✅ | ✅ 🌏 | ✅ 🌏 | ✅ 🌏 | ✅ 🌏 | ✅ | ✅ |
| Kiro IDE | kiro-ide | ✅ 🌏 | ✅ | ✅ 🌏 | ✅ | ✅ 🌏 | ✅ 🌏 | ✅ 🌏 | ✅ |
| Google Antigravity IDE | antigravity-ide | ✅ 🌏 | ✅ 🌏 🔧 | ✅ 🌏 | ✅ 🌏 | ✅ 🌏 | ✅ | ||
| Google Antigravity CLI | antigravity-cli | ✅ 🌏 | ✅ | ✅ 🌏 🔧 | ✅ 🌏 | ✅ 🌏 | ✅ 🌏 | 🌏 | |
| JetBrains AI Assistant | aiassistant | ✅ | ✅ | ✅ | |||||
| JetBrains Junie | junie | ✅ 🌏 | ✅ | ✅ 🌏 | ✅ 🌏 | ✅ 🌏 | ✅ 🌏 | 🌏 | ✅ 🌏 |
| AugmentCode | augmentcode | ✅ 🌏 | ✅ | 🌏 | ✅ 🌏 | ✅ 🌏 | ✅ 🌏 | ✅ 🌏 | ✅ 🌏 |
| Devin Desktop | devin | ✅ 🌏 | ✅ | ✅ 🌏 🔧 | ✅ 🌏 | ✅ 🌏 | ✅ 🌏 | ✅ 🌏 | ✅ 🌏 |
| Warp | warp | ✅ | ✅ | ✅ 🌏 | ✅ 🌏 | 🌏 | |||
| Replit | replit | ✅ | ✅ 🌏 | ||||||
| Pi Coding Agent | pi | ✅ 🌏 | ✅ 🌏 | ✅ 🌏 | |||||
| Zed | zed | ✅ 🌏 | ✅ | ✅ 🌏 | ✅ 🌏 | ✅ 🌏 |
- ✅: Supports project mode
- 🌏: Supports global mode
- 🎮: Supports simulated commands/subagents/skills (Project mode only)
- 🔧: Supports MCP tool config (
enabledTools/disabledTools) - ⚠️: Deprecated — still supported, but see the note below
Deprecation notes
- Google Antigravity (
antigravity-ide/antigravity-cli) — Antigravity 2.0 splits into two products: the desktopantigravity-ideand theantigravity-cli(agy). As of Antigravity 2.0 the IDE reads its global MCP config and skills from the shared~/.gemini/config/tree —~/.gemini/config/mcp_config.jsonand~/.gemini/config/skills/, matching the current MCP and Skills docs. Theantigravity-cliglobal MCP config also lives in the shared~/.gemini/config/mcp_config.json, while the CLI keeps its own global skills tree at~/.gemini/antigravity-cli/skills/. Both targets also intentionally share the global rule file~/.gemini/GEMINI.mdand the global hooks file~/.gemini/config/hooks.json— enabling both targets in--globalmode writes those shared files once. For project-scope rules, bothantigravity-ideandantigravity-cliemit the root rule as a plain cross-toolAGENTS.mdat the project root (the Gemini-lineage discovery order isAGENTS.md,CONTEXT.md,GEMINI.md; the IDE has readAGENTS.mdsince v1.20.3) and non-root rules under.agents/rules/(the IDE adds trigger frontmatter to non-root rules; the CLI keeps them as plain markdown). For commands (workflows), both targets share the project.agents/workflows/directory (invoked as/workflow-name); in--globalmode the IDE writes to~/.gemini/antigravity/global_workflows/while the CLI keeps its own~/.gemini/antigravity-cli/global_workflows/tree (mirroring the CLI's global skills tree). - Kiro (
kiro) — Kiro ships as two products with diverging config formats: the Kiro IDE reads Markdown subagents (.kiro/agents/*.md) and structured JSON hooks (.kiro/hooks/*.json, format{ "version": "v1", "hooks": [ ... ] }), while the Kiro CLI reads JSON agent-config subagents (.kiro/agents/*.json) and agent hooks in.kiro/agents/default.json. A single target cannot emit both faithfully, sokirois split intokiro-cliandkiro-ide. The legacykirotarget is kept as a deprecated alias (its current mixed output is unchanged for backward compatibility). Shared surfaces (steering rules withinclusion,.kiro/settings/mcp.json,.kiro/prompts/commands,.kiro/skills/,.kiroignore, permissions) are identical between the two; they differ in subagents (.mdvs.json) and hooks. Kiro IDE hooks are emitted as a single.kiro/hooks/rulesync.json(whosehooksarray holds every generated hook) in both project (.kiro/hooks/) and global (~/.kiro/hooks/) scope, mapping canonical lifecycle events to the IDE's PascalCase triggers (SessionStart,UserPromptSubmit,PreToolUse,PostToolUse,Stop) and supporting bothagent(prompt) andcommandactions; the Kiro CLI continues to emit agent hooks in.kiro/agents/default.json. Global skills (~/.kiro/skills/) and global Kiro IDE subagents (~/.kiro/agents/) are also supported, as are global Kiro CLI commands (~/.kiro/prompts/) and subagents (~/.kiro/agents/).
