Updates

August 8, 2026

First preview - status & roadmap

QuBrain Omni is in preview

This is the first public status entry for the desktop browser. QuBrain Search and the Omni API already run on Cloudflare Workers at the edge (api.qubrain.org). The app UI is usable day-to-day, but several surfaces are still unfinished — this post is the honest snapshot.

What the browser can do today

  • Tabs — open, close, reorder, session restore, reopen closed tabs, per-tab mute, favicons, hover tips (title / domain / memory)
  • Navigation — back, forward, reload, hard reload, stop, omnibox (URL or search)
  • Start page — clock, branding, search, engine picker (QuBrain default + Brave, DDG, Google, Bing, …)
  • QuBrain Search — All / Images / News / Videos SERP, knowledge panel, pagination, image proxy
  • Library — bookmarks (toolbar + manager), history (manager + menu flyout), downloads (progress ring + manager)
  • Media controls — toolbar button when a tab plays audio/video; play/pause, seek, ±10s, PiP when available
  • App menu — New Tab / Window, History, Bookmarks, Downloads, Info, Exit
  • Info → Updates — this feed, loaded live from Cloudflare KV (not baked into the app binary)

Feature status

FeatureStatusNotes
Window chrome & multi-windowReadyMin / max / close, new window
Tabs & session restoreReadyIncludes closed-tab restore
Navigation + omniboxReadyURL or search
Start pagePreviewPreview banner still shown
Search engine pickerReadyDefault: QuBrain
QuBrain SERP (All / Images / News / Videos)ReadyVia api.qubrain.org
Knowledge / Wikipedia panelReadySide panel on SERP
Maps SERPExperimentalOff by default — enable with omni.features.maps=1
BookmarksReadyToolbar + manager
HistoryReadyManager + flyout
DownloadsReadyCEF downloads + UI
Global media controlsReadyOverlay above content
Per-tab muteReadySpeaker icon on tab
Info / Updates feedReadyCloudflare-backed
New Private WindowPlannedMenu item exists, not implemented
Delete Browsing DataPlannedMenu item exists, not implemented
Site permissions (general)Known issuesOnly Maps geolocation chip so far
Extensions / sync / passwordsPlannedNot started
Find in page / DevTools UIPlannedNot started

Known problems

  • Preview quality — chrome and start page are still marked as work-in-progress; expect layout and polish changes.
  • Maps — place search, opening hours, and nearby POIs are incomplete / flaky, so Maps is hidden from the tab bar until it is ready enough.
  • Private browsing — the menu entry does nothing yet (no isolated profile).
  • Delete browsing data — no unified clear flow from the menu yet (history / bookmarks / downloads can still be cleared on their own pages).
  • Permissions — no full site-permission model in the native host; only the Maps location prompt in the SERP.
  • Edge cases — rapid tab close / reopen used to race the content browser; recycling was added, but keep reporting crashes if you hit them.

Cloudflare backend (already shipping)

  • Search API on Workers with global edge latency
  • KV cache for responses and this updates feed
  • D1 + Vectorize own-index hybrid with SearXNG
  • Browser Rendering + Workers AI for previews / enrichment
  • Image proxy and place/geocode helpers for Maps

What we want to improve next

  1. Finish or remove stubs — Private Window and Delete Browsing Data should either work or leave the menu.
  2. Maps v1 — stabilize place results and hours, then bring the Maps tab back by default.
  3. Permissions — real prompts for geolocation / notifications / media from pages, not only SERP helpers.
  4. Settings — engine default, Maps flag, data clearing, and basic privacy toggles in one place.
  5. Stability & polish — fewer preview banners, tighter tab/media edge cases, clearer empty states.
  6. Later — find-in-page, password manager hooks, sync, extensions (only after the core browser feels solid).

Thanks for testing the preview — new entries will land here as features ship or known issues close.