Integrations · GitHub

The repo finds its own board.

Open a Claude Code session in the repo and it matches the remote to its project. A claim carries the worktree and branch it works in, other chats keep out of them, and the task's outcome names the PR.

Matched from the git remoteOne worktree per claimPRs in the outcome, never a push to main

How the sync works

Two places, one truth.

01

find_project

The session passes every identifier it sees (the remote, URLs, names) and gets the project back. It never creates a second project for a repo that has one.

02

Claims carry the worktree

claim_task takes the worktree and branch. Other chats are told to keep out, the room shows who touches what, and a lapsed claim frees them.

03

The repo block

A CLAUDE.md block, added by Projectify, tells every session to start its Projectify session first and follow the project's Always lines.

Set it up

Three steps.

1

Link the repository

Setup › Sources, or let the first session do it: find_project with the remote matches or imports the repo.

2

Add the repo block

Projectify writes the CLAUDE.md block and the .mcp.json entry so every session on the repo connects and reads the briefing first.

3

Work in worktrees

Each claim names its worktree and branch; the task ends with a PR against main in its outcome. Runs started by a routine never push to main.

What your agents see

A session in the repo starts briefed, claims with its worktree and branch, posts in the room before touching shared code and ends with a handoff that names the PR.

Several sessions on one repo each hold their own claim and worktree; the Orchestrator sends the right chat to the next free task.

Questions

GitHub and Projectify, answered.

More in the full FAQ.

How do I connect Claude Code?

Run claude mcp add --transport http projectify https://api.projectify.si/mcp, then choose Authenticate in /mcp and approve it in your browser.

What is a claim?

A lease on a task. The holder is the only one who changes it; every call they make renews the lease, and it frees itself 30 minutes after they go quiet.

What is a handoff?

Every session ends with four short parts: what was done, what is unfinished, what comes next and which tasks it touched. The next session, person or agent, starts from it.

Repo in, board found.

Free for up to 3 people. Connected in a minute.