Open as many windows as you like

For four years, Horse ran in exactly one window.

Not because one window is purer, more focused, or spiritually aligned with the majestic horse. It was a limitation. The whole browser had been built around one window, and making another one without losing, duplicating, or confusing the Trail tree was genuinely hard.

For four years, the answer to “Can I open another window?” was “Not yet.”

On June 22, 2026, Horse 3.0 removed the limit.

Press ⌘+N and another Horse appears. Or use a Trail’s menu to send it into a new window. One on each monitor. One for the project you are buried in. One for the dashboard you are pretending not to check. If you own a truly unreasonable number of screens, Horse is prepared to meet you at your level.

Every window uses the same Trail tree.

Rename a Trail in one window and the new name appears in the others. Move a branch and everybody sees the move. There are no separate copies to reconcile because the underlying map remains one map.

Each window does keep its own place in that tree. The left screen can stay six links deep inside a project while the right screen remains on a calendar, a call, or the hotel-booking Trail you opened before discovering that the town has a museum devoted entirely to pencils.

The windows share the map. They do not share the cursor.

That distinction took time to get right. A second window that merely looks independent is easy. A second window that can edit the same living Trail tree, respond instantly to changes, and still remember its own position is the real product. The visible result is simple because the computer is doing an impressive amount of synchronised choreography behind the curtain. Tiny top hat. Furious little feet.

Trails preserve context inside a task. Windows let you place separate contexts beside one another.

You can keep a call in one window and the work it concerns in another. You can move a reference Trail to a portrait monitor without uprooting it from the larger project. You can give each screen a job, then close a window without deleting the Trails it showed.

This does not turn Horse back into a pile of detached rectangles. The hierarchy remains underneath everything. A page still knows where it came from. A branch can move between windows without becoming an orphan.

The computer gets to carry one coherent map across the whole desk. Your monitors get to stop behaving like expensive decorative panels. Tremendous news for everyone except the decorative-panel industry.

Before this release, Horse was still wearing 0.x version numbers.

That made sense while it was an experiment. It made less sense after years as a paid, signed browser that people trusted with their daily work. Horse had become a grown product while continuing to introduce itself as 0.77, like a full-sized horse wearing a foal costume and insisting nobody mention the knees.

So we counted the real milestones. The paid browser was 1.0. Trails, the navigation model that replaced tabs, were 2.0. Multiple windows became 3.0.

We had undersold the product in public for years. The number finally caught up with the animal.

Multiple windows have shipped. For everything that followed Horse 3.0, read the changelog. To understand the map those windows share, start with Trails.

Now open another window. Your second monitor has been loafing.