If the GitHub connector is connected but Perplexity answers from the web, cannot see your repositories, or reports that a tool is unavailable, work through the steps below. For setup and permissions, see Connecting Perplexity with GitHub.
GitHub is connected but Perplexity says it is unavailable or answers from the web
Select GitHub as a source for the thread
In Search, select the paperclip icon before your first message and switch GitHub on. Writing @GitHub in your question does not select it as a source.
Start a new thread
If GitHub tools stop responding after the first message in a thread, the thread has lost its connector session. Start a new thread with GitHub selected and ask again.
Check Tools
Go to Plugins → Installed → GitHub → Tools (or Customize → Connectors if you don’t see Plugins yet) and make sure the read tools you need are set to Allow.
Reconnect
Open GitHub under Plugins → Installed (or Customize → Connectors if you don’t see Plugins yet), select Disconnect, then Reconnect, and reauthorize.
Check organization access on GitHub
If repositories belonging to a GitHub organization are missing, an owner of that organization needs to approve the Perplexity application for the organization in GitHub’s settings.
Enterprise members: confirm the connector is enabled
Confirm your Perplexity administrator has the GitHub connector enabled for your organization.
This connector can also appear inside a plugin. Connecting it anywhere connects it for your account everywhere, and your connection and your organization’s connector settings apply inside every plugin. What are plugins?
Rate-limit messages
A rate-limit message means GitHub is throttling requests from your account. Wait a few minutes and retry with a narrower request. Point your question at a specific repository, folder, file, or pull request rather than asking Perplexity to read an entire codebase at once.