GitHub, GitLab & Azure DevOps

Synergoi talks to your forge for three things: authenticating pushes, opening pull requests, and pulling a pull request into a thread. It supports GitHub, GitLab and Azure DevOps. Bitbucket is not supported.

GitHub

Open Settings › Source control › Hosting. If the gh CLI is installed and signed in, Synergoi adopts that login and the card shows your handle with gh CLI as the mode. Otherwise choose Authorize GitHub for a device-code flow: enter the code on github.com, press I authorized, done. You can disable GitHub for Synergoi at any time without touching your gh login.

GitLab and Azure DevOps

Both connect with a personal access token pasted once, or by adopting a login you already have: glab for GitLab, the Azure CLI (az) for Azure DevOps, and any git credential helper that already answers for the host. Adoption is on by default and can be disabled per host. Adopted secrets are held in memory only; pasted tokens are stored encrypted in the app's data folder.

Pull a pull request into a thread

From the project's forge panel, choose a pull request. Synergoi creates a thread named after it, checks the request's source branch out into a worktree, and opens the Changes dock on the diff against the base branch. Ask any model to review it, fix it, or explain it; pushing from that thread updates the pull request.

Clone from the app

The forge panel also lists your repositories so you can clone one straight into a new project, and shows the local checkouts Synergoi already knows about.