Bruno is a local-first, file-system-based, Git-friendly, open-source API client. You store collections directly inside your codebase and they grow naturally with your API endpoints. But importing a collection from a GitHub repo still meant copying a URL and pasting it into Bruno.
Git Providers support changes that. You can search GitHub directly from the app, browse repositories, and clone collections without ever leaving Bruno. Download Bruno from official website.
Table of Contents
No authentication needed for public repositories. GitHub's public search API is open, so Bruno can query it without any credentials — this works out of the box.
Open the Import collection dialog and go to the GitHub tab.
Type a repository name or keyword in the search box. Results appear as you type.
Select the repository you want and click Clone. By default, Bruno clones into ~/Documents/bruno. Click Browse to pick a different location.
Bruno scans the cloned repo for Bruno collections and lists them. Select the ones you want and click Open.
Searching private repositories or scoping results to a specific GitHub organization requires you to authenticate with GitHub from within Bruno. This is available in Bruno Pro and Ultimate editions and supports two methods:
gh) Once connected, the scope dropdown in the GitHub tab gains new entries for your user and every organization you belong to. Private repositories appear in the list, often marked with a lock icon.
A PAT gives Bruno predictable, auditable access to GitHub on your behalf. It works in any environment and does not depend on having the CLI installed.
Step 1 — Open Git provider settings
Step 2 — Enable GitHub and generate a token
repo scope is the minimum.If you already have a token, you can paste it directly into the field — no need to generate a new one.
When the connection succeeds, the settings panel shows a Connected as @your-username via Personal Access Token confirmation. From there you can Refresh the connection or Clear token when it is time to rotate credentials.
Multiple accounts: You can add up to 5 GitHub accounts to your workspace using the All of GitHub input field in the GitHub settings panel.
Step 3 — Import again from the GitHub tab
Return to Import collection → GitHub. The scope dropdown now shows your user and your organizations. Select the right scope, search for the private repository, and clone it the same way you would a public one.
If you prefer not to manage a PAT, Bruno can delegate authentication to the GitHub CLI.
In Preferences → Git providers → GitHub, open the GitHub CLI tab.
Click Install to install the GitHub CLI if you do not have it, then authenticate from within Bruno.
Once connected, the panel shows Connected as @your-username via GitHub CLI. Use Refresh or Clear token to manage the session.
Recommendation: A PAT is still the better default — it is simpler to set up, easy to rotate, and works in environments where the CLI is not installed.
If your team runs a self-hosted GitHub Enterprise Server, Bruno can point its search and metadata calls at your internal instance instead of api.github.com.
Go to Preferences → Git providers → GitHub and expand Advanced.
Replace the default https://api.github.com with your Enterprise API root. For GitHub Enterprise Server this is typically https://<your-hostname>/api/v3. Check with your administrator if you are unsure.
Connect with a PAT or GitHub CLI as normal. Org-scoped search and private repos now resolve against your Enterprise instance.
Not sure which path to take? Use this table:
| Goal | What to use |
|---|---|
| Import a public repo by search | GitHub tab, scope All of GitHub, no login needed |
| Import private or org repos | Enable GitHub under Git providers + PAT (recommended) or GitHub CLI |
| Enterprise GitHub host | Same as above + Advanced → set API URL to your server's base |
| Any Git URL without search | Git repository tab + paste the URL directly |
Git provider support in Bruno gives you complete control over how collections are discovered, shared, and brought into your workspace. For public repositories, it is just a search and a click, no raw URLs, no browser tab switching.
For private repositories and organizations, connecting a PAT takes a couple of minutes and unlocks org-scoped search and private repo access. Enterprise users get the same experience pointed at their own host.
Happy collecting.