Repository navigation
Dev build 2026-11-21 (656a90a): Passkeys, authenticator codes and screenshots
Unstable dev build. Not a stable release: expect bugs, and keep backups of anything important.
The README now introduces the browser before the build instructions: what it is, what it does, how it looks and how to install it.
The browser can now keep passkeys itself. Each time a site creates or asks for one, you choose between the browser and a security key such as a YubiKey. The password manager also fills two-factor authenticator codes, and Ctrl+Shift+S takes screenshots. Security keys work everywhere now: sites like GitHub no longer wait forever for the browser.
New
- Passkeys saved in the browser: when a site offers a passkey (for example GitHub → Add a passkey), pick "Save in browser-wip" or "Use a security key". Passkeys are encrypted with your passwords and stay on this device.
- Signing in with a passkey: the panel lists the browser's passkeys for the site plus "Use a security key". On sites that support it, passkeys also show at the top of the login field's dropdown. With no passkey saved for the site, it goes straight to your security key.
- about:passwords lists passkeys in their own section, where you can delete them. Encrypted exports and imports carry them along.
- Authenticator codes (TOTP): add a site's two-factor key to its saved login by scanning the QR code on the page or pasting the key. The 6-digit code then fills itself in the code field, or you can copy it from the login dropdown or about:passwords.
- CSV imports and exports keep authenticator keys (a "totp" column).
- Screenshots: Ctrl+Shift+S, or "Take screenshot" in the app menu or the page context menu. Drag a region, click an element, or save the visible part or the full page. Then copy it or download it.
Fixes
- Security keys: sites asking for a security key (GitHub's "Add a passkey", for example) were stuck on "Waiting for input from browser interaction…" because the browser showed no prompts. It now asks you to plug in and touch your key, for your PIN, and which account to use.
- Authenticator codes for an account with no matching saved login now offer a new login instead of attaching to the first one.
- CSV rows with an authenticator key but no password are no longer dropped on import.
Changes
- The README has a feature list, a gallery of current screenshots, a download table for each Linux package, and credits.
- Build, test and release instructions are still there, under Build from source and Development.
- New screenshots in docs/screenshots: split view, tab overview, translation, the new tab page, first run, browsing and Settings.
- Using a saved passkey needs your master password typed within the last 5 minutes; the panel asks for it when needed, so sites can trust that it was you.
- Passkeys can't be saved in private windows, and a site can't make a second one for an account that already has one here.
- Dev builds are now regular releases, no longer marked pre-release.
Install (Linux x86_64)
| System | File | How |
|---|---|---|
| Any distribution | browser-wip-dev-20261121-656a90a-linux-x86_64.tar.zst or .tar.xz |
Extract it and run browser-wip/browser-wip |
| Any distribution, one file | browser-wip-dev-20261121-656a90a-linux-x86_64.AppImage |
chmod +x it and run it |
| Debian, Ubuntu | browser-wip-dev-20261121-656a90a-linux-x86_64.deb |
sudo apt install ./browser-wip-dev-20261121-656a90a-linux-x86_64.deb |
| Fedora, openSUSE | browser-wip-dev-20261121-656a90a-linux-x86_64.rpm |
sudo dnf install ./browser-wip-dev-20261121-656a90a-linux-x86_64.rpm |
| Arch Linux | PKGBUILD |
Put it in an empty folder and run makepkg -si |
Check a download with sha256sum -c SHA256SUMS --ignore-missing. The packages aren't signed.
Built from 656a90a, on the Gecko of Firefox 157.0.2.
Full changelog: dev-20261121-690d8b5...dev-20261121-656a90a