Specsight reads code through a GitHub App with read-only access to the repositories you grant. It never writes to your code and never sees anything you have not granted. For the full data-handling story — ephemeral analysis, no source-code storage, GDPR — see Security at Specsight.
First-run setup handles the install for you. This article covers the GitHub page you use afterwards to add or remove repositories, or to disconnect. Open it by clicking Integrations in the organisation rail — the link lands directly on the GitHub page, with a sub-sidebar offering GitHub and MCP as the two integration surfaces.
Connect
- Click Integrations in the left rail — you land on the GitHub page
- Click Connect GitHub in the Connection card
- Pick the GitHub account or organisation to install the App on
- Choose All repositories or Only select repositories, then confirm on GitHub
You land back on the GitHub page with a GitHub connected. banner. The Repositories card lists everything the App can see.
Change which repositories Specsight can read
Click Manage repository access in the Connection card. Specsight opens the App's install page on GitHub, where you change the repository selection. Save on GitHub and the Repositories card updates on the next page load.
Disconnect
Click Disconnect in the Connection card and confirm. Specsight removes the installation record but keeps every existing spec — features, scenarios, annotations, and the changelog stay intact. Automatic syncing stops until you connect again.
Who can manage it
Only Admins and Developers can open the GitHub integration page. Everyone else can still read the spec the connection produces. See members and roles for the full breakdown.