This guide covers the full connection lifecycle for Neo on GitHub — first-time install, joining an org a teammate already installed, reconnecting, switching the active org, and disconnecting.Documentation Index
Fetch the complete documentation index at: https://docs.neo.projectdiscovery.io/llms.txt
Use this file to discover all available pages before exploring further.
Before You Start
You need:- A GitHub account with permission to install the App (admin on the org, or install on your personal account).
- A Neo account. Any authenticated Neo user can start the connection. If you don’t yet belong to a Neo team, Neo creates one for you during the install. If your team already has Neo installed on an org you’re a member of on GitHub, you don’t need to install again — you just authorize.
Connect Neo To GitHub
Connect always starts with GitHub OAuth — not the install picker. That way Neo can immediately see whether your team already has Neo installed on a GitHub organization you’re a member of, and surface it without making you install a duplicate.Click Connect
From Settings → Applications → GitHub, click Connect GitHub. Neo opens a GitHub OAuth consent screen.
Return to Neo
Neo confirms the connection and opens the Applications panel. If your team already has Neo installed on a GitHub organization you’re a member of, that organization appears in the GitHub card’s organization switcher — you can start commenting
@pdneo on PRs in it immediately, no install required.Neo connects in two stages because most users who join a Neo team don’t need to install anything — a teammate already did. OAuth runs first so Neo knows who you are on GitHub; the install step (via + Add organization) is only needed when you actually need to grant Neo access to a new org or account.
Going Directly To Install
If you’d rather skip the in-app Connect button and install Neo directly from GitHub, use the public install link:Install Neo for GitHub
Open the GitHub install picker and pick the org or account where you want Neo to operate. Install and OAuth complete in one click.
Switch Between Organizations
If your team has Neo installed on more than one org, the GitHub settings panel has an organization switcher at the top:- click the dropdown to see every org you have access to
- select an org to scope the settings below to that install’s repositories and defaults
- the choice persists across reloads (saved per-browser)
- the bottom of the dropdown has + Add another organization — clicking that opens the GitHub install picker so you can install Neo on an additional org
Add Another Organization
You can connect Neo to more orgs at any time, without disconnecting first.Click + Add another organization
GitHub opens the install picker on a new tab so you can pick another account or org to install on.
Reconnect An Existing Install
Reconnect re-runs the OAuth step without touching the install on GitHub. Use it when:- you previously disconnected your Neo↔GitHub identity link and want to restore it
- your OAuth credentials need refreshing
- a teammate has rotated who is the registered installer
Click Reconnect
Neo opens GitHub’s OAuth-only screen — the App is already installed, so there’s no install picker.
Reconnect doesn’t install anything. It only re-runs OAuth. If the App has actually been uninstalled on github.com (rather than just disconnected in Neo), use the install link from the top of this page instead.
Disconnect Your GitHub Account
Disconnect is a per-user action that clears your Neo↔GitHub identity link. It does not touch the install on github.com and it does not affect your teammates.Confirm
Neo clears your stored GitHub identity link. The install on the team stays exactly where it was.
Ownership Rules
Neo enforces a clean install↔team relationship to avoid ambiguous ownership.- Each GitHub App install is owned by the user whose OAuth completed the original install.
- Teammates of that user see and can use the install via Neo’s team trust model.
- A GitHub-org-membership check guards visibility: even if a teammate installed Neo on an org, you only see it if you’re also a GitHub member of that org.
- Per-repo access is enforced via GitHub’s own collaborator check at use time — see Admin & Permissions.
Common Setup Scenarios
You’re A First-Time User With No Team Yet
Click Connect → authorize on GitHub → Neo creates a team for you and connects your GitHub identity. From the GitHub card, use + Add organization to install Neo on the org or account where you want it to operate. You can rename the team and invite teammates later from team settings.Your Team Already Installed Neo On An Org You’re A GitHub Member Of
Click Connect → authorize on GitHub → the org appears in your switcher immediately. No install step required — you’re already covered by the teammate’s install.Your Team Has An Install But You’re Not A GitHub Member Of That Org
The teammate’s install is hidden from your list because GitHub itself wouldn’t grant you access to those repos. After Connect/OAuth your switcher will be empty — use + Add organization to install Neo on an org or account you do own.You Want To Switch Which Org Settings Apply To
Use the organization switcher at the top of the GitHub settings panel. It rescopes the settings below without touching anything else.You Already Connected But Want To Uninstall Neo Entirely
Uninstall from github.com (Org settings → GitHub Apps → Configure → Uninstall). GitHub notifies Neo of the uninstall and Neo removes the install automatically. Don’t try to delete it from inside Neo — github.com is the source of truth for installation existence.Next
- Day-to-day usage and commands: Use Neo On GitHub
- Permissions and configuration: Admin & Permissions
- Stuck somewhere: Troubleshooting

