HeartFlow Harness · terminal
Aurora CLI
in your terminal.
One command from the repository. No global install.
The companion without a window.
Read from this site's harness copy
and from the repository itself.
Aurora CLI is the terminal half of the same harness the desktop build belongs to. It is a coding companion that answers at a prompt instead of in a window, and it starts from the directory you run it in, so the files it can see are the files you were already working on.
What it does with them is gated. Reads cost you nothing, and anything that writes, edits or runs a command waits for your approval first, one action at a time. You can also choose how much initiative it takes: in build mode it edits, and in plan mode it investigates and proposes without touching the tree.
It is local-first by design. Point it at your own local model daemon and the local models need no API key at all; the requirement the repository states is Node 20 or newer, and the package is MIT-licensed.
- Launch.
npx github:HeartFlowAI/HFAI-TUIruns theauroracommand the repository declares, at version 0.2.0 under the MIT licence with Node 20 or newer — checked at github.com/HeartFlowAI/HFAI-TUI. - Approvals. Reads are free; a write, an edit or a command stops and asks you first — checked against this site's own harness copy at /#aurora-cli.
- Separate surface. Aurora CLI is not the desktop build, and the Windows v12 test evidence does not cover it — checked on the same harness copy.
One line, from the repository.
No package to add to a project,
and nothing to uninstall afterwards.
npx github:HeartFlowAI/HFAI-TUI
Run it from the directory you want the companion to work in. The first run fetches the repository, so it needs a network connection and Node 20 or newer; after that the command is the same, and the requirements and the licence live in the repository rather than here.
The repository is HeartFlowAI/HFAI-TUI. What the harness has been measured to do, and what it has not, is on the evidence section of the homepage; the desktop build and the harness family have their own pages.
The same companion, on the desktop.
The terminal build and the desktop build are separate surfaces of HeartFlow Harness, with separate requirements and separate test evidence.