Connect a Git Repository (and Other Connections)
1. Register the connection at the org level
Go to Project Config → Connections tab → Add connection:
- Type —
GIT,JIRA,CONFLUENCE,FIGMA,SLACK,SMTP,WEBHOOK, orCOGNEE(memory provider). - For
GIT, pick a Provider — GitHub, GitLab, Bitbucket, Azure DevOps, or generic Git. - Name — a short label you'll recognize later (e.g.
acme-git). - Base URL — your Git host, e.g.
https://git.example.com. - Auth type — Personal Access Token, OAuth2, SSH key, or Basic.
- Credentials — paste your token/key into the secret field shown for the chosen auth type. It's stored encrypted and never shown again after saving.
Click Add connection.
2. Map the repository into your project
Go to Project Config → Repositories tab → Add repository:
- Organization / Project — which project this repo belongs to.
- Connection — the connection you just created.
- Repository key — the alias agents will refer to (e.g.
payments-api). - Clone URL — the full repository URL.
- Default branch — usually
main. - Branch pattern — the pattern agent-created branches must follow, e.g.
agent/feature/*. - Protected branches — branches whose pushes must never be auto-approved (e.g.
main,master,release/*), one per line. A matching push is parked for explicit approval.
Click Add repository.
If a project has exactly one repository (the common case), a workflow run uses it automatically — no extra setup needed.
Binding a non-Git connection
Jira, Confluence, and memory-provider connections use the same idea, one tab over:
Go to Project Config → Project Bindings tab → Bind connection:
- Organization / Project / Connection — same as above.
- Connection key — the alias an agent profile refers to (e.g.
memory-main). - Role — optional label if you're binding the same connection type twice.
The Connection key must exactly match what the agent profile expects. A mismatched or missing binding can fail dispatch with a message such as "No active memory connection 'memory-main' mapped to project PAYMENTS." Bind the expected alias to an active connection, then retry the task.
Next
With a repository (and any other connections) in place, move on to Create a Registry Resource — the skills, hooks, plugins, and permission presets your agent profiles will use.