Help Extend Horse

March 4th, 2025

Horse could not run Chrome extensions. Neither could any other app built on Electron, which is most of the desktop software you already have open.


This campaign asked you to help fix that in Electron itself rather than in one browser, so it would land once and everyone would get it. The ask was small: go to the pull request and show the Electron team that people wanted this.


It worked. See what runs today →

The Campaign

The goal was never a Horse feature. Extensions could have been bolted on privately, and there is precedent: Brave started as an Electron app and forked Electron into ‘Muon’ to get them, then carried that fork themselves for years. One person cannot carry a fork of Electron. More to the point, a fork helps exactly one browser.


So the ask was public and small. Go to the pull request. Upvote it. Say you want it. That was the entire thing this page asked of anyone who read it, and it was the only thing that would work, because what the change needed was not another volunteer writing code. It needed evidence that people wanted it.


Enough of you did it that within three days it was the most upvoted pull request in Electron’s history. Pieter Levels put it in front of an audience many times the size of this site’s. Sam Maddock had written the pull request and the packages underneath it, and kept at it while the votes came in. The core team saw the demand, and it merged.


That is the part worth keeping a page about. Electron carries something like 184 million users across apps like Slack and Discord, and every one of those apps can host extensions now. Anyone building a browser for a school, a newsroom, or one stubborn job no longer has to choose between the extension library and a fork they cannot maintain. Horse got what it needed by asking for something bigger than itself.


Closer to home, the person who asked most plainly was a customer. Max Roberts, in an interview on this site in 2024, back when he could only ask:


“I do desperately want integration with third-party password managers, specifically 1Password. The Saddlepack is a great feature/idea, but when you have years of passwords in another manager, you don’t want to leave them behind.”

Max Roberts, podcaster

The Timeline

Done

Manifest v3 Support

Core extension manifest support implemented in electron-chrome-extensions
Done

Chrome Web Store Package

Created electron-chrome-web-store for extension installation
Done

Preload API Redesign

Redesigned preload APIs to better support extension features
Done

Context Bridge Execution

Done

Service Worker Main

Implemented ServiceWorkerMain for extension background processes
Done

Service Worker Implementation

Implemented service worker support. Thanks to everyone who showed their support. This was the most liked pull request in Electron’s history.
Done

Electron 35 Release

Electron 35 containing the service worker implementation has been released.
Done

Extensions Working In Electron

June 2025

Sam Maddock got the whole set working together: the merged Electron APIs plus his packages, running real Chrome extensions in a real Electron app.
Done

A Year Of Refactoring In Horse

June 2025 to June 2026

Horse still could not use any of it. Trails predate all of this, and the code underneath them assumed a browser with no extensions in it. Rebuilding that took a year, and it finished in June 2026.
Done

Extensions Integrated, 3.3 Beta Launched

July 2026

1Password, uBlock Origin Lite, and Dark Reader, running in Horse on the Beta channel.
Pending

Full Chrome Web Store Support

The blocker that remains. Horse installs the extensions it has tested; installing anything you like straight from the Chrome Web Store does not work yet. Extensions were built for browsers made of tabs and Horse is made of Trails, so each one is ridden around here by hand before it joins the list.

Get on the Horse

The browser designed for ADHD minds. Trails® keep every page and every tangent where you left it.

favicon
Japanese Green TeasGoogle Search
favicon
Japanese Green TeaWikipedia
favicon
MatchaWikipedia
favicon
SenchaWikipedia
Sencha

From Wikipedia, the free encyclopedia

Sencha tea leaves and brewed tea

Sencha tea leaves and brewed tea

Sencha (煎茶) is a type of Japanese ryokucha (緑茶, green tea) which is prepared by infusing the processed whole tea leaves in hot water. This is as opposed to matcha (抹茶), powdered Japanese green tea, where the green tea powder is mixed with hot water and therefore the leaf itself is included in the beverage. Sencha is the most popular tea in Japan.
Types of sencha

The types of sencha are distinguished by when they are harvested. Shincha(新茶, "new tea") represents the first month's harvest of sencha. Basically, it's the same as ichibancha(一番茶, "first tea"), which is the first harvest of the year.

Kabusecha (かぶせ茶) is sencha grown in the shade for about a week before harvest. Asamushi (浅蒸し) is lightly steamed sencha, while fukamushi (深蒸し) is deeply steamed sencha.

Production

Sencha tea is made from the leaves of the Camellia sinensis plant. The leaves are steamed, rolled, and dried immediately after harvest to prevent oxidation. This process preserves the fresh, grassy flavor that sencha is known for.

The steaming process used in making sencha is what differentiates it from Chinese green teas, which are typically pan-fired. The duration of the steaming process affects the final taste and color of the tea.

Brewing

Sencha is typically brewed at lower temperatures than black tea or oolong tea. The ideal water temperature is usually between 60–80°C (140–176°F), with brewing time ranging from 1 to 2 minutes.

The tea can be brewed multiple times, with each infusion revealing different flavor notes. The first brew tends to be more astringent and fresh, while subsequent brews become milder and sweeter.

Join Our Community

Stay connected with updates, participate in discussions, and help shape the future of Horse Browser through our community channels.

Unsubscribe anytime.
Horse NewsletterIssue #12

Turn your Browser into the Ultimate Productivity System.

You don’t need a todo list, or a notes app. Your browser can do these things. But it should be more integrated than simply loading a website. This is where Horse Browser comes in, with built-in productivity features that make your browser a powerful tool.

Read the Manual

The full user manual: getting started, basics, navigation, features, and the FAQ.

Open the Manual
Opening page of the Horse Browser manual

Need Help?

Access your account, manage billing, and find answers to frequently asked questions about Horse Browser.

Get Help
Pascal and Eleanor at Disneysea Tokyo