v0.13.0

Prerelease

Breaking changes

  • Omaweb now owns six Space colours: orange, yellow, green, teal, blue and violet. A theme's spaces values are no longer read, and the Omarchy template and the terminal theme importer no longer write them. Each colour has a fixed OKLCH hue and chroma. The theme moves its lightness until it reaches 3:1 on the Space grounds. If a colour lands within 20° of the theme's urgent colour, Private accent, Agent accent or another Space colour, it turns just far enough to clear it.
  • At start, stored bright_yellow, bright_green and bright_blue are renamed orange, teal and violet. An older build gives a name it does not know one of its own, and Sync carries that back. Update every machine you sync to v0.13.0.
  • Your settings now live in settings.json in the configuration directory. On the first start, Omaweb migrates interface.json, downloads.json, privacy.json and the settings kept in the session store, then deletes the old files it read. If you start an older build after that, it starts from default settings.

Settings in one file

  • settings.json holds only what you changed from the default, with typed values. It keeps unknown keys and your key order. Omaweb watches the file, so an edit applies while it runs, the same way a change in Settings does.
  • If the file does not parse or has another version, Omaweb keeps the last good values and never writes over the file. Settings says why at its top, the Settings button is marked, and the controls that write the file are disabled until you fix it. If a single value has the wrong type, that key falls back to its default and Settings names it.
  • Settings names the file at its top, with a button that shows it in its folder.
  • Allow agents and the agent command move to agents.json. Copying settings.json to another machine therefore does not let Agents in there.

Appearance

  • Settings' Interface section has a Sidebar opacity slider from 50% to 100% in steps of 5%, with a reset to the theme's value. Your value is kept as sidebar-opacity, survives a theme switch, and applies in Private windows too. Settings and History follow it when they have no page behind them.
  • A switch at the top of Settings' Spaces section turns Space colour off on this machine. Spaces are then drawn in the muted text colour, and each keeps its stored colour for when you turn colour back on. Settings offers the six colours in hue order.
  • The Omnibar writes another Space's name in the text colour, beside a square in that Space's colour.
  • On Linux, Settings lets you choose the launcher icon. Black and white is the icon the package installs. Theme is the same mark in the Omarchy theme's accent on its background, and it follows a theme switch while Omaweb runs. The choice is synced as app-icon. If you chose Theme and later remove the package, delete ~/.local/share/applications/omaweb.desktop so the menu stops listing Omaweb.
  • The sidebar's address field is now as tall as a tab row. The height and padding of both scale with the interface font size, as Pinned tab rows do. At the default size of 12 the rows are 36 px, and 44 px for a Pinned tab. At other sizes, a different number of tabs fits in the sidebar.
  • Translucent grounds over the desktop get a still dither of one output level. This covers the sidebar, the overlay panels and the Agent activity page. It stops a blurred wallpaper from showing as bands behind them.

Start page

  • At rest with no results, the Omnibar shows only its field. A ? key cap and "shortcuts" cue the Shortcut sheet in the Start page's lower right corner and go when you type. Typing ? into the empty field still opens the sheet. A new tab also asks "Where to?".
  • In the night sky, the planet now stands a third of the way down from the resting Omnibar. Its glow pulses on a five second cycle. Comets fall from the upper right at 25°, up to three at once. Every 30 seconds, a larger comet catches the Omnibar's rim, crosses in front of the planet and lights it up. That comet never falls under reduced motion.

Agents

  • Turning on Allow agents links the packaged Agent skill into ~/.agents/skills and into the skills directory of each installed coding agent. Turning it off removes only those links. If you had already allowed Agents, the skill is linked once at the first start.
  • Settings has an Agent setup row with Add skill and Add MCP server. Add MCP server registers omaweb mcp through the mcp add command of claude and codex, and leaves an existing registration alone.

Fixes

  • The user agent no longer carries the QtWebEngine/<version> token. Sites such as WhatsApp Web now load instead of showing their unsupported-browser page.
  • The browser no longer crashes when a Known extension such as Bitwarden creates an offscreen document. This crash was seen on resume from suspend. The package now requires omaweb-qtwebengine>=6.11.2-6.
  • A machine that had used its Space before adopting an existing Sync repository now restores the repository's Spaces. Before, it failed with "Could not apply a deleted remote Space". The repository's Spaces replace the used local Space. When a restore stops, the omaweb.sync log now names the record or Space it stopped on.
  • Sync no longer fails with "Could not apply the synced keybindings". keybindings.json was seeded read-only. It is now seeded owner-writable, and an existing read-only copy is made writable at start.

Full changelog: https://github.com/villekivela/omaweb/compare/v0.12.1...v0.13.0

This release on GitHub