A small desktop app for keeping an eye on GitHub. Follow a set of users to get a unified feed of their public activity and merged pull requests, browse trending repositories from the Discover tab, and watch the Reactions tab for stars and forks on your own repositories.
Octoradar is built with Wails (Go + React). It signs in through GitHub's OAuth device flow and stores your access token in the OS keychain — never in plain text on disk.
| Feed | Discover |
|---|---|
 |
 |
Download the latest build for your platform from the Releases page.
The .dmg ships a universal build for both Apple Silicon and Intel.
-
Open the
.dmgand drag Octoradar into Applications. -
The app is ad-hoc signed but not notarized, so the first launch is blocked by Gatekeeper. Double-click Octoradar once (it will be blocked), then open System Settings → Privacy & Security, scroll down, and click Open Anyway next to the Octoradar message. You only need to do this once.
Alternatively, clear the quarantine flag from a terminal:
xattr -dr com.apple.quarantine /Applications/Octoradar.app
Pick the package for your distribution (replace <version> accordingly):
# Debian / Ubuntu
sudo apt install ./octoradar_<version>_amd64.deb
# Fedora / RHEL / openSUSE
sudo dnf install ./octoradar-<version>-1.x86_64.rpmThe packages declare their runtime dependencies (GTK 3 and WebKit2GTK 4.1). The GitHub token is stored through the Secret Service API, so a keyring daemon such as gnome-keyring must be running.
A plain .tar.gz is also provided for other distributions; extract it and run the octoradar binary, providing WebKit2GTK and a keyring daemon yourself.
- Launch Octoradar and sign in: it shows a one-time code to enter at the GitHub URL it opens in your browser.
- Add the GitHub usernames you want to follow.
- Watch the Feed for their activity, switch to Discover for trending repositories, or open Reactions to see stars and forks on your own repositories.
Prerequisites: Go (see go.mod for the version), Node.js 22 with pnpm, and the Wails CLI.
Octoradar needs a GitHub OAuth app client ID (with device flow enabled). The device-flow client ID is not a secret. Provide it via the OCTORADAR_CLIENT_ID environment variable for development, or bake it into a build with -ldflags:
# Live development
OCTORADAR_CLIENT_ID=<client-id> wails dev
# Production build
wails build -ldflags "-X github.com/tnagatomi/octoradar/internal/oauth.BuildClientID=<client-id>"