amosblomqvist
8ebaf0da6e
Demos execute JS and need a browser; the app's own binary now provides one: main.cjs boots a hidden window + CDP port under --browser-service (before the single-instance lock - a helper is deliberately a second instance of this binary), lifetime tied to the server's stdin (EOF = quit, no orphans). headless.ts connects over CDP as PRIMARY (owner ruling 2026-10-10), system Chrome stays the fallback, graceful refusal when neither. Electron's CDP has no Target.createTarget, so the helper's pre-created window is THE page, reused and reset per job behind a serialized queue. PDFs and SVGs never reach a browser anymore (native since stages 1-2); stale Chrome wording in model-facing tool copy made engine-neutral. Live-proofed end-to-end from the dev tree (helper seen by process watch, js-ran 42 probe, no orphan). Gates 1523/1523.
LearnHarness
A desktop AI tutor that teaches by questioning — one reasoning step at a time — and keeps everything you learn in a growing knowledge graph.
It runs on your machine, with your own API key. Your data stays in plain files you can open.
The idea
Understanding has a dependency structure: some things require other things first. A lesson that ignores what you already hold is wasted on you; a lesson that outruns what you hold is lost on you. There is exactly one optimal path — the smallest set of steps from what you know to what you want to know — and finding it requires knowing precisely what you know.
So LearnHarness measures first. It questions you to bracket the edge of your understanding, plans the shortest path from that edge to your goal, then teaches it one reasoning step at a time — checking that each step lands before building on it. Every step is small enough to feel obvious on arrival.
And it remembers. Everything taught accumulates into a single persistent structure — propositions and the reasoning chains that connect them — rendered as the graph that is the app's home view. The next session starts from what the last one built: no re-probing what you already hold, questions aimed at the actual boundary of your knowledge, learning that compounds.
Teaching installs understanding; practice makes it available when you need it. Separate practice sessions draw problems from the same graph — retrieval at the edge of your ability, not review — because being taught something and having it come to mind in the right situation are different states.
Yours, locally
A system whose premise is that it can be trusted is built so that it can be checked:
- Your keys. Bring your own (OpenRouter works out of the box). No subscription, no markup — a live cost meter shows what each session actually spent.
- Your machine. Chats, graph, settings — plain files under your home directory. Nothing is sent anywhere except the model calls you configure.
- Inspectable. Every system prompt is visible and tunable. The graph is stored as reasoning chains — the structure of what you were taught, not a pile of text.
Download
Releases — macOS on Apple Silicon, signed and notarized. Windows and Linux are planned.
Quick start
- Download the DMG and drag the app to Applications.
- Open Settings, paste your OpenRouter API key, and pick your models.
- Start a session and say what you want to understand.
Development
npm install
npm run dev # http://localhost:3000
npm test # deterministic, no LLM, no network
The architecture spec and full development guide live in docs/ — start with docs/architecture.md and docs/development.md.