The rules are Hearthkeep's own permissions table. clock and note are its real demo tools; outward tools arrive in Phase 4.
↗ Full screen
The problem
Cloud assistants see everything you type, and an agent that can act needs rules it cannot talk its way around.
What it was
Local models on your own PC, passkeys, and nothing leaves without your yes.
How it was done
Local models only: chat through llama.cpp, images through ComfyUI, swapped on the GPU when they don't fit together.
Every tool call is Look, Change local or Outward, and every tool is Allowed, Ask or Off. Unknown tools fail closed.
Anything outward waits for an approval and a fresh passkey check. The model cannot approve its own requests.
Everything listens on 127.0.0.1; phones reach it only over a private Tailscale network. Sign-ins, approvals and permission changes go into a log the app cannot edit.
The result
Phases 1 to 3 done: passkeys, approvals, audit log, local chat, image generation and photo editing, and files analysed in a sandbox where every number is checked by code. Public on GitHub under Apache 2.0.