sync.md - Visual Studio Marketplace

Skip to content

| Marketplace

Sign in

Visual Studio Code>Other>sync.mdNew to Visual Studio Code? Get it now.

sync.md<br>sync-md

| (0) | Free<br>Keeps AI coding-agent instruction files (AGENTS.md, CLAUDE.md, .cursorrules, .github/copilot-instructions.md) in sync by using an AI model to compare their meaning, not just their text. Also includes local-only length and active-file checks. No telemetry, no bundled API keys.<br>Installation<br>Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.<br>Copy<br>Copied to clipboard

More Info

OverviewVersion HistoryQ & ARating & Review<br>sync.md

Using more than one AI coding tool? Your AGENTS.md, CLAUDE.md, and<br>.cursorrules quietly drift apart and start contradicting each other.<br>sync.md compares your AI instruction files by meaning — not text — and<br>keeps them aligned, clean, and visible across your whole workspace,<br>including nested subdirectories.

It watches AGENTS.md, CLAUDE.md, .cursorrules, and<br>.github/copilot-instructions.md. It never modifies your source<br>code — only the rule files themselves. No telemetry. No bundled cloud<br>API keys.

Demo

Screenshots

Problems panel — conflicts, missing rules, and length warnings appear<br>as normal VS Code diagnostics, grouped by file, with the sync.md source<br>label so you always know where they came from:

AI-powered meaning comparison, not text diffing — these two files say<br>the same thing in totally different languages/wording (German, emoji,<br>Japanese, Chinese vs. plain English) and sync.md correctly treats them as<br>in sync, only flagging a genuinely missing Security section:

Run "sync.md: Reconcile" from the Command Palette:

The Reconcile webview — a calm, native-feeling view of conflicts and<br>missing rules between two files, with one-click "Copy to..." actions and a<br>"Make consistent" button that applies every suggested fix at once:

After reconciling — the missing Security section is now written into<br>CLAUDE.md automatically, clearly marked so you can review exactly what<br>changed before committing:

What it does

1. Sync check — AI-powered

When two or more rule files share the same directory scope, sync.md asks<br>a language model to compare their meaning, not their text . Files<br>that say the same thing in different words are correctly treated as in<br>sync — only genuine contradictions (conflicts) or rules present in one<br>file but entirely absent from another (missing) get flagged.

Diagnostics appear inline (squiggles) and in the Problems panel, labeled<br>so you always know they came from sync.md:

Conflicts with : . (Warning)

Missing vs : . (Warning)

Because it compares meaning, the same rules written in German, Japanese,<br>emoji, or plain English are all recognized as equivalent — it only flags<br>what's genuinely different.

For each conflict, the model also recommends which version to keep<br>("Suggested: keep — "), grounded in real project<br>evidence where available — for example, an actual package.json test<br>script can settle a disagreement about which test command to run. If the<br>model can't judge confidently, no recommendation is shown and the first<br>file's wording is used as a deterministic fallback.

Run sync.md: Reconcile to open a calm, native-feeling webview<br>showing conflicts and missing rules grouped clearly, with per-item<br>Copy to… actions and a Make consistent button that applies every<br>suggested fix at once. You can override any individual item with its own<br>Use this button.

The check re-runs on save and on file open (debounced ~800ms) and caches<br>the last result per file pair — it only calls the model again when a<br>watched file's content actually changed.

Heads up: the sync check is AI-powered and needs a language model —<br>either GitHub Copilot (default) or a local model via LM Studio<br>/ Ollama. Without one, the length and active-file features still work;<br>the sync check politely tells you it needs a model rather than falling<br>back to unreliable text diffing.

Model options:

auto (default) — VS Code's Language Model API, typically backed<br>by GitHub Copilot.

local — an OpenAI-compatible endpoint such as LM Studio or<br>Ollama, for a fully offline setup with no cloud dependency.

2. Length hygiene

If a rule file exceeds rulesSync.maxLines non-empty lines (default<br>200), an Information diagnostic on line 1 suggests splitting it into<br>nested rule files. No AI required.

3. Active-file indicator

A status bar item shows which rule file governs the file you're<br>currently editing, using "nearest file wins" (the closest rule file<br>walking up the directory tree): Rules: , or<br>Rules: none. Click it to open that file. Updates as you switch<br>editors. No AI required.

Configuration

Setting<br>Default<br>Description

rulesSync.enable<br>true<br>Master on/off switch.

rulesSync.maxLines<br>200<br>Non-empty-line threshold for the length check.

rulesSync.watchedFiles<br>["AGENTS.md", "CLAUDE.md", ".cursorrules", ".github/copilot-instructions.md"]<br>File names/paths sync.md watches.

rulesSync.modelProvider<br>"auto"<br>"auto" uses VS...