Caliber — AI Agent Config Sync

Keep your AI setups in sync with one command — generate and maintain context files for Claude Code, Cursor, Codex, and more.

Stars
★ 1.3k
Last updated
25d ago
License
MIT
Primary language
TypeScript

At a glance

How it runs
CLIAgent plugin / skill
Works with
Platform-specificCodex · Claude CodeChatGPT (Unsupported)
Cost
Free software; you pay for model usage
Setup effort
Low · running in minutes
You'll need
Node.js >= 20Shell / CLINetwork accessLocal filesystemMCP Server
Typical use
A developer who just refactored a project wants CLAUDE.md and Cursor rules updated automatically, so the AI doesn't hallucinate outdated paths.
Not a fit if
  • Windows users who only run PowerShell and won't use Git Bash
  • Environments without Node.js 20 or newer

What does this agent do, and when should you use it?

Caliber is a CLI tool (npm package @rely-ai/caliber) that solves the problem of stale AI agent context files (CLAUDE.md, .cursor/rules/, AGENTS.md) by automatically generating and maintaining them. It uses deterministic scoring (caliber score) to audit existing configs, generates tailored context files, MCP configurations, skills (OpenSkills format), and hooks for multiple platforms. Caliber supports various LLM providers (Anthropic, OpenAI, MiniMax, Vertex AI) but can leverage existing Claude Code or Cursor subscriptions without extra API keys. Installation is via npx, and the initial setup is handled by the agent itself via /setup-caliber. All writes are diffed, backed up, and reversible.

Caliber provides two primary commands: caliber bootstrap (installs agent skills for fastest start) and caliber init (full interactive wizard). caliber score performs a deterministic audit, cross-referencing config files against the actual filesystem, and outputs a score with structured fix data. caliber refresh analyzes git diff (committed, staged, and unstaged) and updates config files to reflect code changes. caliber learn installs hooks to capture AI session events and distill patterns into CALIBER_LEARNINGS.md. caliber hooks manages git pre-commit and session-end hooks for auto-refresh. caliber undo and caliber uninstall provide full reversibility. Generated files include CLAUDE.md, CALIBER_LEARNINGS.md, .claude/skills/*/SKILL.md, .mcp.json, .cursor/rules/*.mdc, AGENTS.md, .github/copilot-instructions.md, and more.

  1. A developer who just refactored a project wants CLAUDE.md and Cursor rules updated automatically, so the AI doesn't hallucinate outdated paths.
  2. A team wants to keep AI configs consistent across Claude Code, Cursor, Codex, OpenCode, and GitHub Copilot, ensuring every member's agent behaves the same.
  3. A user wants to assess the quality of their current AI setup before making changes, using caliber score --compare main to see how a branch impacts the score.
  4. A developer who already has a Claude Code or Cursor subscription wants to generate configs without paying for additional API keys.
  5. A developer wants configs to refresh automatically on every commit via pre-commit hooks, reducing manual maintenance.
  6. A team working in a monorepo wants to run caliber refresh from a parent directory to update configs across multiple repositories at once.

How do you install or deploy this agent?

Requires Node.js >= 20. Run in your project root: npx @rely-ai/caliber bootstrap. No API key is needed for bootstrap or scoring (fully local). Alternatively, use caliber init for the full wizard. For generation, you can configure an LLM provider: export ANTHROPIC_API_KEY, OPENAI_API_KEY, or MINIMAX_API_KEY, or use your existing Claude Code or Cursor subscription.

How do you use this agent?

Run npx @rely-ai/caliber bootstrap. Then, in your terminal (not IDE chat), start a Claude Code or Cursor CLI session and type /setup-caliber. The agent will analyze your codebase, generate configs, install hooks, and enable continuous sync. If you don't use Claude Code or Cursor, run caliber init as a CLI wizard. Common commands: caliber score to see your score, caliber refresh to update docs, caliber undo to revert changes, caliber hooks --install to enable auto-refresh hooks. All writes are diffed and backed up first.

What are this agent's strengths and limitations?

Pros
  • Deterministic scoring (no LLM) provides consistent, auditable config quality checks, with git branch comparison.
  • Bootstrap and scoring are fully local and don't send code; generation uses your own AI subscription or API key.
  • Automatic backups, score regression guard, full undo, and clean uninstall ensure safety and reversibility.
  • Supports multiple platforms (Claude Code, Cursor, Codex, OpenCode, GitHub Copilot) to unify team configs.
  • Automatic MCP server discovery and skills in OpenSkills format enhance agent capabilities.
Limitations
  • Generation requires network and third-party APIs (unless using Claude Code or Cursor subscription), and sends a project summary to the LLM provider.
  • Generates many files, potentially increasing repo complexity; requires Node.js >= 20.
  • Windows support has caveats: Git Bash recommended, avoid multiple terminals, hooks may be silently skipped in PowerShell.
  • Core operation depends on specific agent environments (e.g., /setup-caliber for Claude Code), requiring extra configuration for cross-platform use.
  • Scoring criteria may favor certain config styles and may not suit all project structures.

How does this agent compare with similar options?

Key facts side by side with the most closely related agents.

Agent Source review Form / cost Stars Updated Language Full support on
Caliber — AI Agent Config Sync This agent 58 · Major gaps CLIFree + model costs ★ 1.3k 25d ago TypeScript Codex · Claude Code
Puppetmaster 68 · Some gaps CLIFree + model costs ★ 468 today Python Codex · Claude Code
Loop Library: Reusable AI Agent Workflows 61 · Some gaps Agent plugin / skillFree ★ 3.2k 3mo ago JavaScript Codex · Claude Code
Self-Learning Skills 56 · Major gaps Agent plugin / skillFree + model costs ★ 968 1mo ago — Codex · Claude Code

How does FollowAgents rate this agent?

FollowAgents source review · FARS-2.1
Major gaps
58/ 100 5-point scale 2.9 / 5
This review covers the source as of Aug 09, 2026. The project has shipped 4 stable release(s) since, which have not been re-reviewed. The score and verdict describe the reviewed version only. Recent releases ↓
Trust 18/29
Reliability 6/14
Adaptability 12/18
Convention 10/18
Effectiveness 9/13
Verifiability 3/8
Why each dimension lost points
Trust18 / 29 · 3.1/5

Evidence: CLI requires user confirmation before writes (diff review), provides backups and undo, API keys stored in ~/.caliber/config.json with 0600 permissions, and claims no code is sent. Deductions: dependencies use caret ranges (^) posing supply chain risk; telemetry enabled by default requiring opt-out; publisher unverified, source attribution unclear.

Reliability6 / 14 · 2.1/5

Evidence: README and package.json descriptions align, CI configured for multi-platform tests. Deductions: dependency version ranges are broad, potentially causing non-reproducible builds; failure messages not detailed in docs, relying on CLI output.

Adaptability12 / 18 · 3.3/5

Evidence: Supports multiple AI tools and languages, provides multiple installation methods (bootstrap/init), and includes Windows-specific notes. Deductions: capability boundaries not explicit (e.g., MCP discovery scope), triggers like /setup-caliber depend on user action, environment fit not covering all scenarios.

Convention10 / 18 · 2.8/5

Evidence: README well-structured with install notes, FAQ, command list, MIT license clear. Deductions: no explicit changelog, naming stability not guaranteed (frequent version updates), known limitations not listed, maintenance responsibility unclear (publisher unverified).

Effectiveness9 / 13 · 3.5/5

Evidence: Output is usable config files, provides scoring and auto-fix, high marginal value (saves manual maintenance). Deductions: cost-benefit not quantified, no real-world usage cases or performance data.

Verifiability3 / 8 · 1.9/5

Evidence: README claims (e.g., local operation, deterministic scoring) align with code structure, but no independent verification. Deductions: lack of traceable test results, insufficient cross-source corroboration, facts vs inferences not clearly separated.

Risks and how to mitigate them
  • Dependencies are not pinned, posing supply chain risk; consider locking versions.
  • Telemetry is enabled by default, requiring opt-out; be aware of privacy.
  • Publisher is unverified, source attribution unclear; evaluate before use.
Evidence confidence: Low Reviewed Aug 09, 2026 Reviewed revision 7950921a7220 New commits since this review; the score may not cover them
See the full review method →

Recent releases

Latest entries from the project's GitHub Releases. Notes are quoted from upstream as written, not rewritten or tested by FollowAgents.

  1. v1.55.2
    Release notes excerpt
    What's Changed * docs: lean README in the /solution design language by @keterslayter in https://github.com/caliber-ai-org/ai-setup/pull/252 Full Changelog: https://github.com/caliber-ai-org/ai-setup/compare/v1.55.1...v1.55.2
    View on GitHub ↗
  2. v1.55.1
    Release notes excerpt
    What's Changed * fix(hooks): freshness hook cannot parse the state file caliber writes by @mann1x in https://github.com/caliber-ai-org/ai-setup/pull/250 Full Changelog: https://github.com/caliber-ai-org/ai-setup/compare/v1.55.0...v1.55.1
    View on GitHub ↗
  3. v1.55.0
    Release notes excerpt
    What's Changed * feat: Jev compaction for Cursor, Grok Bot, and other non-Claude agents by @keterslayter in https://github.com/caliber-ai-org/ai-setup/pull/249 Full Changelog: https://github.com/caliber-ai-org/ai-setup/compare/v1.54.0...v1.55.0
    View on GitHub ↗

FAQ

Does Caliber overwrite my existing configs?
No. Caliber shows a diff of every proposed change, and you can accept, refine, or decline. Originals are backed up to .caliber/backups/ automatically, and caliber undo restores everything.
Do I need an API key to use Caliber?
Bootstrap and scoring don't need one. For generation, you can use your existing Claude Code or Cursor subscription, or bring your own key for Anthropic, OpenAI, MiniMax, or Vertex AI.
Does Caliber send my code anywhere?
Scoring is fully local. Generation sends a project summary (languages, structure, dependencies — not source code) to the LLM provider. Anonymous usage analytics (command names, durations — no code) are collected via PostHog; opt out with CALIBER_TELEMETRY_DISABLED=1.
Does Caliber work with monorepos?
Yes. You can run caliber init from any directory, and caliber refresh can update configs across multiple repos when run from a parent directory.
What if I use Windows?
It works, but Git Bash is recommended, and you should run from a terminal (not IDE chat). Some hooks may be skipped in PowerShell, and avoid running from multiple terminals simultaneously.
View on GitHub ↗ Install ↓

Compare agents like this one

The same FARS review applied across the shortlist this agent qualifies for.

Related agents