Intelligence Sync is an archived project positioned as a single source of truth for AI coding rules across multiple AI coding tools (Claude Code, Cursor, Copilot, Codex, etc.), with the core idea of "write once, sync everywhere." This repository no longer accepts new feature development; the officially supported successor product is Intelligence CLI, distributed under the package name @ainova-systems/intelligence. The final built-in release version is 0.10.4; existing projects can remain unchanged and continue to use it, but new projects should not copy this repository or bootstrap from its legacy engine.
Main purpose and capabilities: to uniformly manage and synchronize coding rules for multiple AI coding assistants, avoiding repeated maintenance across multiple tools. It supports retaining a project's existing rules, agents, skills, and adapters, and upgrading through CLI lifecycle management.
Requirements for installing the successor product: Node.js 18+, Git, Bash, and awk; on Windows, Git Bash or WSL is required. For the specific installation method for new projects, refer to the package, adapter, and CLI lifecycle instructions in the official Intelligence documentation (the materials do not provide specific installation commands).
Converting from an existing Intelligence Sync project: conversion is one-way, plan-first, and transactional. It is recommended to first commit or stage unrelated changes, then run intelligence init --preview in the project root directory. This command does not write anything; it detects the built-in project, stages the proposed root intelligence.yaml, lockfile, package store, and generated output, and then displays the conversion plan. --apply executes the reviewed plan and rolls back if staged validation or synchronization fails. The specific commands for the post-conversion lifecycle are not listed in the materials. During conversion, the CLI preserves the project's own rules, agents, skills, and adapters; the built-in engine and legacy config.yaml will be replaced by the root manifest, the committed lockfile, and the CLI-managed package store.
Project version limitations: the CLI conversion boundary is legacy schema 0.10.0 or newer. If intelligence init --preview reports an older or missing sync_version, you must first instruct the coding agent to update intelligence-sync to the final built-in version, and then provide the migrationoptions to Intelligence CLI. For conventional modular layouts, the directly compatible commands are not provided in the materials. Very old flat-layout projects use intelligence/scripts/update.sh; the update process can discover and migrate either layout without touching project-authored content. After upgrading to 0.10.4, run intelligence init --preview again. If the agent is started from an update skill prior to 0.10.2, a second update request may be required, because the newly installed migration process cannot replace instructions already loaded in the current turn.
Continuing to use the legacy engine: for projects not yet ready to convert, the built-in engine remains functional and deterministic; however, it is frozen, and new features, adapters, packages, and lifecycle work all belong to the ainova-systems/intelligence repository. Historical references include the legacy changelog, legacy conventions, legacy adapter contracts, and final migration tips. The license is MIT.
