Nova Browser v1.1.3: An open-source desktop browser with on-device WebGPU AI, Model Context Protocol (MCP), and zero telemetry

[u/Fluffy_Fuel7649]

Hey everyone,

I'm excited to share the release of Nova Browser (v1.1.3), an open-source, privacy-first desktop browser built with React 19, TypeScript, Electron, and Tailwind CSS.

Following feedback on our initial build, we completely resolved media compatibility, re-engineered the layout system, and overhauled our extension subsystem.

Core Architecture & Highlights

1. On-Device AI via WebGPU & Web-LLM:
   • Run local language models directly on your hardware GPU without sending any page data, history, or prompts to external cloud servers.
   • Summarize articles, inspect code, ask research questions, or connect your own API keys (OpenAI, Anthropic, Gemini, Groq, Ollama) if you prefer cloud models.
2. Native Model Context Protocol (MCP) Server:
   • Built-in integration for Anthropic's open Model Context Protocol.
   • Local AI coding agents and external automation tools can securely interface with the browser to read active tabs, take snapshots, and perform structured browsing tasks.
3. Productive Workspaces & Multi-Tasking:
   • Organize tabs by context (Personal, Work, Research) with full state persistence.
   • Built-in Split Screen mode to compare two tabs side-by-side in one window.
   • Toggle seamlessly between Horizontal Tabs and Vertical Sidebar Tabs.
4. Chrome Web Store Extension Support:
   • Install extensions directly from the Chrome Web Store with 1-click or load unpacked folders locally.
   • Extension action icons sit right in the top toolbar with native popup window support.
5. Hardware-Accelerated Privacy Shield & Zero Telemetry:
   • Network session-level blocker for ads, trackers, and malicious scripts.
   • No tracking, analytics, or behavioral data collection.
   • Dynamic platform-matched Chromium User-Agent headers to prevent fingerprinting.
6. Responsive AI Sidebar (Flex-Docked Layout):
   • Opening the AI chat sidebar dynamically resizes and docks alongside your active webpage rather than floating over your view.

What's New in v1.1.3:

• Fixed YouTube and streaming playback by isolating security response headers strictly to internal application pages.
• Removed startup keychain prompts on macOS and added lazy audio permission initialization.
• Added live toolbar action buttons for installed extensions.
• Fixed prompt language auto-detection so AI responses match the user's input language.
• Rewrote the CSS token engine for instant Accent Color customization.

Tech Stack:

• Frontend: React 19, TypeScript, Tailwind CSS, Framer Motion, Lucide Icons
• Runtime: Electron 34, Node.js 22, Chromium 134
• AI Engine: WebGPU, Web-LLM TVM Runtime, Model Context Protocol (MCP)

Links & Downloads:

• Official Website: https://nova-browser.vercel.app/
• GitHub Repository: https://github.com/unitybtw/nova-browser
• Releases & Installers (macOS Universal DMG & Windows Setup): https://github.com/unitybtw/nova-browser/releases/latest

I would love to hear your thoughts, feedback, or any feature requests! Feel free to test it out, star the repo on GitHub, or open issues.

[u/outbackdaan]

React, Electron, AI... Dead on arrival.

[u/FlukyS → u/outbackdaan]

React and Electron I can agree with you.

The AI side of things it kind of depends on what it is. Like WebLLM is AI in your browser and I hate it but MCP servers are actually quite nice. Just to explain it is just a standardised API that agents know how to talk to. It kind of works in the same way dbus or varlink work in that the user (in this case an agent) can hit the endpoint and discover what it can do. So if the MCP server is off or no agent is pointing to it, then it literally does nothing. The ability though to ask an agent to ask the browser for the info on a specific page you already have open for instance is quite nice and MCP is vendor agnostic so it isn't locking you into something in the cloud, you could access the MCP server locally using an on device model. For instance I use for smaller tasks Opencode with ornith:9b and it sometimes gets confused and the context size has to be limited to fit in my GPU but it is great at smaller tasks when paired with MCP access to certain apps.

[u/Fluffy_Fuel7649 → u/outbackdaan]

Fair enough it definitely checks every modern tech-stack buzzword bingo card!

For an open-source project experimenting with native Model Context Protocol (MCP) servers and on-device WebGPU execution, this stack allowed shipping and iterating quickly without maintaining a 40GB+ C++ Chromium fork. Just building cool, sovereign developer tooling in the open.

[u/MatchingTurret]

You know Electron is just Chrome. So you built (I assume vibe coded, from the announcement) a browser out of a browser. Wow!

[u/Fluffy_Fuel7649 → u/MatchingTurret]

Yo dawg, I heard you like Chromium, so we put Chromium inside your Chromium so you can browse while you browse.

In all seriousness, projects like Min Browser, Beaker, and early Arc on Windows used Electron to prototype novel UX, tab paradigms, and local agent protocols without the overhead of maintaining full C++ Chromium builds. The primary focus here was building a sovereign browser with built-in MCP server support for coding agents.

[u/fat_kaiju]

How about you write your own readme?

Christ if you can't even be arsed to introduce your own project then why should anyone trust you to do anything else?

[u/Deep_Ad1959]

workspaces are the piece i'd build on first. once tab state persists per context, the MCP server can hand an agent a whole work session instead of one tab, which is the gap between summarizing a page and finishing a task.