Skip to Content

GitHub

The GitHub integration keeps AIDEN close to the way software actually ships: real repos, real branches, real pull requests.

AIDEN is not trying to replace your Git workflow. It makes AI work cleanly inside it.


Connecting your account

  1. Open AIDEN’s settings and choose Connect GitHub.
  2. Authorize AIDEN through GitHub’s standard OAuth flow.
  3. If your repos live in an organization, grant access to that organization during authorization.

You can disconnect at any time from the same settings screen.


What the integration does

Import repositories

Create a project From repository and pick any repo you have access to. AIDEN clones it and wraps project structure — board, stories, specs — around the existing codebase.

Branches and worktrees, automatically

When a story moves into implementation, AIDEN creates a branch for it. Parallel work is isolated in Git worktrees, so several stories (and several agents) can be in flight without stepping on each other. See Git Workflow for the mental model.

Pull requests from finished stories

When a story is ready for review, AIDEN can open a pull request automatically — with the story and spec as context. Review happens where it always has: in the diff.


The workflow this enables

  1. Import the repo as a project.
  2. Shape work into stories on the board.
  3. Each story gets its own branch as it starts.
  4. Finished work becomes a pull request.
  5. You review and merge — nothing ships without you.

Best practice

Let the story boundary be the branch boundary. One story, one branch, one reviewable pull request. If a PR feels too big to review, the story was too big — split it next time.