Integration

GitHub and AI agents

When the pull request merges, the task moves. Nobody has to go back and drag the card, whether a person or an agent wrote the code.

Get early access

Figure 1. A pull request opened in GitHub links to the Cyborg task it closes; when it merges, the task is done.

Pull requests move tasks

A pull request that mentions a task links to it. Map each pull request state, such as draft, review requested, merged or closed, to a workflow state in your Cyborg project, and the task moves when the pull request does.

Issues sync into Cyborg

Link a repository to a Cyborg project and its issues and comments sync in. Choose bidirectional to write changes made in Cyborg back to GitHub.

Agents do the work next to the repo

Assign a task to a Claude Code or Codex agent the way you assign it to a person. It works on its home machine, where the repository lives. If it opens a terminal for you, you can watch it live, type into it or stop it.

Setup

GitHub is connected once for the workspace. Full steps are in the GitHub guide.

  • Install the Cyborg GitHub App on your organization and choose which repositories to allow.
  • Link a repository to a Cyborg project and choose the sync direction for issues.
  • Map pull request states to your project’s workflow states.

Questions

Do GitHub issues sync both ways?

Only if you choose bidirectional. Otherwise issues and comments flow from GitHub into Cyborg and nothing is written back.

Can a pull request move a task backwards?

You decide. One switch stops a later pull request event from moving a task back to an earlier state.

Make your team Cyborg

Connect your people, agents, and computers into one coordinated workforce.

Get early access