Resource Recommendation: vsync - Config Sync Tool for AI Coding Tools

[2214962083]

Resource Recommendation

Name

vsync

URL

https://github.com/nicepkg/vsync

Category

Tooling 🧰 > General

Description

vsync is a CLI tool that syncs Skills, MCP servers, Agents & Commands across Claude Code, Cursor, OpenCode, and Codex.

Why it belongs here

Managing configurations across multiple AI coding tools is a nightmare:

• Different directory structures for Skills/Agents/Commands/MCP in each tool
• Different config file formats (JSON, TOML, JSONC)
• Different environment variable syntax

vsync solves this with one simple command: pick one tool as your source of truth, and all others stay perfectly in sync.

Key Features

• One Command Sync: vsync sync syncs all your configs to all target tools
• Automatic Format Conversion: JSON ↔ TOML ↔ JSONC (preserves JSONC comments!)
• Environment Variable Preservation: Converts ${VAR} ↔ ${env:VAR} ↔ {env:VAR} automatically
• Safe Mode (default): Add & update only, never deletes
• Prune Mode: Strict mirroring with deletions
• Atomic Writes: Crash-safe file operations
• Manifest Tracking: Hash-based change detection
• Multi-Language CLI: English & 中文

Installation

```bash
npx @nicepkg/vsync
```

Real-World Use Cases

1. Team Onboarding: New member joins, has Claude Code setup → vsync sync → All tools configured in seconds
2. User-Level Config Sync: Set up global personal configs once → sync across all projects
3. Tool Migration: Moving from Cursor to Claude Code? One command migrates everything

Links

• npm: @nicepkg/vsync
• Documentation: https://vsync.xiaominglab.com

---

Thank you for maintaining this awesome list! 🙏

[hesreallyhim]

thanks @2214962083 ! i just happened to be looking at this: https://github.com/vercel-labs/skills

it looks kinda similar, what do you think? i haven't done a close study but curious to know your opinion

[2214962083]

Thanks for the question @hesreallyhim!

I took a look at vercel-labs/skills - it's a great collection of skills for Claude Code, but it serves a different purpose than vsync.

Key Differences:

Feature	vsync	vercel-labs/skills
Purpose	Config synchronization across tools	Skill collection/registry
Skills	✅ Sync across tools	✅ Provides skills
MCP Servers	✅ Sync across tools	❌ Not supported
Agents	✅ Sync across tools	❌ Not supported
Commands	✅ Sync across tools	❌ Not supported
Multi-tool support	Claude Code, Cursor, OpenCode, Codex	Claude Code only
Format conversion	JSON ↔ TOML ↔ JSONC	N/A

vsync's core value:

When you use multiple AI coding tools (which many developers do), keeping their configs in sync is painful:

• Different directory structures
• Different file formats
• Different environment variable syntax (${VAR} vs ${env:VAR} vs {env:VAR})

vsync solves this by letting you maintain one source of truth (e.g., Claude Code) and sync everything to other tools with one command: vsync sync

They're complementary:

You could use vercel-labs/skills to discover great skills, then use vsync to sync them across all your AI coding tools!

Hope this clarifies the difference. Happy to answer any other questions!

[hesreallyhim]

ok so what do you mean by "tool" in this case? specifically an MCP tool? If not please clarify.

i don't mean to ask you to talk so much about another repo, but it seems to me that the capabilities are somewhat broader than you are suggesting:

https://github.com/vercel-labs/skills/blob/main/src/add.ts#L81

also you say "Claude Code only" so could you check this link?

https://github.com/vercel-labs/skills?tab=readme-ov-file#supported-agents

And could you ask the agent to take a little more time before they generate the response? 😉 just kidding!