返回资讯中心
外部精选
软件工程
#开发者实时流

Show HN: Aisync, advisory file claims so two AI agents don't edit one repo

Claude Code, Codex and Cursor share rules, a journal and file claims, and hear what the others did mid-session.

Hacker News 最新MaxTigerYoung2026/11/10 · 7 天前18 分钟阅读

以下正文同步自 Hacker News 最新,版权归原站所有,已转换为易读排版。

Claude Code, Codex and Cursor share rules, a journal and file claims, and hear what the others did mid-session.

English · 中文 · Website · Demo status board

Your AI tools are coworkers who never talk. aisync is their standup. Every tool works out of one local hub (~/.ai-sync/, a git repo). Before editing, an agent claims files, and an overlapping claim exits with code 3, so the agent stops before it collides. Every decision, blocker and commit goes into one hash-chained journal. Hooks tell a running Claude Code, Codex or Cursor session what the other tools just did, and stay silent when nothing changed.

If aisync keeps your agents from stepping on each other, a star helps other people find it.

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.

After your first successful command, the CLI asks once: Star MaxonT/aisync on GitHub? [y/N]. The default is no, it never asks again, and it stays silent in CI, pipes and scripts. A yes stars the repo through your own gh login (or prints the link if gh is missing). Set NO_STAR_PROMPT=1 to skip the question.

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.

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.

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:

aisync claim -a codex -p api -f app/payments/ -m "SDK upgrade" # 3 = taken aisync log -a codex -p api -m "SDK 5.0, retries kept" aisync rule add -a codex --when "changing an API" --do "add a contract test" aisync release -a codex -p api

Command What it does

init create the hub: shared rules, journal, config, local git repo

log append one event (dev_log, decision, blocked, unblocked, rule_change, note)

rule add / rule list any agent adds a shared rule (--when/--do/--not, --topic, --replaces R-012); every tool's copy gets it on the next sync

rule lint / rule rewrite / rule enforcement rules not in the When/Do/Not shape / rewrite them by ID without losing a fact / which test or hook keeps each rule

tidy rules clerk: likely duplicates, rules nobody cited lately, core layer over budget; proposals only, you tick them

rulecheck prove a rules cleanup lost no hard fact (paths, numbers, commands, IDs)

instinct optional habit list grown from past mistakes, injected into every session

mcp serve the hub to any MCP agent over stdio (pip install 'aisync[mcp]')

claim / release / claims who is working on which files right now; overlap = exit 3

news what other tools did since this session last looked

hook <tool> entry point for Claude Code, Codex and Cursor hooks (reads hook JSON, never fails)

install-hooks wire the hooks, seed the rules block, add the git Agent: trailer hook; diff first, asks before writing (--dry-run, --yes)

status health, conflicts, claims, blockers, metrics (exit 1 when something needs you)

board write the hub as one static HTML page: claims, blockers, who did what, timeline

report read-only self-check: silent tools, commits without an Agent: trailer, stale blockers

tail latest journal events

verify check the hash chain

sync / watch run one sync cycle / the debounced, event-driven loop

resolve / resume rule on a rule conflict / clear failure counters after a pause

demo the throwaway hub shown above

New in 0.2.0: rules as interfaces, loaded in layers

A rules file grows until every session pays for it and nobody reads it. 0.2.0 treats a rule like an API:

Step through it at your own pace (play, pause, ← →)

A sync cycle is harvest (new git commits in watched repos become journal events, attributed by their Agent: trailer) → rules (new entries in repos you list in rule_sources) → distribute (3-way sync of the rules block into each tool file) → render (progress page) → flush (commit the hub, optional push). Each step is isolated: one failure never blocks the others.

The rules block is synced 3-way. If only the truth changed, copies are overwritten (with a backup). If one copy was edited and nobody else changed anything, the edit is adopted everywhere. If both sides changed, nothing is overwritten: it becomes a conflict for you to resolve.

Reliability and observability: timeouts and retries with backoff on every git call, failure isolation per step and per project, auto-pause after fail_threshold failures in a row with an ALERT.md and a desktop notification, a per-cycle run log (state/runs.jsonl), hook call stats and aisync status for all of it.

~/.ai-sync/config.toml (set AISYNC_HOME to put the hub anywhere):

roster = ["claude-code", "codex", "cursor"] # tools report expects to hear from scan_dirs = ["~/projects"] # every git repo inside is watched rule_sources = [] # repos whose AGENTS.md "## Meta rule" feeds shared rules remote = "" # e.g. "origin" to also push the hub

progress_file = "progress.md" # keep agents.md byte-stable; hooks inject progress at session start rule_spec = true # rule add only accepts When/Do/Not rules require_enforcer = false # true: every new rule names --enforced-by or --judgment-only core_topics = ["Safety", "Meta"] # topic headings a layered copy carries in full instincts_path = "" # optional habit file injected at session start tidy_daily = false # the watcher starts one aisync tidy --write a day tidy_usage_globs = [] # files whose R-### mentions count as a rule being used

[shelf] # folded topic -> keywords that pull it into a session Deploys = ["deploy", "terraform", "rollback"]

[[target]] # files carrying the shared-rules block label = "claude-code" path = "~/.claude/CLAUDE.md" layer = "core" # optional: fold non-core topics, inject them on demand

To keep aisync watch running, start it from your login items, a systemd user unit or a launchd agent that runs aisync watch; create ~/.ai-sync/STOP to stop it cleanly.

aisync: AGENTS.md, but for live coordination between AI tools.

aisync is an independent project, not affiliated with the projects above.

python3 -m unittest discover -s tests # includes wheel -> venv -> demo

The images are generated: the terminal GIF is a recorded real run of .github/refine/demo-terminal.json, the how-it-works animation comes from .github/refine/how-it-works.stages.json, and the credits above from .github/refine/lineage.json. All demo data is synthetic.

正文由 探How 从来源站点 RSS 同步,内容未经改写;遇到排版缺失或需要图片、视频时请以原文为准。

打开原文
去社区讨论 →