Configure once. Sync every AI coding assistant.
Keep AGENTS.md, skills, commands and MCP servers synchronized across Claude, Copilot, Cursor, Gemini, Codex, OpenCode, and more.
npx @dallay/agentsync initWorks with the tools you already use
Why AgentSync?
Single Source of Truth
Maintain one AGENTS.md and sync it to Claude, Copilot, Gemini, and more via symlinks.
Native Symlinks
Uses symbolic links instead of copies. Change a file once, and every assistant sees it immediately.
Works Across Assistants
Claude, Copilot, Cursor, Gemini, Codex, OpenCode, and 25+ more — one config covers your whole toolchain.
MCP Integration
Define MCP servers once in TOML and sync them across all supported agent environments.
Skills
Install and manage reusable skills (from skills.sh or local archives) under .agents/skills/.
Gitignore Management
Start with the default managed .gitignore workflow, or opt out intentionally when your team commits managed destinations.
Cross-Platform
Written in Rust for maximum speed and portability. Works on macOS, Linux, and Windows.
How AgentSync works
Define
Keep instructions, skills, and MCP configuration in
.agents/— the single source of truth..agents/AGENTS.mdApply
Run one command. AgentSync materializes native symlinks — no copies, no drift.
$ agentsync apply ✔ Linked: CLAUDE.md -> .agents/AGENTS.mdSynced
Every assistant reads the same files. Verify the state anytime.
✔ OK: CLAUDE.md -> .agents/AGENTS.md Status: All good
Quick Start
Section titled “Quick Start”Get started in under a minute — no signup, no SaaS, just the CLI:
$ npx @dallay/agentsync init
✔ Created: .agents/agentsync.toml
✔ Created: .agents/AGENTS.md
✨ Initialization complete!
$ npx @dallay/agentsync apply
✔ Linked: CLAUDE.md -> .agents/AGENTS.md
✔ Sync complete
$ npx @dallay/agentsync status
✔ OK: CLAUDE.md -> .agents/AGENTS.md
Status: All goodFull reference lives in the Getting Started guide, including one-off runs, binaries, and source builds.
This documentation is the authoritative project reference.
Canonical Source: All agent instructions and skills are maintained in
.agents/AGENTS.md. This is the single source of truth—they get synced everywhere!
If you are deciding how your team should handle .gitignore, start with the Gitignore Team Workflows guide. It explains the default managed mode, the committed-destination opt-out mode, and when --no-gitignore is appropriate.
If you use AgentSync from Windows, the Windows Symlink Setup guide covers native prerequisites, when WSL is the lower-friction option, and how to verify symlink health after apply.
