v0.14.0

11 October 2026Prerelease

A tab of any Space can now pop out into a Tab window of its own, so a page can sit on another monitor. Run pop-out-tab from Command scope, from the tab menu, or with omaweb run pop-out-tab <tab id>.
The live page moves into the window as it is. Nothing reloads, and scroll position, typed text and playing video carry over.
The tab stays in its Space's sidebar with a window mark. It keeps running whichever Space the main window shows, and it is never put away.
Selecting a popped-out tab raises its Tab window and leaves the main window as it was.
The window has a slim strip with the Space, Site information and the address. It opens with the Wayland app id omaweb-tab, so a Hyprland rule can place it, for example on another workspace.
A Tab window comes back after a restart, with its strip as you left it.
Closing the window or running put-back-tab returns the tab to the sidebar, still live.
A page in a Tab window asks for permissions and automatic downloads in its own Space. It fills the window when it asks for fullscreen. A link that wants a new tab opens a Glance or a new Tab window.
Which tabs are popped out, and the state of their strips, stay on this machine and are never synced.
An Agent tab cannot pop out.
A popped-out Pinned tab has no close-tab command, as in the sidebar.
A popped-out tab cannot move to another Space until you put it back.

These need omaweb-qtwebengine 6.11.2-12, which pacman now installs with Omaweb.

Bitwarden's passkeys now work in Omaweb. An extension can now ask where its page's window is and how large it is. Bitwarden uses this to place its passkey prompt, and before this change it refused to open the prompt. With Bitwarden signed in as a Known extension, a passkey registers on webauthn.io and signs in again. On Wayland the window's top left is reported as 0, 0, and only the size is real.
Content scripts an extension registers are now kept across a restart, as in Chrome, unless the extension registered them with persistAcrossSessions: false. Turning a Known extension off and on again keeps them.
Because Bitwarden never unregisters its page script on logout, a Space that signs out of Bitwarden still gets that script after a restart.
When a window an extension opened with windows.create closes, the extension now hears tabs.onRemoved and then windows.onRemoved. A Bitwarden request ends when you close its prompt, so you no longer wait out the site's timeout.
A page an extension opened is still reported to the extension as its own window when Omaweb shows it as a tab. This happens with Glance off, or after "Open as tab" (#694).

On Omarchy, the one-line installer now runs omarchy update -y for the system upgrade and then pacman -S --needed omaweb. Omarchy's pacman guard aborts a direct pacman -Syu, so the installer no longer runs it there.
The installer's plan names which path it takes. On Omarchy, omarchy update keeps Omaweb current. On plain Arch, sudo pacman -Syu still does.
Omaweb no longer asks you to add a Hyprland window opacity rule, because Omarchy now draws windows opaque unless they opt in. Install and upgrade no longer print the rule. If you added it earlier, you can remove it. On Omarchy 4.0.4 or earlier, pages still look slightly washed without the rule.

A page in a Space not on show can now open tabs and windows. This covers a Keep active or inspected tab in an away Space, and an Agent tab in an Agent Space. Before, window.open returned null and an extension's windows.create failed.
- A tab request opens a tab at the end of that Space's list, and the main window stays where it is.
- An Auxiliary window opens as it does from the Space on show.
- A request from a page whose tab has just closed is now dropped.
A permission asked by a Keep active tab in an away Space is now answered in that tab's Space, not in the Space on show.
Favicons that recolour themselves for the colour scheme, such as ChatGPT's, now match the theme. Omaweb clears each Space's stored favicon drawings at startup, so the first visit in a run draws the icon again under that run's scheme.
- A launch that hands its address to an already running browser does not clear anything.
- A theme changed while Omaweb runs still shows the earlier icons until the next start (#700).
An Agent command with an option such as --name or --json before the verb now runs as an Agent command. Before, it silently launched or raised the browser you were using. Every option a verb takes may come before it. omaweb --name x mcp works. An Agent option with no verb now exits 2 and names the option.
Pinned tabs now stay on a column grid. A partial row leaves its remaining columns empty instead of stretching its tiles, and a lone pin is one column wide.

Full changelog: https://github.com/villekivela/omaweb/compare/v0.13.1...v0.14.0