Private development
Sarah
An AI companion that keeps its memory on your own hardware.
A voice-first companion and assistant: a PC brain for conversation and memory, a phone client, and a private bridge between them.
Ask about SarahScreenshots pending. Nothing may be published: Sarah is private, and its endpoint and bridge must not be shown.
How it is put together
- A PC-side brain handles conversation, persona and memory; a phone client connects to it through an authenticated bridge rather than a public endpoint.
- The bridge is deliberately strict: the phone client must reach it the approved way, and the test suite fails if a LAN fallback is reintroduced.
- Speech in and speech out are first-class, with a text path for the same conversation store.
Memory and identity
- Long-term memory is kept in a local store with per-identity archives; the owner store held roughly 2,972 conversation turns at the last audit.
- Persona and style are treated as engineering artifacts, with charm and response-quality suites in the regression set.
- Secrets live in a token vault backed by the platform keystore, not in configuration files.
Hardening
- A pathguard layer confines file access to approved roots, with a documented activation runbook for production.
- Dependency and security reviews are tracked as explicit owner decisions rather than silent upgrades.
- Regression evidence is kept as dated sweep files so a claim of “green” can always be traced to a specific run.
What is not there yet
- Sarah is a private project: there is no public build, download or API.
- At the most recent handoff the PC workstream was conditionally closed pending owner decisions and one open cross-project regression in the Android client's test harness.
- Sarah's machine endpoint and private network path are intentionally not described here or exposed anywhere on this site.
- Microphone capture on the owner's current hardware was still being diagnosed at that handoff.