Supported browsers

cubrs talks to your cube over Web Bluetooth, a browser feature that only ships in certain browsers. This is a browser limitation, not a cubrs one.

Where it works

Use Chrome, Edge, or Opera on desktop (Windows, macOS, Linux, or ChromeOS). These are Chromium-based browsers with Web Bluetooth built in, and they’re where cubrs is designed to run.

Where it doesn’t

Safari and Firefox don’t implement Web Bluetooth, so a cube can’t connect there. iPhones and iPads can’t run it at all — every browser on iOS uses Apple’s engine, and Apple hasn’t shipped Web Bluetooth. That’s Apple’s decision, not ours. If you land on the app in an unsupported browser, cubrs offers to email you a link so you can open it later on a desktop.

The keyboard demo works in any browser, because it doesn’t touch Bluetooth.

If your cube won’t appear: two Chrome flags

On most desktop setups Web Bluetooth just works. If your cube never shows in the connect list — most common on Linux — two chrome://flags settings can help. Paste each address into your address bar, switch it on, and relaunch the browser.

1. Experimental Web Platform features — chrome://flags/#enable-experimental-web-platform-features. This turns on the newest Web Bluetooth capabilities and is the flag that most often fixes a cube that won’t enumerate.

2. Web Bluetooth new permissions backend — chrome://flags/#enable-web-bluetooth-new-permissions-backend. This enables the persistent-permissions system that lets cubrs remember your cube and reconnect without asking every time.