Browser extension · open source

Turn every repo into a SuperRepo

Every tool lives one click away in the GitHub header. Prompt, diagram, wiki, IDE, podcast. No URL swaps, no account, no backend, nothing collected.

Install · free Try the live demo Browse the catalog
Live now on Chrome Web Store Microsoft Edge Add-ons Firefox Add-ons
Every service, one catalog 0 network calls of its own Path aware on file and folder views

Stop rewriting GitHub URLs by hand. The buttons are already where you look.

The problem

Every tool works. Remembering the rewrite is the tax.

github.com becomes gitingest.com becomes gitpod.io becomes deepwiki becomes gitdiagram. Each one works. None of them are where you already are.

✕
The manual way

Copy the URL, open a new tab, paste, swap the host, remember which host this tool wants, fix the path for files versus folders.

✓
With SuperRepo

One glyph in the repo header. Click it. The right URL for the page you are on opens in a background tab.

Features

Buttons that know where you are

A service that cannot accept the page you are on is not offered at all, rather than offered and broken.

Path aware

On a file view, GitIngest gets the containing folder, github.dev gets the exact file, and DeepWiki stays at the repo root — because that is all it accepts.

Four ways in

Header buttons, the More panel with filter and previews, the right click menu on any repo link, and the gp omnibox command.

Zero footprint

No account, no analytics, no backend and no network call of its own. It builds a URL and lets your browser open it.

Pins by name or by category

Pin up to eight services by name, or pick whole categories and let each slot fill with the tool you use most in it. Icon only or icon with name, in settings. Nothing is forced.

GitLab, opt in

Install touches one site: github.com. GitLab turns on in settings, and asks for that host and nothing else.

Learns your top four

A Frequently used section orders itself from your own clicks, stored locally, never transmitted.

How it works

Three steps, no setup

01

Install the extension

Install it from your browser's store, or download the build for your browser from the release page — one build per engine, on desktop and Android, plus a Safari companion app for macOS and iOS. One host permission: github.com.

02

Open any repository

The cluster appears right after Watch, Fork, and Star. Hover any glyph for its name and one line description.

03

Click, or copy the URL

Every row has a copy button. Hold the modifier key to open in a background tab. Alt+Shift+G toggles the full panel.

Service directory

Every tool we point a repo at

A treemap of the whole catalog. Each leaf is a tool, and the area of each category follows how many tools sit in it. Category bands stay together. Click any leaf to open that tool.

The whole catalog, grouped by category. Layout recomputes on resize.

Grow the catalog

Know a repo tool we missed, or a category we should cover?

The catalog grows one issue at a time. Maintainers can list their own tool with the template below, no code required, and new categories are welcome when the existing ones do not fit.

List my service Read the deal Contribute code
Privacy

It asks for the least it can

Install touches one site. No account, no analytics, no backend, no remote code. The extension builds a URL and lets your browser open it.

Permissions storage saves settings locally, contextMenus powers the right click menu, clipboardWrite powers copy, scripting only acts on a host you grant by hand.
Data collected None. Nothing is sent, sold, or shared. Usage counters live in storage.local and never leave the browser.
Content script GitHub only by default. GitLab stays off until you turn it on in settings and grant that one host.
Remote code None. There is no eval, no remotely hosted script, and no telemetry endpoint to phone home to.
Get started

Add SuperRepo to your browser

Free, open source, MIT licensed. Chrome, Edge and Firefox install straight from their stores; the Safari button downloads the build from the latest release — no clone, no build step — until its App Store listing finishes review.

Chrome, Edge, Brave

Every Chromium browser loads the same build — Chrome, Edge and Brave, plus Arc, Opera and Vivaldi, and Edge for Android. One build covers them all, and both stores carry it today.

Chrome Web Store Microsoft Edge Add-ons

Firefox

Its own build and its own manifest, live on addons.mozilla.org — and one of the few repo-tool extensions that runs on Firefox for Android.

Firefox Add-ons

Safari 17+ · macOS & iOS

Ships as a companion app for macOS and iOS/iPadOS, because Safari will not load an unpacked MV3 extension from a folder. In review on the App Store; npm run safari turns the same build into an Xcode project you run locally until it lands.

Download for Safari

The one build per engine reaches roughly 99% of desktop browsers (StatCounter, Sept 2026). On mobile it covers every browser where an extension can run at all — Safari on iOS, Firefox and Edge on Android — because Chrome for Android, Samsung Internet and Opera Android cannot run extensions.

No spam. Unsubscribe in one click. Email is not actually collected today; this form shows validation only.

FAQ

Questions, answered

Does this touch my GitHub account or need a token?
No. SuperRepo never calls the GitHub API and holds no credentials. It reads the URL in your address bar and builds another URL from it.
Does it work on private repositories?
The buttons render on any repository page. What the destination service can do with a private repo is up to that service, not SuperRepo.
Why does the install prompt ask for github.com?
Because the buttons render inside the page. There is no other way to put UI next to Watch, Fork, and Star. Nothing is read beyond the address bar and the header.
Can I turn off the in page UI?
Yes. Set placement to Nowhere in settings and the script stops rendering. The right click menu, omnibox, and toolbar icon keep working.
Does it work on GitLab?
Partially. Repo level services only, and only after you opt in in settings, which asks for the gitlab.com host.
How often is the catalog updated?
Each service is probed on a schedule and the results are published in docs/CATALOG.md. A rename or a dead service becomes visible in a diff.
Can I add my own service?
Yes. One object in src/catalog.js covers buttons, panel, context menu, and omnibox. Maintainer? Open one issue, no code, using the List my service template.
What browsers are supported?
Chrome, Edge, Brave, and Firefox from one source tree — plus Firefox for Android and Edge for Android; Safari ships as a companion app for macOS and iOS built with Xcode (see SAFARI.md). That covers about 99% of desktop browsers, and on mobile every browser that supports extensions at all.