HeartFlow Harness · desktop

HeartFlow Harness
on your desktop.

A companion that works beside your windows, with your approval.

01 / THE DESKTOP SURFACE

A companion beside the work.

Everything here is quoted from this site's
own harness copy, with the date it was checked.

This is the desktop half of the harness, and the windows are the point. On a Mac, a Linux desktop or Windows you can hand it a task in plain language — find a document, research a question, work through something in an app it supports — and it navigates, uses its tools and speaks a short result back while the conversation stays where you left it.

You stay in charge of the parts that matter. The model is your choice, every file change and command is yours to approve, and a running task can be stopped. With listening enabled you can also start a request by voice, and read the sources and paths afterwards.

The build the documentation stands behind is the Windows v12 build, and it is cloud-connected. Distribution is deliberately unfinished: the builds are unsigned, there is no production installer and no updater, and the source release is planned rather than out. The permissions and data-handling notes for that build sit on the homepage, not here.

02 / WHAT SHIPS TODAY

An honest distribution state.

No installer, no updater,
and no download offered here.

There is nothing on this page to download, and that is the accurate state of the project rather than an omission: the builds that exist are unsigned and there is no production installer or updater. The source release is planned. When it lands, this page is where it will be described.

What can be read today is the evidence. The homepage carries the technical details and the test evidence for the Windows v12 build, together with what it does not cover, and the privacy notes for that build are there as well.

The evidence and its limits are on the homepage. The terminal build and the harness family have their own pages.

TWO SURFACES · ONE FAMILY

The same companion, at a prompt.

The terminal build shares the family and none of the desktop evidence, so its page carries its own requirements and its own approvals.