Open Cursor from Chain
Press Open AI and pick Cursor, or from a terminal:
Cursor opens on a fresh worktree and branch for the task. The repo already contains Chain’s rules and hook, written between chain:begin / chain:end markers, so Cursor’s agent reads the board before it edits and claims the paths it touches.
What happens when it hits a claimed file
If Cursor’s agent reaches for email.ts while a teammate’s Claude Code session holds it, the pre-tool hook refuses the write and says who has it and for which task. The agent can work on something else or queue the change for after. You see the same thing on the timeline: “Blocked on email.ts (Max). Queued to change it after.”
Merging without a meeting
When the task is done, Chain runs your tests in the worktree, merges if they pass and nothing conflicts, pushes, and releases the claims. If two branches did change the same lines, the merge waits for a person. The docs cover merging and conflict review in detail.
Private by construction
Cursor keeps running on your Mac with your own Cursor account. Chain’s relay only sees claims, tasks and log lines. Code moves through your own GitHub or git remote.