Dillo 3.3.0 Adds Remote Control and OAuth Fixes

Dillo browser version 3.3.0 is out, and the release adds a set of changes that are small in size but meaningful for users who still rely on lightweight, privacy-focused browsing tools. According to the project’s release notes, the new version brings a command-line control utility, page actions, bug fixes, experimental support for FLTK 1.4, and a browser behavior change that helps OAuth logins work again in cases involving redirects and cookies.

Dillo is a long-running graphical web browser that has always occupied a narrow niche. It is built to be fast, simple, and modest in its resource use, which makes it different from the larger mainstream browsers that ship with large JavaScript engines, extensive media support, and layers of integrated features. That simplicity has been part of Dillo’s identity for years, and it also means changes to core behavior can have an outsized effect on the kinds of workflows it can support.

One of the most notable additions in 3.3.0 is a new command-line control tool. The release notes call it dilloc, and it gives users a way to interact with the browser from the terminal rather than only through the graphical interface. For people who automate desktop tools, that matters because command-line hooks can be easier to script, monitor, and combine with other utilities.

The release also introduces page actions. In practical terms, that means the browser can now expose actions tied to a page or page state, which opens up more structured handling of browser events and interactions. The project has not framed this as a full automation platform, but it does add another layer of control that was not present before.

Another point in the release is experimental support for FLTK 1.4. FLTK, short for Fast Light Toolkit, is a cross-platform GUI library used by a number of small desktop applications. Experimental support usually signals that the code builds and is being tested against the newer library, but it may not yet be considered fully stable for all setups.

The browser also includes a fix for OAuth login flows that depend on redirects and cookies from the main page. OAuth is the authorization system used by many sites when you sign in through a third party, such as a Google or Microsoft account. In some browser implementations, cookie handling during redirects can interfere with that handshake, so support for cookies from the main-page redirect path can be the difference between a login failing and completing normally.

That kind of fix matters because modern web authentication often depends on browser behavior that seems minor on the surface, but is tightly specified underneath. If a browser is conservative about when it accepts cookies, it may block some login sequences even when the site itself is working as expected.

The release notes also mention several bug fixes beyond those headline items, which is typical for a point release in a mature project. For browsers in this category, maintenance updates often focus less on visual changes and more on making sure existing features continue to work across changing web and desktop environments.

Dillo 3.3.0 was released on 2026-04-26, and the project has published the update on its release page with the new control tool, page actions, FLTK 1.4 support, OAuth-related cookie handling change, and the rest of the bug-fix list.