Install aisync

One standup for all your AI coding tools: shared rules, a hash-chained journal, file claims and mid-session news hooks for Claude Code, Codex and Cursor. You install it by handing this page to your AI.

For humans

Paste this into your AI coding agent (Claude Code, Cursor, Codex, or any capable agent). It reads this page and sets everything up, asking before it changes anything.

Read https://maxont.github.io/aisync/install and install aisync for me.

You need Python 3.11 or newer, git, and an agent that can run shell commands.

Prefer the terminal? One line installs the aisync command (it never edits your shell config):

curl -fsSL https://maxont.github.io/aisync/install.sh | bash

Want to read the script first? install.sh. Add --dry-run to see what it would do without changing anything.

FOR YOUR AI

You are the AI agent the user gave this page to. Everything below is addressed to you. Follow it in order. If you cannot do a step, say so plainly instead of pretending.

0. What you are installing

One standup for all your AI coding tools: shared rules, a hash-chained journal, file claims and mid-session news hooks for Claude Code, Codex and Cursor. Source: https://github.com/MaxonT/aisync.

1. Capability gate

You must be able to (a) run shell commands and (b) read and write files in the user's home directory. If either is missing, stop and tell the user to paste this prompt into an agent that can, or to run the terminal one-liner above by hand.

2. Preconditions

python3 --version reports 3.11 or newer.
git --version works. aisync keeps its hub in a local git repo; without git, stop and tell the user how to install it.
One of uv, pipx or python3 -m pip is available. Prefer them in that order. When the system Python refuses user installs (PEP 668), the script uses its own virtualenv in ~/.local/share/aisync instead.
Never use sudo. Never install system-wide.

3. Ask before you touch anything

Before running anything that changes the machine, show the user the exact command and wait for a yes. Start with a dry run:

curl -fsSL https://maxont.github.io/aisync/install.sh -o /tmp/aisync-install.sh
bash /tmp/aisync-install.sh --dry-run

Read the output to the user. After they agree:

bash /tmp/aisync-install.sh
aisync --version

If aisync is not on PATH, do not edit shell config on your own. Tell the user which command fixes it (uv tool update-shell, pipx ensurepath) and ask. Until then, run it by the full path the script printed (for example ~/.local/bin/aisync).

4. First run

Show the user what a hub looks like. This writes only to a new temp dir:

aisync demo

Then create their own hub (in ~/.ai-sync; it does not touch any tool config):

aisync init

Wiring the hooks changes tool configs (~/.claude/settings.json, ~/.codex/hooks.json, ~/.cursor/hooks.json, the rule files, and the global git core.hooksPath). Show the user the diff first:

aisync install-hooks --dry-run

Walk them through it and ask which parts they want. Apply only what they approve, for example:

aisync install-hooks --only claude-code,codex,cursor --yes

Finish with aisync status.

5. Rules you must keep

Additive only. Never overwrite or delete existing user files.
Do not touch shell config, ~/.ssh, ~/.gitconfig or LaunchAgents without an explicit yes for that specific change.
Be honest about failure. If a step failed, say which one and why.

6. Report back

Finish with a short summary: what was installed, whether aisync --version worked, what you did not do, and the one next step for the user.

aisync is MIT licensed. Star it on GitHub if it helps you.