April 26, 2026
No clone, hot takes loaded
Show HN: Browse GitHub repos in Emacs without cloning
Emacs fans cheer, skeptics ask: why API, and why read-only
TLDR: A new Emacs add-on lets you browse any GitHub repository inside your editor without downloading, but it’s read-only. The community is thrilled by the convenience yet split over relying on GitHub’s API, wanting plain web access, and pushing for broader platform support—because fast code-peeking matters.
Emacs just dropped a party trick: a new package that lets you peek inside any GitHub project straight from your editor—no downloads, no mess, just instant snooping. Fans are calling it “buttery smooth” Emacs magic, loving that they can open folders, read files, and skim READMEs without cluttering their laptops. The catch? It’s read-only, and it leans on GitHub’s API via the GitHub command-line tool. Cue the drama.
The loudest thread starter? One commenter asked, “does this need to use the Github API?” and wished for “plain http.” That set off a mini culture war: purists want fewer lock-ins, tinkerers argue this approach is faster and smarter, and pragmatists just want to read code now. TRAMP loyalists (Emacs’s usual remote-edit tool) grumbled about not using the old way, while others said skipping heavy plumbing is the point. Folks joked that this turns Emacs into a “code Netflix” and revived the classic meme: “Emacs isn’t an editor, it’s an operating system.” There’s buzz about future support beyond GitHub—GitLab and Codeberg—and a Reddit thread fanned the flames with wishlist features and “just let me write, too!” pleas. Love it or side-eye it, the community is loud, divided, and absolutely glued to this read-only rollercoaster.
Key Points
- •remoto.el lets Emacs users browse GitHub repositories read-only without cloning by mapping file operations to GitHub API calls via the gh CLI.
- •The package integrates with Emacs through file-name-handler-alist, enabling find-file, dired, completions, and dired-subtree to work on remote repos.
- •Usage supports multiple GitHub URL formats and provides canonical paths of the form /github:OWNER/REPO@REF:/PATH, with commands like remoto-browse and remoto-refresh.
- •Implementation fetches the entire directory tree once via the Git Trees API, caches it in memory, and retrieves file contents on demand with SHA-based caching.
- •The tool is read-only, lacks git operations, uses synthetic timestamps, may slow down on very large repos, and adheres to GitHub’s 5,000 requests/hour rate limit.