Backstory

Why Halley Exists

A different answer to the old desktop problem: keeping context alive.

Halley began as a frustration with the traditional desktop.

For decades, graphical interfaces have treated work like a pile of overlapping paper: windows stacked, minimized, hidden, tiled, or pushed into virtual workspaces. These systems are familiar, but they often make large, messy, real-world workflows harder to understand. The more things you open, the easier it is to lose the shape of what you were doing.

Halley tries a different approach.

Instead of forcing every task into fixed workspaces or rigid layouts, Halley gives each monitor an open field. Windows live as spatial objects inside that field. They can expand when active, collapse into readable nodes when they move out of focus, and gather into clusters that behave more like living workspaces than static desktops.

The idea is simple: your computer should help you keep context.

You should be able to move through your work the way you move through a place. A browser belongs near the notes it supports. A terminal belongs near the editor it controls. A project should be something you can find, recognize, enter, leave, and return to without rebuilding your mental map every time.

Halley is built on Wayland and written in Rust, but its purpose is not just technical. It is about exploring a better interaction model for personal computing: one where navigation, memory, focus, and motion are treated as first-class parts of the desktop.

It is not trying to recreate the past.

It is trying to make the workspace feel alive again.