NOW IN BETA

One source of truth for all your config files

Sync CLAUDE.md, .cursorrules, settings.json, and any file across all your repos with a single CLI command.

See How It Works

~/my-project

$ npx rulesync-cli pull

Fetching: company-defaults, nextjs-standards, claude-settings...

✓ Wrote CLAUDE.md (2 files, 1.4kb)

✓ Wrote ~/.claude/settings.json

✓ Wrote .cursorrules

How It Works

Three steps to consistent AI rules

Create Files

Author shared rules and config files in the dashboard — CLAUDE.md, .cursorrules, settings.json, or any file. Version every change.

Authenticate via CLI

Run npx rulesync-cli login to open your browser and link the CLI to your account. One-time setup, no token pasting required.

Sync with CLI

Run npx rulesync-cli pull or add it to postinstall. All your files stay in sync across every repo, automatically.

Features

Everything you need to manage AI rules & config

Versioned Files

Every edit creates a new version. Roll back anytime. See exactly what changed and when.

Any File, Any Path

CLAUDE.md, .cursorrules, settings.json, or custom paths. Markdown and JSON supported. Sync to ~ home paths or relative project paths.

CLI-First Workflow

npx rulesync-cli pull. Add to postinstall. Works in CI. Zero friction for your team.

API Key Auth

Generate scoped API keys for CI pipelines and local CLI. Revoke anytime from the dashboard.

Dashboard Editor

Full markdown editor with live preview. Manage files, projects, and team settings in one place.

Multi-Repo Scale

Built for teams with 5, 50, or 500 repos. Change once, propagate everywhere.

Built for teams that ship with AI

50+

Files synced

200+

Repos connected

< 1s

Avg sync time

99.9%

API uptime

FAQ

Common questions

What files does RuleSync manage?

Any file. CLAUDE.md, AGENTS.md, .cursorrules, ~/.claude/settings.json, .github/copilot-instructions.md — you set the output path per file. Markdown and JSON are both supported, with JSON validation built in.

How does the CLI authenticate?

You generate API keys from the Settings page in the dashboard. The CLI stores your key locally at ~/.rulesync/auth.json. Keys can be scoped and revoked anytime.

Can I use RuleSync in CI/CD pipelines?

Absolutely. Set the API key as a secret in your CI environment and run npx rulesync-cli pull as a build step. The CLI also supports a rulesync check command to verify files are in sync without writing.

What happens if two files conflict?

Files are composed in the order you specify. Later files appear below earlier ones in the output. The AI tool reads top-to-bottom, so later rules naturally take precedence for conflicting instructions.

Is my file content private?

Yes. All files are private by default and only accessible to you and your API keys. We plan to add optional public files for sharing community standards.

Is RuleSync free?

RuleSync is free during the beta period. We plan to offer a generous free tier for individual developers and paid plans for teams and organizations.

Stop copy-pasting AI config files

Set up RuleSync in under two minutes. Free during beta.