English · 한국어
Keep your browser. Replace its frame.
Rivet Browser is a Windows-first, open-source browser frame for an installed Chromium browser. It keeps the browser engine, profile, sign-in, extensions, media stack and updates in the browser the user already chose. Rivet supplies the frame, workspaces and agent control surface.
Rivet is not a Chromium fork and it is not a webview browser.
Early implementation. The Rust workspace contains an experimental rivet session start
command, a generated local control protocol and a Windows runtime-injection bootstrap. It can
start an explicitly selected Chromium executable in visible or hidden mode. The direct native
frame, browser control commands, Ember integration and installer are not complete yet.
- Start and directly integrate a user's installed Chromium browser on Windows.
- Replace the visible browser frame with Rivet's native frame while retaining the real browser process and its browser-owned features.
- Offer the same browser control surface to people and agents through a CLI.
- Let a caller select presentation: visible for visual inspection and UI automation, or hidden when browser processing alone is enough.
- Let Ember coordinate a user's Rivet settings and logical workspaces as the user moves between registered desktop clients.
Hidden presentation does not mean that a page has no renderer. JavaScript, layout and navigation still run in the browser. It means Rivet does not create a visible composited browser surface or capture frames unless the caller asks for one.
rivet/: all Rivet code and packaging inputs. Rust is the implementation language.docs/locales/: translations of this README.scripts/tests/: repository checks.
Work happens on develop. Publishing is one way: develop to release to main through a
pull request. Internal planning documents stay on develop.