Version v3.3.0-beta.4
Beta, released on July 31, 2026
Groundwork: extensions. Settings now put Extensions, Trails, and Saddlepack where you expect them. Extensions are held to their declared permissions, dark mode carries over from 3.2.1, password filling understands more real login pages, Welcome and Settings survive a resize, and Trail exclusions keep doing their one job over time. <!-- horse-release-sha: 6d5bde0d21c2737ae20284c7a09017f104967413 -->
- Welcome and Settings stay visible when you resize the window.
- Saddlepack recognises more login forms, including sign-ins where the password field appears after the username step.
- Saddlepack avoids filling account-creation and password-change fields as though they were ordinary sign-ins, and still offers to save the new password you typed there.
- Pasting a full address into Trail exclusions now saves the correct site and keeps working over time.
- Navigating away no longer replaces a real parent Trail title with its address.
- More interrupted, retried, and rapidly repeated navigation keeps the correct Trail selected and preserves Back and Forward.
- On Windows and Linux, clicking a link while Horse is closed opens it as soon as the window is up instead of waiting on the network.
- The shelf stays open while an extension window is open, and closes when that window loses focus.
- On macOS, one click switches between extension windows: the click that closes one also opens the next. Double-clicking the titlebar zooms again.
- Pages that constantly create and remove embedded frames, like Feedly, no longer trigger a "Render frame was disposed" error dialog.
- Extensions now live inside the Settings menu, with their full submenu preserved.
- Trails and Saddlepack each have their own Settings screen.
- Horse now relies on extensions for ad blocking and dark mode instead of carrying separate built-in versions. If you had dark mode switched on, Horse installs and enables Dark Reader for you once and tells you; the same hand-off uBlock Origin Lite already makes for ad blocking.
- Extensions can now only read and touch the sites their permissions actually name. Scripts, styles, cookies, and page-visit events all check the extension's host permissions first.
