Back to browse
Better Hub – A better GitHub experience

Better Hub – A better GitHub experience

by bekacru·Feb 26, 2026·38 points·48 comments

AI Analysis

●●SolidSlickEye Candy

Prettier GitHub interface, but no killer differentiation vs VS Code + GitHub CLI.

Strengths
  • Keyboard-first ⌘K command center meaningfully faster than clicking
  • Real-time webhooks for PR/issue updates without page refresh
  • Comprehensive permission model respects user privacy with granular OAuth scoping
Weaknesses
  • Crowded category: Cursor, GitPod, GitHub Desktop already own workflow UX
  • No evidence GitHub's official team won't ship these same improvements
Target Audience

Developers who use GitHub daily; teams managing repositories

Similar To

GitHub Desktop · Cursor IDE · GitPod

Post Description

Hey HN,

I’m Bereket, founder of Better Auth. Our team spends a huge amount of time on GitHub every day. Like anyone who’s spent enough time there, I’ve always wished for a much better GitHub experience.

I’ve asked a lot of people to do something about it, but it seems like no one is really tackling GitHub directly.

A couple of weeks ago, I saw a tweet from Mitchell (HashiCorp) complaining about the repo main page. That became the trigger. I decided to start hacking on a prototype to see how far I could push an alternative interface using GitHub’s APIs.

Within a week, I genuinely started using it as my default, same with the rest of our team. After fixing a few rough edges, I decided to put it out there.

A few things we’re trying to achieve:

- UI/UX rethink* – A redesigned repo home, PR review flow, and overview pages focused on signal over noise. Faster navigation and clearer structure.

- Keyboard-first workflow: ⌘K-driven command center, ⌘/ for global search, ⌘I opens “Ghost,” an AI assistant, and more.

- Better AI integration: Context-aware AI that understands the repo, the PR you’re viewing, and the diff you’re looking at.

- New concepts: Prompt Requests, self-healing CI, auto-merge with automatic conflict resolution, etc.

It’s a simple Next.js server talking to the GitHub API, with heavy caching and local state management.

We’re considering optional git hosting (in collaboration with teams building alternative backends), but for now, the experiment is: how much can we improve without replacing GitHub

This is ambitious and very early. The goal is to explore what a more modern code collaboration experience could look like, and make it something we can all collaborate on.

I’d love your feedback on what you think should be improved about GitHub overall.

Similar Projects