Author your AI-assistant config once, sync it to every tool.

You write this once

.agent-config/
├── AGENTS.md                 # project-wide guidelines
├── agents/<name>.md          # one subagent per file
├── skills/<name>/SKILL.md    # one skill per folder
├── rules/<name>.md           # one rule per file
└── mcp-servers/<name>.json   # one MCP server per file

…and Cyncia generates

• Tool-specific file paths and layouts
• Tool-specific file formats
• Tool-specific frontmatter keys
• MCP server config in each tool's documented shape

For the full reference (formats, frontmatter, MCP secret tokens, per-tool field map, edge cases), see the cyncia.md reference in the repo.

Frontmatter and secret tokens

• Generic rule keys (applies-to, always-apply, description) → globs / alwaysApply (Cursor) and applyTo (Copilot).
• Generic skill key applies-to → paths for Claude; stripped elsewhere.
• Generic agent key mcp-servers → mcpServers: [...] (Claude), tools: ["<server>/*", ...] (Copilot); stripped for Cursor and Junie.
• MCP secret tokens (${secret:NAME}, ${secret:NAME?optional}) → ${env:NAME} (Cursor), ${NAME} / ${NAME:-} (Claude), ${input:NAME} + inputs[] entry (VS Code), and Codex environment forwarding / bearer-token env vars where Codex documents those fields.

Rules on Codex

Codex’s native .rules files are Starlark command-approval policies, not Markdown instruction files. By default Cyncia merges generic rules/*.md into root AGENTS.override.md, which Codex prefers over AGENTS.md in the same directory. Set codex-rules-mode: ignore to skip Markdown rule output for Codex, and keep Codex command policy under .codex/rules/*.rules by hand.

When rule bodies are merged into CLAUDE.md, .junie/AGENTS.md, or AGENTS.override.md, Cyncia shifts imported ATX headings so the highest rule heading sits under the generated rule-file section. Standalone rule files keep their original heading levels.

Dependencies

• Bash 4+ (macOS/Linux/WSL/Git Bash)
• PowerShell 5.1+ or PowerShell 7+ (Windows / cross-platform)
• jq 1.6+ (required only when the MCP sync step runs)
• Git (not required by the installer or by sync time)
• Standard POSIX utilities (sed, awk, grep, find, cp, mv)

Common installer flags

Ask your assistant

• "sync agent config"
• "regenerate Cursor rules"
• "clean sync for Copilot only"
• "sync delegate-to-aside for Cursor and Claude"

The skill detects the platform, locates the installed scripts, infers input/output roots, tools, item filters, and clean mode, then reports what was written.

Run scripts directly

# Sync using the default tool list from .cyncia/cyncia.conf
.cyncia/scripts/sync-all.sh -i .agent-config -o .

# Only some tools
.cyncia/scripts/sync-all.sh -i .agent-config -o . --tools cursor,claude

# Only some items (by name); --clean removes stale generated files
.cyncia/scripts/sync-all.sh -i .agent-config -o . --items delegate-to-aside --clean

# Windows / PowerShell
.\.cyncia\scripts\sync-all.ps1 -InputRoot .agent-config -OutputRoot $PWD