Oxagen Docs

GitHub App (private repositories)

Install and configure the Oxagen GitHub App so your workspace can ingest source code from private and organization-owned repositories.

Oxagen

Overview

Public GitHub repositories can be connected from the Oxagen app using owner/repo only — no GitHub App required.

Private repositories (and organization-owned repos that need app-based access) require the Oxagen GitHub App to be installed on the correct GitHub account or organization. The app grants workspace-scoped, auditable access so Oxagen can clone and index code through the same ingestion pipeline described in Ingestion.

Before you start

  • An Oxagen account and a workspace where you can manage connections.
  • A GitHub account with permission to install GitHub Apps on the target user account or GitHub organization (org owners can install for the org).
  • The repository names you want (in owner/repo form) and the default branch you want indexed (often main).

Install from Oxagen

  1. Open app.oxagen.ai and select the workspace that should own the connection.
  2. Go to Connections (or your workspace’s connection management surface).
  3. Choose Add connectionGitHub.
  4. Select the flow for private (or organization) repositories — not the public owner/repo-only path.
  5. Click Install GitHub App (or equivalent). Oxagen redirects you to GitHub’s install screen with a secure, one-time state so the installation is tied to your Oxagen workspace when you return.

Complete the flow on github.com before closing the tab.

Configure on GitHub

On GitHub’s installation screen:

  1. Install for — Pick your personal account or the organization that owns the private repos. If you pick the wrong account, Oxagen will not see the installation for the org you need.
  2. Repository access
    • All repositories — Simplest if policy allows; new private repos are included automatically.
    • Only select repositories — Add every private repo Oxagen should ingest. You can add more later under Settings → Applications → Installed GitHub Apps (user or org settings).
  3. Confirm permissions requested by the Oxagen GitHub App and finish Install.

If your company restricts third-party apps, an org admin may need to approve the app or allow installation for your org.

Finish in Oxagen

After GitHub redirects back to Oxagen:

  1. Open Add connectionGitHub → private flow again if needed.
  2. Select the installation that matches the GitHub account or org you used (Oxagen lists installations linked to your tenant).
  3. Enter owner/repo (for example acme-corp/api) and the default branch.
  4. Save the connection. Ingestion runs on Oxagen’s side using the GitHub App installation token for that org — your workspace graph stays isolated per Oxagen’s Security model.

Troubleshooting

IssueWhat to check
Installation missing in OxagenInstall completed on the same GitHub user/org you use in Oxagen; try Install GitHub App again from the connection dialog.
Repo not found or access deniedUnder the org’s Installed GitHub Apps settings, confirm the repo is allowed (All repositories or explicitly selected).
Wrong GitHub orgUninstall the app from the mistaken account (GitHub settings) and reinstall on the org that owns the code.
Org policy blocks the appAsk an org admin to allow the Oxagen GitHub App or to complete the install on behalf of the org.
  • Ingestion — How content becomes typed nodes and edges in the workspace ontology.
  • Security & Privacy — Data handling, workspace isolation, and encryption.

On this page