Skip to content
GAP DOCS

Sync your setup

gap sync copies your rules into every agent’s file and installs any listed skills that are missing. It never moves a skill pin.

The three-step flow

Section titled “The three-step flow”
  1. § 01 EditEdit global/AGENTS.md, merge it to master, and pull. gap sync only publishes merged rules.
  2. § 02 SyncRun gap sync.
  3. § 03 CheckRun gap status to see each component's pin and any skill drift. It writes nothing and exits 1 on drift.
Terminal
$ gap sync
$ gap status
Note

gap status writes nothing and exits 1 on drift. That is a signal, not a crash.

Note

Only gap pin <id>@<ref> moves a pin in gap.lock.

Tip

If sync asks about a file it did not write, answer in a terminal. In an agent's shell with no terminal, it printsRefusing to replace foreign file, skips that file, publishes the rest, and exits 1.

One rules file, six agent files

Section titled “One rules file, six agent files”

Write your policy once in global/AGENTS.md. gap sync copies it into the file each agent already reads: Claude, Pi, OMP, Codex, Cursor and Empryo. Grok reads the Claude copy.

How it flows

Section titled “How it flows”
How gap sync flowsglobal/AGENTS.md on the left. gap sync copies it into the file for each of six agents: Claude, Pi, OMP, Codex, Cursor and Empryo. A dotted line shows Grok reads the Claude copy.global/AGENTS.mdONE RULES FILEGAP SYNCClaudePiOMPCodexCursorEmpryoGrokREADS THE CLAUDE COPY
Fig. 01 · gap syncSix agents get a copy. Grok reads the Claude copy.