Agent hooks
An agent program can start a sync by itself: when a session starts, and each time the agent stops. Then the files you track are in step without you running korbo sync.
Set them up
This writes korbo's hooks into every agent program it finds on the machine. It keeps everything else in those files, replaces a korbo hook written earlier, and changes nothing when run again.
korbo hooksshows which programs were found and whether the hooks are set up.korbo hooks removetakes korbo's hooks out again.- Name programs to limit either command, for example
korbo hooks install codex.
The hooks call the korbo program at the path it was run from, so run korbo hooks install from ~/.korbo/bin/korbo.exe.
What each program gets
Codex runs a new or changed hook only after you trust it. Start codex in a terminal, open /hooks, and trust both korbo hooks. Trusted hooks run outside Codex's sandbox, so they can reach the hub.
Antigravity cannot show anything after a turn. A change synced after a turn is reported at the next session start, and a conflict is reported again until it is settled.
When nothing appears
korbo sync --hook prints nothing when nothing changed, so a quiet session is the normal case. It always exits with code 0, because a failing hook at the end of a turn would keep the agent working; every problem is reported in the line instead.
To see a line, change a tracked file, then start a new session.