aisync: Multi-Agent Context Management, Coordination & Observability
One local hub for developers working with multiple AI coding agents: share the right context, coordinate concurrent work, and verify what happened.
aisync is agent-agnostic at its core. It provides native hooks for Claude Code, Codex and Cursor, and exposes its hub to other agents through a CLI, MCP server, or shared instruction files. These three native integrations are not a limit on which agents can use aisync.
English · 中文 · Website · Demo status board
[!NOTE]
Multiple coding agents should not have to work with isolated rules, conflicting file ownership, and disconnected histories.
aisync is a local, verifiable hub (~/.ai-sync/, a git repo) designed for multi-agent workflows:
- Context management: share and 3-way-sync rules; load core context up front and inject relevant context on demand, including mid-session updates where hooks are available.
- Multi-agent coordination: declare file claims, detect overlapping claims (exit code 3), release ownership, and surface blockers and other agents' activity.
- Observability & verification: inspect agent activity, blockers, and health through the journal, status reports, and board;
aisync verify checks the journal's hash chain for tampering.
File claims are cooperative, not OS-enforced locks: agents must use the claim protocol. Hash-chain verification detects changes to recorded events; it does not prove every claimed action occurred.
Who it's for
Developers running two or more AI coding agents across one or multiple repositories—especially when agents work concurrently, hand tasks off, or need a shared record of decisions and blockers. aisync is not another coding agent or a task orchestrator: it is the shared context and coordination layer those agents can use.
See it
The Agent Swarm Floor
https://github.com/user-attachments/assets/b28bed86-c262-4efa-b92d-9eeca2bf5b73
Integrations: native hooks are not the compatibility boundary
| Integration | Who can use it | What to expect |
|---|
| Native hooks | Claude Code, Codex, Cursor | Automatic context and news delivery at supported hook events, plus access to aisync's coordination and journal commands |
| MCP server | MCP-compatible agents | Exposes rules, rule additions, logging, claims, releases, news, status and tidy; an agent must invoke the tools |
| CLI | Agents that can run shell commands | Direct access to hub operations such as aisync claim, aisync news, aisync log and aisync verify |
| Shared instruction files | Agents that read supported instruction files | Standing rules and context only; not automatic mid-session news or file-claim enforcement |
Compatibility is not equivalent to automatic integration. For agents without native hooks, features depend on the agent's MCP/CLI usage and configuration. aisync does not automatically intercept all edits or guarantee every agent will honor file claims.
Install
Give it to your AI. It reads the page, does a dry run first and asks before it changes anything:
Read https://maxont.github.io/aisync/install and install aisync for me.
Or in a terminal. It installs with uv, pipx or pip and never edits your shell config:
curl -fsSL https://maxont.github.io/aisync/install.sh | bash
Needs Python 3.11+ and git, on macOS or Linux. Nothing else: aisync uses only the standard library.
Two agents, one file
A real terminal run: aisync demo (synthetic data), then two tools reach for the same file.
Step by step: how it works · the same demo hub as a
status board.
| Multi-agent need | What aisync provides |
|---|
| Context management | 3-way-synced rules, layered rule loading and relevant mid-session news via hooks |
| Multi-agent coordination | Cooperative file claims and releases, overlap detection (exit 3), blockers and activity updates |
| Observability & verification | Hash-chained event journal, aisync verify, status, report, tail and a static board |
aisync also does the rules part: one rules block copied into every tool's own rule file, synced 3-way, conflicts never overwritten.
Dogfooded: 6,700+ journal events from 7 AI tools over 4 weeks.
Why not just AGENTS.md?
Keep AGENTS.md for a repo's standing instructions. aisync sits beside it and covers what a single file cannot: the context that changes while agents work.
| AGENTS.md | aisync |
|---|
| Scope | Standing instructions for agents working in a repo | A shared hub across configured agents and repositories |
| When it is read | When a session starts | At start, and mid-session through hooks |
| Who is editing what | Not covered | Cooperative claims: an overlap returns exit 3 to the caller |
| Tamper evidence | Not provided by the file format | Hash-chained journal: aisync verify detects alterations to recorded events |
| Context per session | Whole file, every time | Triggered rules only: always-loaded rules 20,673 → 7,876 tokens* |
* Measured once on one author's own hub (2026-11-08), always-loaded rules before and after layered loading. One machine, not a benchmark: your numbers will differ. aisync tidy reports your own rule budget and uncited rules.
Use it
aisync demo # a throwaway hub with a synthetic two-week journal
aisync init # create ~/.ai-sync (or wherever AISYNC_HOME points)
aisync install-hooks # shows every tool config change as a diff, then asks
aisync watch & # event-driven sync loop (or run `aisync sync` by hand)
What an agent does during a session:
여기까지가 README 앞부분입니다. 나머지는 원문에서 읽을 수 있습니다. README 전문 보기 ↗
