An extensible and keyboard-focused web browser
1.4k
Stars
41
Forks
42
Open issues
13
Contributors
AI Analysis
Glide is a keyboard-focused web browser built on Firefox, designed for users who prefer modal-based navigation and extensive customization through TypeScript configuration. It serves developers and power users seeking an alternative to traditional browsers with keyboard-centric workflows, support for web extensions, and specialized features like Gemini protocol support. It is not a general-purpose browser for typical users seeking mainstream functionality.
Inferred from signals mentioned in the README (tests, CI, type safety) — not a review of the actual code.
AI's overall editorial judgment — not an average of the bars above, can weigh other factors too.
Keyboard-first Firefox fork targeting power users and developers with TypeScript config
Glide is a Firefox-based browser fork launched in April 2025, designed for users who prefer keyboard navigation and extensibility. It layers modal keymaps, fuzzy tab search, and TypeScript-based configuration on top of Firefox. Target audience appears to be developers, terminal enthusiasts, and Vim-like workflow advocates. Real-world adoption metrics are limited; primary signals are GitHub activity (1,402 stars, 14 months old) and a maintained community Zulip. Not positioned as a general-purpose browser replacement.
Created April 2025, Glide enters a crowded niche of Firefox-based productivity browsers and keyboard-driven web clients. Similar projects like Tridactyl (browser extension, 6,251 stars) and Surfingkeys (extension, 6,108 stars) predate it; Floorp (8,244 stars) is another Firefox fork targeting customization. Glide differentiates by baking keyboard-first design into the core browser rather than via extension.
Star acquisition has been steady but modest: 1,402 stars over 14 months (roughly 100/month average), with 11 gained in the last 7 days. Growth trajectory suggests niche appeal rather than viral adoption. Project appears sustained by active maintenance (last push 2026-06-28, nearly current) and a funded development cycle (Depot sponsorship noted). Growth likely driven by word-of-mouth in developer communities and power-user forums rather than mainstream outreach.
Adoption not verified. README lists features and documentation links but provides no case studies, company usage, user counts, or testimonials. Appears targeted at individual users and small enthusiast communities rather than organizations. Presence of sponsorship (Depot) suggests some backing but does not indicate production scale.
Based on README: built on Firefox, uses TypeScript for user configuration, supports WebExtensions API, and implements custom modal keymap system. Appears to be a browser shell wrapping Firefox with custom UI and config layer, likely using TypeScript/Node tooling for build and configuration. Cannot verify implementation details from README alone.
Not documented in README. No mention of testing strategy, CI/CD setup beyond Depot sponsorship, or test coverage metrics.
Active: last push 2026-06-28 (one day before analysis date), suggesting continuous development. Project is 14 months old; regular pushes indicate not stagnant. Community presence via Zulip chat suggests engagement. However, limited public issue/PR discussion visible in repository metadata — cannot verify response times or development velocity.
ADOPT IF: you are a developer or terminal-focused user who wants keyboard-first browsing baked into the browser itself, value TypeScript configuration, and are comfortable using a young, community-maintained fork. AVOID IF: you need enterprise support, require absolute stability over experimental features, depend on proprietary browser features, or prefer lightweight extensions over full forks. MONITOR IF: you are interested in keyboard-driven workflows but want to see larger adoption numbers, more production case studies, or long-term maintenance guarantees before committing.
Independent dimensions
Mainstream potential
3/10
Technical importance
6/10
Adoption evidence
2/10
- Fork maintenance burden: Glide must track Firefox releases and merge upstream changes; divergence risk increases over time, potentially leading to security gaps or compatibility issues.
- Limited adoption visibility: no documented production users or organizations; community appears small, raising questions about long-term viability if maintainers lose interest.
- Tight niche: keyboard-first browsing appeals primarily to developers and power users; mainstream growth potential is inherently constrained.
- Dependency on TypeScript ecosystem: configuration reliance on TS tooling may alienate non-developer users; build/install complexity could limit accessibility.
- Competing extension ecosystem: Tridactyl and Surfingkeys offer similar keyboard workflows with lower friction (no fork required), making Glide's marginal value harder to justify for casual users.
Glide likely remains a niche project serving dedicated keyboard-driven user communities. Adoption may grow steadily within developer circles and terminal enthusiast spaces, but unlikely to reach mainstream market share. Long-term viability depends on continued volunteer or sponsored maintenance; if funding or momentum stalls, project risk increases. More probable outcome: stable, community-maintained fork with 5k–20k active users over 2–3 years.
Newsletter
Get analyses like this every Monday
Free weekly digest of the most interesting open-source discoveries.
Languages
Information
- Website
- https://glide-browser.app
- Language
- TypeScript
- License
- MPL-2.0
- Last updated
- 20h ago
- Created
- 15mo ago
- Analyzed with
- anthropic/claude-haiku-4-5
Stars over time
Contributors over time
Top 100 contributors only — repos with more will plateau at 100.
Open issues
Add `PreModeChanged` autocmd for cancelling mode transitions
Set up / document memory usage benchmarks
gemini: auto reload custom css
gemini: support user input
gemini: support redirects
Top contributors
Similar repos
| Repository | Stars | Week Δ | Language | Score | Updated |
|---|---|---|---|---|---|
|
glide-browser/glide
this
|
1.4k | +19 | TypeScript | 7/10 | 20h ago |
 glidejs/glide
|
7.7k | — | JavaScript | 7/10 | 4mo ago |
 tridactyl/tridactyl
|
6.3k | — | TypeScript | 7/10 | 5d ago |
 glacambre/firenvim
|
6.1k | — | TypeScript | 8/10 | 2mo ago |
 Robbendebiene/Gesturefy
|
1k | — | JavaScript | 7/10 | 4w ago |
 brookhong/Surfingkeys
|
6.1k | — | JavaScript | 7/10 | 2w ago |
Firefox extension (not full browser fork); 6,251 stars; similar keyboard-first philosophy. Requires no installation of separate browser; lighter footprint. Glide offers more integrated customization but higher barrier to entry.
Browser extension for Chrome/Firefox; 6,108 stars; mature and widely used. Less intrusive than Glide; no fork required. Glide offers deeper integration but narrower platform support.
Firefox fork; 8,244 stars; focuses on UI customization and vertical tabs. Less keyboard-centric than Glide; broader appeal to general users. Glide is more specialized.
Keyboard shortcuts and extension support available out-of-box. Glide layers additional keymaps and modal workflows on top; adds value for power users but represents friction vs. vanilla Firefox.
Lighter-weight alternatives exist (e.g., Vimium, Vimium-C). Glide offers a complete browser environment rather than just keybindings, but requires full fork adoption.
Thanks to